Difference to sphinx-doc/sphinx-argparse
#262
|
Hi all, just something I was curious about. What is the difference between this package and the one over at https://github.com/sphinx-doc/sphinx-argparse / https://pypi.org/project/sphinx-argparse/ ? Having two packages maintained for a very similar purpose seems like a bit of a waste. Is it an option to combine both repositories? |
Replies: 2 comments · 4 replies
|
Hi folks, I was remembering this suddenly. Any thoughts on this matter in the end? |
|
Why When I created it in February 2021, Key differences in design:
Merging? The two have diverged significantly in architecture and API surface. Both serve their users well — 
|
|
Wow, thanks for the very clear answer, cool. So the differences are quite fundamental. It's a bit of shame because it feels like double effort to maintain both packages. Another consideration is that 
Have you considered moving under the |
|
Not sure I see the benefits of doing so 🤔 |
|
It gives a kind of authority to an extension, I think. If it's hosted under the Sphinx organization it shows it must be legit. |
|
The downside of doing that is that suddenly there are a lot of maintainer-level issues, such as permissioning and stuff, that inevitably we would run into. And technically this project is maintained by this organization, not that one, so having it here feels more correct. |
Why
sphinx-argparse-cliwas created:When I created it in February 2021,
sphinx-argparsewas effectively dormant — the original repo (alex-rudakov/sphinx-argparse) had its last release in 2018, and the revival underashbwas still early. The move tosphinx-docand the modernized 0.5.x releases didn't happen until mid-2024, over 3 years later.Key differences in design:
sphinx-argparsesphinx-argparse-cli:path: