Author paul.moore
Recipients jeremy.kloth, jkloth, jt, ncoghlan, paul.moore, steve.dower, tim.golden, zach.ware
Date 2019-02-16.22:54:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> 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 omitted seems at a minimum user-unfriendly, and possibly even outright broken. (We've had similar discussions in the past over Linux distros splitting parts of the stdlib into optional "devel" packages).

Is there a technical reason why the venv module cannot work with the nuget package? If not, then I'd suggest that we simply include it, and don't pre-judge what people might want to do with it. If there *is* a technical problem, let's document the limitation, and note in the venv docs that it may not be present in all installations.

(I'm specifically interested in venv here because there's a possibility that at some point, virtualenv will change to use the core venv functionality under the hood on Python 3+, and if that happens, your suggestion to use virtualenv would no longer work).
Date User Action Args
2019-02-16 22:54:20paul.mooresetrecipients: + paul.moore, ncoghlan, tim.golden, jkloth, jeremy.kloth, zach.ware, steve.dower, jt
2019-02-16 22:54:20paul.mooresetmessageid: <>
2019-02-16 22:54:20paul.moorelinkissue36010 messages
2019-02-16 22:54:20paul.moorecreate