On Thu, Aug 24, 2017 at 5:04 AM, John Torakis <john.tora...@gmail.com> wrote: > Dark times... > > So is it a "case closed", or is there any improvement that will make it > worth it to be an stdlib module? > > I mean, times have changed from 1995, and I am not referring to HTTPS > invention. This is the reason that makes httpimport just tolerable > security-wise. > > I'm talking about the need to rapidly test public code. I insist that > testing code available on Github (or other repos), without the > venv/clone/install hassle is a major improvement in my (and most sec > researchers' I know) Python workflow. It makes REPL prototyping million > times smoother. > We all have created small scripts that auto load modules from URLs anyway. > That's why I thought that this modules falls under the second category of > 20.2.1 in https://docs.python.org/devguide/stdlibchanges.html (I did my > homework before getting to mail in this list). > > So, if there is something that would make this module acceptable for stdlib, > please let me know! I'd more than happily reform it and make it comply with > Python stdlib requirements.
Why can't people just "pip install httpimport" to make use of it? Why does it need to be in the stdlib? ChrisA _______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
