[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

jt added the comment: Thank you so much for making it happen <3 -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Change by Steve Dower : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Steve Dower added the comment: New changeset 3e78c7c30553baf72b7eb6fe3384d88fff549906 by Steve Dower (Miss Islington (bot)) in branch '3.7': bpo-36010: Add venv to the nuget distribution (GH-12367) https://github.com/python/cpython/commit/3e78c7c30553baf72b7eb6fe3384d88fff549906 --

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Change by miss-islington : -- pull_requests: +12565 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Steve Dower added the comment: New changeset e724152796a5a41544f52054506c6c2248242a5d by Steve Dower (Paul Moore) in branch 'master': bpo-36010: Add venv to the nuget distribution (GH-12367) https://github.com/python/cpython/commit/e724152796a5a41544f52054506c6c2248242a5d --

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Paul Moore added the comment: Thanks! That seems to have done it. Update to the PR incoming once my test build completes. -- ___ Python tracker ___

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Steve Dower added the comment: > I ran Tools/nuget/build.bat manually, and the resulting file didn't have > lib\venv in it (I opened it in 7-zip, I don't know how to install a local > nuget file...). Huh, Tools/nuget/make_pkg.proj doesn't use the preset for some reason. I don't remember

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Paul Moore added the comment: I ran Tools/nuget/build.bat manually, and the resulting file didn't have lib\venv in it (I opened it in 7-zip, I don't know how to install a local nuget file...). Could you build the nuget files and check? Or suggest a better way I can check that the change

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Steve Dower added the comment: The change in the PR should be all that's necessary - the props file you are referring to is for end-users to integrate a Python build into their application (where I still assume they don't want venvs, and if they do there's already a property there to

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Paul Moore added the comment: The referenced PR isn't working - in the nuget package, python.props still says to exclude venv (and indeed venv is still missing). There's a PC/layout/support/props.py file that includes the offending "remove venv" line. Does that need modifying too? BTW,

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Change by Paul Moore : -- keywords: +patch pull_requests: +12330 stage: needs patch -> patch review ___ Python tracker ___ ___

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Steve Dower added the comment: > :-) I assume as we're at rc1, it's too late for 3.7.3, but it could be aimed > at 3.7.4. I might try to have a look at it if no-one else does. If Ned's okay with cherry-picking the change I have no problems with taking it still. It's just a default option

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Paul Moore added the comment: :-) I assume as we're at rc1, it's too late for 3.7.3, but it could be aimed at 3.7.4. I might try to have a look at it if no-one else does. -- ___ Python tracker

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Steve Dower added the comment: Yeah, someone still has to send a PR :) -- keywords: +easy stage: -> needs patch versions: +Python 3.7 ___ Python tracker ___

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Eryk Sun added the comment: > Is this only targeted at 3.8, then? Steve said he was okay with adding it in 3.7.3, but it hasn't been added yet in 3.7.3-rc1. In msg337949 I linked to the 3.7.3-rc1 version of options.py, line 54, where "venv" would need to be added to the nuget "options"

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Paul Moore added the comment: Hmm, I see that the Versions tag here is 3.8. Is this only targeted at 3.8, then? -- ___ Python tracker ___

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Paul Moore added the comment: Apparently, this is not in 3.7.3-rc1: >nuget install python -version 3.7.3-rc1 Feeds used: C:\Users\\.nuget\packages\ https://api.nuget.org/v3/index.json Attempting to gather dependency information for package 'python.3.7.3-rc1' with respect to

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

jt added the comment: Yeah, having this in the NuGet version would be amazing! I have been too specific with the ticket with my narrow mind set on a solution, but NuGet + complete standard library (including venv and pip) is what I now believe I actually should be using. Not that I would

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Paul Moore added the comment: Ah, yes, you're right. I'd misremembered. Thanks. -- ___ Python tracker ___ ___ Python-bugs-list

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Eryk Sun added the comment: > It appears that the venv module did not get added to the 3.7.3 rc1 > embedded distribution. Was that an oversight, or had I misunderstood > what was needed for this to have happened? I think it was supposed to be added to the nuget package:

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Paul Moore added the comment: It appears that the venv module did not get added to the 3.7.3 rc1 embedded distribution. Was that an oversight, or had I misunderstood what was needed for this to have happened? -- ___ Python tracker

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Steve Dower added the comment: Yeah, I'm okay with it for 3.7.3 and future releases. The only change should need to be for the nuget preset in PC/layout/support/options.py -- ___ Python tracker

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Jeremy Kloth added the comment: Thank you for your testing of the venv and pip workflows. At this point, I believe that all that remains would be for Steve Dower to incorporate the `IncludeVEnv=true` parameter into the nupkg build process. I personally do not see a problem with including

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

jt added the comment: Just to add this, I now tested the proper pip upgrade approach, and it worked fine, like everything else I tried before (installing & using Cython, any other packages, ...). If there's anything else I should test, let me know! NuGet with venv/ensurepip would be awesome

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

jt added the comment: > alternatively, you could perform an unattended installation: I know, I already listed the downsides above. (Basically outside of a container it's a bad way to do things because it has too many side effects, and it likes to break when interrupted after which you will

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Paul Moore added the comment: On Sun, 17 Feb 2019 at 14:12, jt wrote: > subprocess.CalledProcessError: Command > '['C:\\myproject\\tools\\windows\\.python-win\\spen-venv\\Scripts\\pip', > 'install', '--upgrade', 'pip']' returned non-zero exit status 1. > C:\myproject> > > I would expect

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Christian Korneck added the comment: for Python 2.7 you can extract the MSI installer (much like a zip file): mkdir "c:\targetdir" msiexec /a "c:\python-2.7.8.amd64.msi" /quiet /norestart TARGETDIR=c:\targetdir msiexec is part of all Windows editions (except for nanoserver). Side note:

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

jt added the comment: Okay there is one issue that looks like it might be venv related, which is that upgrading pip itself doesn't seem to work for some reason (while installing other packages in the venv worked fine): Could not install packages due to an EnvironmentError: [WinError 5]

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

jt added the comment: Ok, so I just tested this by 1. Installing Python 3.7.2 with the regular installer 2. Copying out "Lib\venv" and "Lib\ensurepip" into another folder 3. Uninstalling Python 3.7.2 (there is now no user-available install of Python on this system) 4. Installing Python via

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Steve Dower added the comment: It would be a great help if you could copy the ensurepip and venv directories from a regular install into an extracted Nuget package and let us know whether your scenario works. As you can see from the discussion, there were problems originally that may have

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

jt added the comment: Sorry I could have added more detailed use cases, so I'll append them here: The use case for venv in this particular script is that it's written to also work outside of CI, so it doesn't assume it runs in a "clean" python like this. And I would rather have the exact

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

jt added the comment: > As that's what you just installed with nuget, there's no point in creating a > venv - just pip install directly into it. This is not a pip install script or anything, it is more complex code that relies on venv. It is not written to run in this build environment

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Steve Dower added the comment: There certainly used to be a problem where venv was totally reliant on Python being in the registry to work properly. I'm not sure if that's still the case - possibly with the new redirector in 3.7.2+ it's fixed. --

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Paul Moore added the comment: > The whole point of a venv is to give you a separate directory with a "stand > alone" Python. As that's what you just installed with nuget, there's no point > in creating a venv However, shipping a copy of Python with a non-optional element of the stdlib

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Steve Dower added the comment: The whole point of a venv is to give you a separate directory with a "stand alone" Python. As that's what you just installed with nuget, there's no point in creating a venv - just pip install directly into it. Alternatively, you can pip install virtualenv and

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

jt added the comment: Okay, I just tested switching to the NuGet package and appear to have hit some sort of issue: C:\myproject\tools\windows\.python-win\python\tools\python.exe: No module named venv Traceback (most recent call last): File "C:\myproject\tools\windows\\windows-build.py",

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Steve Dower added the comment: > So is that a no for a regular .zip release here? > https://www.python.org/downloads/windows/ Correct, it's a no. The main reason is because people use it wrong and get into trouble, and we don't want to support that. (More after the docs link below) > If

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

jt added the comment: > Well, you still need a tool to fetch the zip and you need another tool to > unzip it Windows 10 actually has everything necessary around, so I don't! That's kind of the beauty of it, the other point being that every dev knows how to deal with a .zip (more than know

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Jeremy Kloth added the comment: > Why do I need to fetch another tool just to fetch Python? Well, you still need a tool to fetch the zip and you need another tool to unzip it. If not, how are you bootstrapping your script for those uses? > If this is the final decision then I recommend at

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

jt added the comment: So is that a no for a regular .zip release here? https://www.python.org/downloads/windows/ Don't get me wrong I'm all for options, I just don't get why there is no simple tool-less binary archive for Windows. Why are the only options different variants of installers

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Jeremy Kloth added the comment: On Sat, Feb 16, 2019 at 8:32 AM jt wrote: > Is nuget a standard windows utility? No, but if your script can download a zip of Python, it could download the nuget executable. > What happens if that process is interrupted? Same as interrupting an unzip

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

jt added the comment: Is nuget a standard windows utility? What happens if that process is interrupted? What happens if I install it twice to different folders? What happens if I want a specific python version? Don't get me wrong maybe it can do all these things, but why on earth do I need

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

Jeremy Kloth added the comment: For a "tool-style" installation of Python, see the 'PCBuild\find_python.bat' script in the Python source tree, specifically the nuget section. Ultimately, it is just: > nuget install pythonx86 -ExcludeVersion -OutputDirectory "some\path" which will create an

[issue36010] Please provide a .zip Windows release of Python that is not crippled/for embedding only

New submission from jt : It would be really useful if you could provide a .zip Windows release of Python that is not crippled/for embedding only. The reason is simply is that right now, I am having constant pain & trouble with it writing an automated build script for Windows (.bat) that