I'm noticing the mention of forks in PEP426 for "provides".
so theoretically, `pkg_resources.WorkingSet.resolve` would be updated at
some point to account for "provides" in PEP426, and this feature would be
surfaced as a setup keyword for users to use in their fork projects.
On Wed, Aug 14, 2013 at 10:53 AM, Marcus Smith
I'm wondering if PEP440 should recommend how to version forks? It's fairly common to fork dependencies temporarily until the change can be released upstream.
Ideally, you want to version a fork (and keep the same name) so that it fulfills the requirement, but be obvious that it's a fork.
Although pip allows overriding requirement consistency, consistency is preferred, and needed in cases where a `pkg_resources.require` enforces it in a console script.
As it is now, the "post-release" scheme works for this, but it's not the intended use case.
Marcus