[Distutils] PyPI pull request #7

holger krekel holger at merlinux.eu
Fri Nov 1 06:31:45 CET 2013

On Thu, Oct 31, 2013 at 16:52 -0700, Noah Kantrowitz wrote:
> On Oct 31, 2013, at 4:32 AM, anatoly techtonik <techtonik at gmail.com> wrote:
> > On Wed, Oct 30, 2013 at 11:11 PM, Noah Kantrowitz <noah at coderanger.net> wrote:
> >> Please stop submitting pull requests. Development on the existing codebase is halted except for critical fixes or security issues. You are making extra work for people on this list and it will not be tolerated. Please consider this your final warning.
> > 
> > I can't live as long as you are to see the new incantation of Python
> > website (by PyCon 2013) or PyPI. I am willing to help, and this stuff
> > you're saying is rather discouraging and like "no, go waste your time
> > somewhere else, we are not giving any code reviews for free". I
> > understand that my reputation precedes me, but can we keep this
> > strictly technical?
> > 
> > What I am trying to do is to send small, incremental fixes. They don't
> > affect security. I can commit it directly to avoid distracting
> > overloaded PyPI (bus factor 2) team, and you can blame me for breaking
> > things - ok, and ban if I break something - that's also ok. If learn
> > previous PyPI and new PyPI, I can tell people more about it, and you
> > can expect more pull requests - not from me, for new PyPI, once it is
> > ready.
> > 
> > And if I am going to submit any new features, like reST validation on
> > edit and Markdown support - the code will be more decoupled than
> > existing one to be almost directly reused for the new site.
> > 
> > 
> > Why I am skeptical that new site will replace old one soon? Just
> > because I don't believe in rewrites by one man army. When you develop
> > public resource, you need to rely on external feedback. You also need
> > some designer guy in a team. You also need a backlog for
> > collaboration. My ETA for new PyPI is no earlier than PyCon 2014 if
> > Donald and Richard will be working on it full time. So, instead of
> > all-or-nothing scenario I can try to find some help with incremental
> > approach.
> Your opinion is noted, however my statement stands and as I said, your continued derailment and disruption will not be tolerated. Thank you for your input.

Noah, I don't see Anatoly's postings here as derailment or disruption
and also see no reason to cultivate such a "won't be tolerated" tone
here.  Offering PRs is usually a total legit activity although generally
bitbucket/github is the primary place to handle them, rather than this
mailing list here. Differing oppinions on how things should evolve are also
daily open-source business.

However, Richard and Donald (the two pypi maintainers) have made it clear where
their priorities of spending their own time are.  Donald in particular
is heading the new pypi implementation and there are several areas of
possible collaboration there.  So it's obvious now that non-essential PRs on
the current PyPI code base have hardly a chance of getting eye time at the


More information about the Distutils-SIG mailing list