[WIP] PEP 582: (First draft) Using namespace on projects packages #686
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
Overview
This is a feature proposal. Now when a project is already register on pypi it's not possible to users to test a fork of any projects with the same name when it's already exist, manage projects by namespace increase possiblities for the python community.
With this feature we can introduce trusted packages by allow install/search without namespace and add namespaces on untrusted packages like docker behavior (
docker pull nginx
ordocker pull 4383/nginx
).On docker when the package is trusted (docker trusted image mean maintained by docker itself), namespace does not exist, and when a package is maintain by a third user namespace appear into the name.
I don't want delegate official projects maintainance to the pypa team but we can introduce a vote system by sending pull requests to a specific pypa repository. If the pull request is accepted the namespace was automaticaly removed.
Features
Benefits
Examples
With pip:
Url transposition: