[Python] Remove nose support from server generators

Abierto
  • ¿Algo no está bien?
#25,401 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Refactorización
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
java, python
Área
backend, build-system, testing

Línea de trabajo

Start by locating the Flask, aiohttp, and BluePlanet server generator templates and Java options that define useNose, then trace their generated requirements, tox and CI configuration, documentation, samples, and ignore files. Compare the pytest settings across those generators and preserve the current Python support settings and dependency versions. Done when nose support and the option are removed throughout the affected generators, pytest is configured unconditionally, and the Flask Travis configuration installs test requirements and runs pytest.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Enhancement: Feature
Is your feature request related to a problem? Please describe.

The Python Flask, aiohttp, and BluePlanet server generators still support nose through a useNose option, generated requirements and tox configuration, and CI setup. Nose has been in maintenance mode for years, and its last release was in 2015. Keeping this option adds an obsolete test-runner path and leaves generated projects with inconsistent test configuration.

Describe the solution you'd like

Remove nose support completely from the Flask, aiohttp, and BluePlanet server generators. Generate pytest requirements and runner configuration unconditionally, remove the useNose option and Java API, and update the affected CI templates, documentation, samples, and ignore files. Preserve the existing Python support settings and dependency versions.

Describe alternatives you've considered

Keeping nose as an optional runner would preserve an outdated path and continue carrying its configuration through the generators. Upgrading pytest and standardizing its versions across all Python projects could be done separately; this change should preserve the current versions.

Additional context

This is a breaking change: users who set useNose will need to remove that property. Custom templates or generated projects that provide their own nose configuration may need manual updates. The change also fixes the Flask Travis configuration to install test requirements and run pytest.

Lenguaje dominante
Java
Estrellas
26.9k
Forks
7.8k
Merge medio
2 d 10 h
PR fusionados (30 d)
180

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de OpenAPITools/openapi-generator

Todos los issues de OpenAPITools/openapi-generator

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.