[issue10483] http.server - what is executable on Windows

Change by mike mcleod : -- pull_requests: +28437 pull_request: https://github.com/python/cpython/pull/30216 ___ Python tracker ___

[issue10483] http.server - what is executable on Windows

Change by STINNER Victor : -- nosy: -vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue10483] http.server - what is executable on Windows

Change by mike mcleod : -- keywords: +patch pull_requests: +28141 stage: -> patch review pull_request: https://github.com/python/cpython/pull/29624 ___ Python tracker ___

[issue10483] http.server - what is executable on Windows

mike mcleod added the comment: I will work on this next week. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue10483] http.server - what is executable on Windows

STINNER Victor added the comment: > I got the impression that most core developers used Unix-variants for their > development, and likely most CGI users as well, and that Windows use of CGI > just wasn't a priority for anyone in the core team. Core devs are volunteers who are free to pick

[issue10483] http.server - what is executable on Windows

Glenn Linderman added the comment: On 11/18/2021 7:36 AM, STINNER Victor wrote: > STINNER Victor added the comment: > > I searched for open issues which contain "cgi" in their title. I found 43 > open issues. The oldest is 101 months ago. > > In 10 years, Lib/cgi.py got 43 commits. Only 13

[issue10483] http.server - what is executable on Windows

Change by Ethan Furman : -- versions: +Python 3.11 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue10483] http.server - what is executable on Windows

mike mcleod added the comment: Hi Victor, Ok I'll do that. Regards, Mike On Thu, 18 Nov 2021 at 15:36, STINNER Victor wrote: > > STINNER Victor added the comment: > > I searched for open issues which contain "cgi" in their title. I found 43 > open issues. The oldest is 101 months ago. >

[issue10483] http.server - what is executable on Windows

STINNER Victor added the comment: I searched for open issues which contain "cgi" in their title. I found 43 open issues. The oldest is 101 months ago. In 10 years, Lib/cgi.py got 43 commits. Only 13 commits in the last 5 years (since 2016-01-01). It seems like the cgi module is not really

[issue10483] http.server - what is executable on Windows

STINNER Victor added the comment: > I have put the question on Discuss and wait for (any) responses, Link to the discussion: https://discuss.python.org/t/issue-10483-http-server-what-is-executable-on-windows/11856 -- nosy: +vstinner ___ Python

[issue10483] http.server - what is executable on Windows

mike mcleod added the comment: I have put the question on Discuss and wait for (any) responses, -- ___ Python tracker ___ ___

[issue10483] http.server - what is executable on Windows

Éric Araujo added the comment: It’s not clear to me if CGI support in http.server is a relic or still something useful and in wide use. You can for sure make a pull request and see if a core dev will review and merge it, or you could raise the question on Discuss to see what people think.

[issue10483] http.server - what is executable on Windows

mike mcleod added the comment: Should I go ahead and make the changes as per msg122208 ? on my local copy and test? -- ___ Python tracker ___

[issue10483] http.server - what is executable on Windows

Glenn Linderman added the comment: Ethan, 3.7.2 at the moment. I doubt there'd be any issues moving it to 3.11, unless there have been significant changes to the main branch in that area, I just haven't bothered because it is working for me as is. I forget what version I started with,

[issue10483] http.server - what is executable on Windows

Ethan Furman added the comment: Glen, which version of Python is your fork using? -- nosy: +ethan.furman ___ Python tracker ___

[issue10483] http.server - what is executable on Windows

Glenn Linderman added the comment: As the original author of this report, getting significant pushback from the then maintainer of the code, I went ahead and implemented what I considered to be a useful set of features to make CGI work on Windows. I never proposed them as a patch, because

[issue10483] http.server - what is executable on Windows

mike mcleod added the comment: Hi Éric, Then would the easiest way of dealing with this issue, to close it without any further work? Possibly adding to the documents it doesn't work on windows.. I can move to the next issue. Regards, Mike On Sun, 31 Oct 2021 at 18:03, Éric Araujo wrote: >

[issue10483] http.server - what is executable on Windows

Éric Araujo added the comment: I don’t know if CGI on windows servers is very relevant nowadays. -- nosy: +eric.araujo versions: -Python 3.2 ___ Python tracker ___

[issue10483] http.server - what is executable on Windows

mike mcleod added the comment: Hi, I would like to help on this issue. Let me know what can be done? -- nosy: +mikecmcleod ___ Python tracker ___

[issue10483] http.server - what is executable on Windows

Glenn Linderman v+pyt...@g.nevcal.com added the comment: Martin, you are splitting hairs about the reported problem. The original message does have a paragraph about the executable bits being wrong. But the bulk of the message is commenting about the difficulty of figuring out what to

[issue10483] http.server - what is executable on Windows

Martin v. Löwis mar...@v.loewis.de added the comment: Martin, that is an interesting viewpoint, and one I considered, but didn't state, because it seems much too restrictive. Most CGI programs are written in scripting languages, not compiled to .exe. So it seems the solution should allow

[issue10483] http.server - what is executable on Windows

Glenn Linderman v+pyt...@g.nevcal.com added the comment: The rest of the code has clearly never had its deficiencies exposed on Windows, simply because executable() has prevented that. So what the rest of the code already supports is basically nothing. Reasonable Windows support is

[issue10483] http.server - what is executable on Windows

Martin v. Löwis mar...@v.loewis.de added the comment: Your suggestion of making CGIHTTPRequestHandler easier to subclass is certainly a good one, and is almost imperative to implement to fix this bug in a useful manner without implementing an insufficient set of Windows extensions (for

[issue10483] http.server - what is executable on Windows

Changes by Senthil Kumaran orsent...@gmail.com: -- nosy: +orsenthil ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10483 ___ ___ Python-bugs-list

[issue10483] http.server - what is executable on Windows

Martin v. Löwis mar...@v.loewis.de added the comment: I think it's fairly clear what should be considered executable in this context: anything that subprocess.Popen is able to launch (because if is_executable succeeds, this is what will happen to the file). This excludes word files, and also

[issue10483] http.server - what is executable on Windows

Glenn Linderman v+pyt...@g.nevcal.com added the comment: Martin, that is an interesting viewpoint, and one I considered, but didn't state, because it seems much too restrictive. Most CGI programs are written in scripting languages, not compiled to .exe. So it seems the solution should allow

[issue10483] http.server - what is executable on Windows

New submission from Glenn Linderman v+pyt...@g.nevcal.com: The def executable for CGIHTTPRequestHandler is simply wrong on Windows. The Unix executable bits do not apply. Yet it is not clear what to use instead. One could check the extension against PATHEXT, perhaps, but Windows doesn't