Author jt
Recipients jeremy.kloth, jkloth, jt, ncoghlan, paul.moore, steve.dower, tim.golden, zach.ware
Date 2019-02-17.01:29:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1550366965.77.0.834156936042.issue36010@roundup.psfhosted.org>
In-reply-to
Content
> 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 only, even if that is where I use it right now - so technically I could make it not use the venv in this case but I'd rather avoid the code complexity. Why should I be required to add that branching?

I made this ticket precisely because the Windows Installer is a hassle, and the embeddable version isn't a properly complete Python. So as far as I'm concerned, I'll add to the vote that it would be very preferable to add venv to NuGet, and potential other missing modules people might expect to be around. Because otherwise this is kind of the embeddable issue all over again...
History
Date User Action Args
2019-02-17 01:29:25jtsetrecipients: + jt, paul.moore, ncoghlan, tim.golden, jkloth, jeremy.kloth, zach.ware, steve.dower
2019-02-17 01:29:25jtsetmessageid: <1550366965.77.0.834156936042.issue36010@roundup.psfhosted.org>
2019-02-17 01:29:25jtlinkissue36010 messages
2019-02-17 01:29:25jtcreate