<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Workingenv is dead, long live Virtualenv!</title>
	<link>http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/</link>
	<description></description>
	<pubDate>Mon, 01 Dec 2008 21:45:20 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>

	<item>
		<title>By: Johan Segolsson</title>
		<link>http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/#comment-61280</link>
		<dc:creator>Johan Segolsson</dc:creator>
		<pubDate>Sun, 30 Nov 2008 13:48:28 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/#comment-61280</guid>
		<description>Should virtualenv override the PYTHONPATH environment variable as well in the activate script?</description>
		<content:encoded><![CDATA[<p>Should virtualenv override the PYTHONPATH environment variable as well in the activate script?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean DiZazzo</title>
		<link>http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/#comment-48877</link>
		<dc:creator>Sean DiZazzo</dc:creator>
		<pubDate>Thu, 25 Sep 2008 06:43:39 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/#comment-48877</guid>
		<description>Please remove the 'not' on line 400 of virtualenv.py  Maybe I'm too tired, but it sure seems assbackwards.</description>
		<content:encoded><![CDATA[<p>Please remove the &#8216;not&#8217; on line 400 of virtualenv.py  Maybe I&#8217;m too tired, but it sure seems assbackwards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kiorky</title>
		<link>http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/#comment-18404</link>
		<dc:creator>kiorky</dc:creator>
		<pubDate>Sat, 14 Jun 2008 18:18:32 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/#comment-18404</guid>
		<description>I encountered problems while testing virtualenv under cygwin for an application port to windows.
Here, you ll find a patch to make it working (it seems to).
http://distfiles.minitage.org/public/externals/minitage/patches/virtualenv.win.diff

To be honnest, i'm not a windows user and do no want to.</description>
		<content:encoded><![CDATA[<p>I encountered problems while testing virtualenv under cygwin for an application port to windows.
Here, you ll find a patch to make it working (it seems to).
<a href="http://distfiles.minitage.org/public/externals/minitage/patches/virtualenv.win.diff" rel="nofollow">http://distfiles.minitage.org/public/externals/minitage/patches/virtualenv.win.diff</a></p>

<p>To be honnest, i&#8217;m not a windows user and do no want to.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lee McFadden</title>
		<link>http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/#comment-5386</link>
		<dc:creator>Lee McFadden</dc:creator>
		<pubDate>Tue, 04 Dec 2007 13:21:10 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/#comment-5386</guid>
		<description>I'm still having problems with certain packages on OS X 10.5, particularly Paste, but there may be others out there.  I am trying to get TG2 into it's own virtualenv so I don't nuke my current development projects.  Included is the result of easy_installing Paste (with the output from the end of an SQLAlchemy install to show what the paths *should* be):

    Adding SQLAlchemy 0.4.1 to easy-install.pth file

    Installed /Users/splee/envs/tg2/lib/python2.5/site-packages/SQLAlchemy-0.4.1-py2.5.egg
    Finished processing dependencies for TurboGears2==2.0a1dev-r3757
    
    (tg2)TheBeastie:src splee$ easy_install -U paste
    Searching for paste
    Reading http://pypi.python.org/simple/paste/
    Couldn't retrieve index page for 'paste'
    Scanning index of all packages (this may take a while)
    Reading http://pypi.python.org/simple/
    Reading http://pypi.python.org/simple/Paste/
    Reading http://pythonpaste.org
    Best match: Paste 1.5.1
    Processing Paste-1.5.1-py2.5.egg
    Adding Paste 1.5.1 to easy-install.pth file
    
    Using /Library/Python/2.5/site-packages/Paste-1.5.1-py2.5.egg
    Processing dependencies for paste
    Finished processing dependencies for paste
    (tg2)TheBeastie:src splee$ 

It seems that Paste is still being used from the global site-packages dir, even if I create the environment with the `--no-site-packages` option.</description>
		<content:encoded><![CDATA[<p>I&#8217;m still having problems with certain packages on OS X 10.5, particularly Paste, but there may be others out there.  I am trying to get TG2 into it&#8217;s own virtualenv so I don&#8217;t nuke my current development projects.  Included is the result of easy_installing Paste (with the output from the end of an SQLAlchemy install to show what the paths <em>should</em> be):</p>

<pre><code>Adding SQLAlchemy 0.4.1 to easy-install.pth file

Installed /Users/splee/envs/tg2/lib/python2.5/site-packages/SQLAlchemy-0.4.1-py2.5.egg
Finished processing dependencies for TurboGears2==2.0a1dev-r3757

(tg2)TheBeastie:src splee$ easy_install -U paste
Searching for paste
Reading &lt;a href="http://pypi.python.org/simple/paste/" rel="nofollow"&gt;http://pypi.python.org/simple/paste/&lt;/a&gt;
Couldn't retrieve index page for 'paste'
Scanning index of all packages (this may take a while)
Reading &lt;a href="http://pypi.python.org/simple/" rel="nofollow"&gt;http://pypi.python.org/simple/&lt;/a&gt;
Reading &lt;a href="http://pypi.python.org/simple/Paste/" rel="nofollow"&gt;http://pypi.python.org/simple/Paste/&lt;/a&gt;
Reading &lt;a href="http://pythonpaste.org" rel="nofollow"&gt;http://pythonpaste.org&lt;/a&gt;
Best match: Paste 1.5.1
Processing Paste-1.5.1-py2.5.egg
Adding Paste 1.5.1 to easy-install.pth file

Using /Library/Python/2.5/site-packages/Paste-1.5.1-py2.5.egg
Processing dependencies for paste
Finished processing dependencies for paste
(tg2)TheBeastie:src splee$ 
</code></pre>

<p>It seems that Paste is still being used from the global site-packages dir, even if I create the environment with the <code>--no-site-packages</code> option.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon King</title>
		<link>http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/#comment-4835</link>
		<dc:creator>Simon King</dc:creator>
		<pubDate>Wed, 28 Nov 2007 09:53:01 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/#comment-4835</guid>
		<description>I think the Windows deactivate.bat script still has a couple of bugs. It contains this snippet:

    if defined _OLD_VIRTUAL_WORKING_PATH (
        set PATH=%_OLD_VIRUTAL_PATH%
    )
    set _OLD_VIRTUAL_PATH=

That's three different spellings of `_OLD_VIRTUAL_PATH`:

    _OLD_VIRTUAL_WORKING_PATH
    _OLD_VIRUTAL_PATH
    _OLD_VIRTUAL_PATH

If I replace them all with `_OLD_VIRTUAL_PATH`, everything seems to work properly.</description>
		<content:encoded><![CDATA[<p>I think the Windows deactivate.bat script still has a couple of bugs. It contains this snippet:</p>

<pre><code>if defined _OLD_VIRTUAL_WORKING_PATH (
    set PATH=%_OLD_VIRUTAL_PATH%
)
set _OLD_VIRTUAL_PATH=
</code></pre>

<p>That&#8217;s three different spellings of <code>_OLD_VIRTUAL_PATH</code>:</p>

<pre><code>_OLD_VIRTUAL_WORKING_PATH
_OLD_VIRUTAL_PATH
_OLD_VIRTUAL_PATH
</code></pre>

<p>If I replace them all with <code>_OLD_VIRTUAL_PATH</code>, everything seems to work properly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Graham Dumpleton</title>
		<link>http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/#comment-4081</link>
		<dc:creator>Graham Dumpleton</dc:creator>
		<pubDate>Thu, 22 Nov 2007 23:36:53 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/#comment-4081</guid>
		<description>The other issue with Python 2.3 which had forgotten and only remembered when I tried to run in on a different MacOS X system, is that Python 2.3 doesn't have the 'subprocess' module. Thus it is necessary to copy this from a new version of Python and install it by hand before running virtualenv.</description>
		<content:encoded><![CDATA[<p>The other issue with Python 2.3 which had forgotten and only remembered when I tried to run in on a different MacOS X system, is that Python 2.3 doesn&#8217;t have the &#8217;subprocess&#8217; module. Thus it is necessary to copy this from a new version of Python and install it by hand before running virtualenv.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jens Engel</title>
		<link>http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/#comment-3826</link>
		<dc:creator>Jens Engel</dc:creator>
		<pubDate>Tue, 20 Nov 2007 12:13:43 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/#comment-3826</guid>
		<description>I have a problem creating a virtual environment with virtualenv-0.9.2 on Cygwin.
The problem occurs when the Python interpreter/executable should be copied.

    ...
     File "virtualenv.py", line 468, in create_environment
        shutil.copyfile(sys.executable, py_executable)
    ...
    IOError: [Errno 2] No such file or directory: '/bin/python'

The problem seems to be that Cygwin mostly hides the ".exe" file extension
(or it is not considered for ``sys.executable`` in the Python port).
But the file extension is needed for ``shutil.copyfile()`` to work.

QUICKFIX:

    # -- INSERT-BEFORE: shutil.copyfile(sys.executable, py_executable), line 468
    if sys.platform == "cygwin" and not sys.executable.endswith(".exe"):
        sys.executable += ".exe"</description>
		<content:encoded><![CDATA[<p>I have a problem creating a virtual environment with virtualenv-0.9.2 on Cygwin.
The problem occurs when the Python interpreter/executable should be copied.</p>

<pre><code>...
 File "virtualenv.py", line 468, in create_environment
    shutil.copyfile(sys.executable, py_executable)
...
IOError: [Errno 2] No such file or directory: '/bin/python'
</code></pre>

<p>The problem seems to be that Cygwin mostly hides the &#8220;.exe&#8221; file extension
(or it is not considered for <code>sys.executable</code> in the Python port).
But the file extension is needed for <code>shutil.copyfile()</code> to work.</p>

<p>QUICKFIX:</p>

<pre><code># -- INSERT-BEFORE: shutil.copyfile(sys.executable, py_executable), line 468
if sys.platform == "cygwin" and not sys.executable.endswith(".exe"):
    sys.executable += ".exe"
</code></pre>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean Upton</title>
		<link>http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/#comment-2942</link>
		<dc:creator>Sean Upton</dc:creator>
		<pubDate>Tue, 13 Nov 2007 23:11:46 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/#comment-2942</guid>
		<description>On Win32, packages that distutils need to build C modules for as part of easy\_install within virtualenv require (at least for me), the workaround of copying c:\Python25\libs and c:\Python25\include - since there is not an include symlink like there is on virtualenv on unix.  This was true with both MinGW and VC++ 2003 environments; this may be something to note in documentation.  To duplicate within the virtual environment 'easy\_install zope.interface' - this will attempt to build one C module in zope.interface after fetching the package, which fails prior to the workaround, but succeeds fine after copying the libs and include directory.</description>
		<content:encoded><![CDATA[<p>On Win32, packages that distutils need to build C modules for as part of easy&#95;install within virtualenv require (at least for me), the workaround of copying c:\Python25\libs and c:\Python25\include - since there is not an include symlink like there is on virtualenv on unix.  This was true with both MinGW and VC++ 2003 environments; this may be something to note in documentation.  To duplicate within the virtual environment &#8216;easy&#95;install zope.interface&#8217; - this will attempt to build one C module in zope.interface after fetching the package, which fails prior to the workaround, but succeeds fine after copying the libs and include directory.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Graham Dumpleton</title>
		<link>http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/#comment-2877</link>
		<dc:creator>Graham Dumpleton</dc:creator>
		<pubDate>Tue, 13 Nov 2007 11:12:12 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/#comment-2877</guid>
		<description>BTW, any chance you can document --no-site-packages option on PyPi site where documentation is for virtualenv. I see this as an important option when using mod\_wsgi for shared hosting as in that sort of situation you want to base the underlying Python environment used by mod\_wsgi off a virtual environment which has an empty site-packages. Specific applications would then add on top using their respective virtual environments using site.addsitedir() based mechanisms. If however the application owners didn't use --no-site-packages option and a required module was in global site-packages, and thus easy\_install didn't add a copy to their own virtual environment, that module can then show up as missing when their application is run since mod\_wsgi will not be using the globally installed Python environment.</description>
		<content:encoded><![CDATA[<p>BTW, any chance you can document &#8211;no-site-packages option on PyPi site where documentation is for virtualenv. I see this as an important option when using mod&#95;wsgi for shared hosting as in that sort of situation you want to base the underlying Python environment used by mod&#95;wsgi off a virtual environment which has an empty site-packages. Specific applications would then add on top using their respective virtual environments using site.addsitedir() based mechanisms. If however the application owners didn&#8217;t use &#8211;no-site-packages option and a required module was in global site-packages, and thus easy&#95;install didn&#8217;t add a copy to their own virtual environment, that module can then show up as missing when their application is run since mod&#95;wsgi will not be using the globally installed Python environment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Graham Dumpleton</title>
		<link>http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/#comment-2864</link>
		<dc:creator>Graham Dumpleton</dc:creator>
		<pubDate>Tue, 13 Nov 2007 09:32:53 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/#comment-2864</guid>
		<description>Version 0.9.2 still doesn't work on MacOS X 10.4 with OS supplied Python 2.3.

    $ easy_install "TurboGears==1.0.4b2"
    'import site' failed; use -v for traceback
    Traceback (most recent call last):
      File "/usr/local/wsgi/virtualenv/ENV1/bin/easy_install", line 5, in ?
        from pkg_resources import load_entry_point
    ImportError: No module named pkg_resources

This time it appears to be because 'set' was used in site.py when Python 2.3 doesn't support 'set'. Using 'python -v' with easy_install yields:

    'import site' failed; traceback:
    Traceback (most recent call last):
      File "/usr/local/wsgi/virtualenv/ENV1/bin/../lib/python2.3/site.py", line 432, in ?
        main()
      File "/usr/local/wsgi/virtualenv/ENV1/bin/../lib/python2.3/site.py", line 412, in main
        paths_in_sys = removeduppaths()
      File "/usr/local/wsgi/virtualenv/ENV1/bin/../lib/python2.3/site.py", line 87, in removeduppaths
        known_paths = set()
    NameError: global name 'set' is not defined</description>
		<content:encoded><![CDATA[<p>Version 0.9.2 still doesn&#8217;t work on MacOS X 10.4 with OS supplied Python 2.3.</p>

<pre><code>$ easy_install "TurboGears==1.0.4b2"
'import site' failed; use -v for traceback
Traceback (most recent call last):
  File "/usr/local/wsgi/virtualenv/ENV1/bin/easy_install", line 5, in ?
    from pkg_resources import load_entry_point
ImportError: No module named pkg_resources
</code></pre>

<p>This time it appears to be because &#8217;set&#8217; was used in site.py when Python 2.3 doesn&#8217;t support &#8217;set&#8217;. Using &#8216;python -v&#8217; with easy_install yields:</p>

<pre><code>'import site' failed; traceback:
Traceback (most recent call last):
  File "/usr/local/wsgi/virtualenv/ENV1/bin/../lib/python2.3/site.py", line 432, in ?
    main()
  File "/usr/local/wsgi/virtualenv/ENV1/bin/../lib/python2.3/site.py", line 412, in main
    paths_in_sys = removeduppaths()
  File "/usr/local/wsgi/virtualenv/ENV1/bin/../lib/python2.3/site.py", line 87, in removeduppaths
    known_paths = set()
NameError: global name 'set' is not defined
</code></pre>
]]></content:encoded>
	</item>
</channel>
</rss>
