Thanks for the nudge.
If anyone is interested (or could approve to make the pipeline run), here's the
PR: https://github.com/python/cpython/pull/29217
___
Python-ideas mailing list -- python-ideas@python.org
To unsubscribe send an email to python-ideas-
Thanks. Not as catchy as I would have hoped, though. ;-)
One person except me in favor of this idea.
Any other feedback? How to proceed?
___
Python-ideas mailing list -- python-ideas@python.org
To unsubscribe send an email to python-ideas-le...@python.or
A question for the Python experts: What is the correct technical term for a
functionality like "http.server", i.e., a module with an actual "main" function?
___
Python-ideas mailing list -- python-ideas@python.org
To unsubscribe send an email to python-i
Thanks, finally a +1! \o/
It's funny that "entry point" triggered your reaction, because I think it's not
the correct technical term.
What I'm proposing is very similar to http.server:
https://github.com/python/cpython/blob/3.10/Lib/http/server.py#L1257
Just like "python -m http.server" you co
You are absolutely right, the functionality is there, but the idea is to make
it easily available from the command line.
Here is a line (with shortened URL) from a Dockerfile which installs poetry as
suggested in the docs:
RUN python -c "from urllib.request import urlopen;
print(urlopen('h
Performance is not an issue in the use case I envision.
This is about downloading small installation scripts (i.e for install poetry in
a container)
or a few megabytes of data.
I just tested the improved script (with just 1MB of read buffer) and it could
easily saturate
my 100 Mbit/s connection
I am aware of requests (or httpx, ...), but the idea is to do all that with the
standard library. If I have to install stuff, I could just install wget/curl
and be done.
Feature creep is an issue here, but just like http.server one could be really
strict about just
covering 90% of the use cases
