-
-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When docopt and docopt-ng are in the same venv, docopt takes precedence #22
Comments
Thanks for this issue @matthewdeanmartin. I feel like in hindsight, it would have been nice if the original forker had named the package (package meaning what you use with Renaming the distribution (eg what you use with |
All I can think of is leaving the old docopt-ng as is and publishing going forward with a new package name and new module name, e.g. |
See the discussion I started on discuss.python.org. I emailed the listed |
You should do a pep 541 name request |
See #48 for more info on PEP 541 name request. |
If you install
pipenv install pipreqs pip-upgrader docopt-ng
Which sometimes happens, you can't put everything into system or pipx.
Then apps use the wrong docopt.
In C# there was a way to handle this and ensure that two similarly named dlls weren't confused with each other, I don't know what the python way is to handle this scenario.
The text was updated successfully, but these errors were encountered: