[Python-Dev] Overriding stdlib http package
Guido van Rossum
guido at python.org
Wed Jan 14 21:25:15 CET 2015
Aha. Glad I asked. You would arguably get a more useful response if you
asked on core-mentorship and explained some of that background (for those
of us who rely on external memory :-).
The stdlib intentionally makes what you are trying to do hard (so library
writers don't have to worry about stdlib modules being overridden with
hacks at the whim of other library writers or app writers).
I'm not sure how commit privileges would help you -- can't you just fork
the CPython (I'm sure there's already a Bitbucket mirror that you can fork
easily) and do your work there? Even with commit privileges you wouldn't be
committing partial work unreviewed.
On Wed, Jan 14, 2015 at 12:07 PM, Demian Brecht <demianbrecht at gmail.com>
> On 2015-01-14 11:35 AM, Guido van Rossum wrote:
> > Why do you want to hack the existing http modules?
> > This is not a rhetorical question. The answer may lead us to redesign the
> > existing http modules to be more flexible so that the higher-level
> > you are trying to solve by hacking http import can be solved instead by
> > using an interface provided by the stdlib http module.
> Sorry, this venture began in core-mentorship, so a little context may be
> of use: My end goal is to become a maintainer of the http package.
> As I'm not a core dev, Nick had suggested making a friendly fork of the
> package in order to facilitate progress without being bound to the
> non-core dev contributor workflow (it can, at times, be a little painful
> getting reviews and such completed on orphaned packages).
> So, the question that I was trying to answer isn't directly related to
> the http package in particular, but how to override stdlib modules in
> general with a third party package in order to facilitate out of band
> development while making minimal changes to package code (i.e. changing
> all absolute import package names in test and module code) to ease
> upstream merging.
> That all said, this would likely be a moot issue if I had commit
> privileges ;) But it might be nice to figure out a good workflow should
> this come up again with any other new contributors looking to take
> ownership of an orphaned module.
--Guido van Rossum (python.org/~guido)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-Dev