On Mon, Mar 26, 2012 at 12:58 PM, Carl Meyer <carl at oddbird.net> wrote: > No disagreement here. I think virtualenv's sweet spot is as a convenient > tool for development environments (used in virtualenvwrapper fashion, > where the file structure of the virtualenv itself is hidden away and you > never see it at all). I think it's fine to deploy _into_ a virtualenv, > if you find that convenient too (though I think there are real > advantages to deploying just a big ball of code with no need for > installers). But I see little reason to make virtualenvs relocatable or > sharable across platforms. I don't think virtualenvs as on on-disk file > structure make a good distribution/deployment mechanism at all. > > IOW, I hijacked this thread (sorry) to respond to a specific denigration > of the value of virtualenv that I disagree with. I don't care about > making virtualenvs consistent across platforms. > Well, if you're the virtualenv maintainer (or at least the PEP author), and you're basically shooting down the principal rationale for reorganizing the Windows directory layout, then it's not really much of a hijack - it's pretty darn central to the thread! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20120326/5e929719/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4