Steps to improve somewhat confusing ecosystem of Python systemd packages

Abierto
#152 1 comentario 13 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
python

Línea de trabajo

Start by reviewing setup.py and README.md in this repository, along with pull request #149, to compare the current PyPI description with the proposed README content. Check the package-name history and the linked cysystemd discussion before deciding which documentation changes belong here. Done requires agreed documentation updates and resolved cross-project follow-up.

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

Descripción

The ecosystem of Python systemd packages seems a bit confusing. Here's what the state appears to be, what some of the confusing aspects are and some possible steps to improve it.

Also, it's possible I've misunderstood some aspects of the state of the ecosystem today, if so please call them out so I can correct the summary below.

I've opened this request with the cysystemd project as well in https://github.com/mosquito/cysystemd/issues/71 to see if they can help and add some comparison information to their README.

Summary of Python systemd PyPI packages and Git repos

Things that are confusing

  • The mature and actively developed https://pypi.org/project/systemd-python/ project has a setup.py that doesn't contain a long_description value and as a result is rendered without any information on PyPI, making it appear immature or not legitimate on PyPI
  • The PyPI package named systemd-python has a backing Git repo named differently as python-systemd
  • The PyPI package name python-systemd which matches the Git repo name of the mature and actively developed repo https://github.com/systemd/python-systemd is actually an abandoned PyPI package from 2015 that isn't related to https://github.com/systemd/python-systemd

Things that could be done to improve this confusing ecosystem

By the systemd-python project

  • Merge https://github.com/systemd/python-systemd/pull/149 which adds the README.md contents to the PyPi project description to make the systemd-python project appear more legitimate and mature.
  • Zbigniew contacts Eugeny Pankov to ask if he would be open to retiring his PyPI project called python-systemd and transferring ownership of the PyPI project name to Zbigniew. The rationale to present to Eugeny would be
  • Zbigniew creates a stub PyPI project at https://pypi.org/project/python-systemd which directs people to use
    systemd-python
  • Zbigniew adds a short section to the README for systemd-python which acknowledges that cysystemd exists as another python interface to systemd, and maybe identifies the reasons a user would use systemd-python vs cysystemd

By the cysystemd project

  • Dmitry Orlov adds a short section to the README for cysystemd which acknowledges that systemd-python exists as another python interface to systemd, and maybe identifies the reasons a user would use cysystemd vs systemd-python
Lenguaje dominante
C
Estrellas
522
Forks
79
Métricas de merge de PR
Sin PR fusionados en 30 d

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

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 systemd/python-systemd

Todos los issues de systemd/python-systemd

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.