Comments on: How to get pip/virtualenv/Fabric working on Cygwin http://atbrox.com/2009/09/21/how-to-get-pipvirtualenvfabric-working-on-cygwin/ Mon, 23 Aug 2010 16:05:11 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: cdr http://atbrox.com/2009/09/21/how-to-get-pipvirtualenvfabric-working-on-cygwin/comment-page-1/#comment-2814 cdr Fri, 09 Jul 2010 14:03:19 +0000 http://atbrox.com/?p=110#comment-2814 The Fabric fix for cygwin went in, so you can use the master (http://github.com/bitprophet/fabric/tarball/master) with pip until the next release rather than manually patching and manually installing. The Fabric fix for cygwin went in, so you can use the master (http://github.com/bitprophet/fabric/tarball/master) with pip until the next release rather than manually patching and manually installing.

]]> By: Sancho Pansa http://atbrox.com/2009/09/21/how-to-get-pipvirtualenvfabric-working-on-cygwin/comment-page-1/#comment-2258 Sancho Pansa Wed, 16 Jun 2010 21:52:26 +0000 http://atbrox.com/?p=110#comment-2258 it is my experience, that generally you should avoid using windows and cygwin for serious development work with python - you will bounce your head against more and more problems, lxml is a problem, python-mysql is a problem, and if you have strange errors while debugging your own stuff, you can never be sure, if it is an error you have in your code or if it is a cygwin issue - overall it adds another level of unneeded complexity and lots of boring problems. To avoid all this just use a virtual machine. You can still use your favorite windows tools if you install samba into the virtual machine and export your home to a samba share, which can be mounted on the host machine. I spent many ours and always came to this conclusion - development with python on windows is still a pita, use a linux vm to save many hours! it is my experience, that generally you should avoid using windows and cygwin for serious development work with python – you will bounce your head against more and more problems, lxml is a problem, python-mysql is a problem, and if you have strange errors while debugging your own stuff, you can never be sure, if it is an error you have in your code or if it is a cygwin issue – overall it adds another level of unneeded complexity and lots of boring problems.
To avoid all this just use a virtual machine. You can still use your favorite windows tools if you install samba into the virtual machine and export your home to a samba share, which can be mounted on the host machine.
I spent many ours and always came to this conclusion – development with python on windows is still a pita, use a linux vm to save many hours!

]]> By: Luis M. Morales S. http://atbrox.com/2009/09/21/how-to-get-pipvirtualenvfabric-working-on-cygwin/comment-page-1/#comment-561 Luis M. Morales S. Fri, 12 Feb 2010 18:25:20 +0000 http://atbrox.com/?p=110#comment-561 i think the anoying problem you been having can be solve by using. cd \cygwin\bin ash PATH=. rebaseall -v i think the anoying problem you been having can be solve by using.

cd \cygwin\bin
ash
PATH=. rebaseall -v

]]> By: David Gingrich http://atbrox.com/2009/09/21/how-to-get-pipvirtualenvfabric-working-on-cygwin/comment-page-1/#comment-510 David Gingrich Sat, 06 Feb 2010 20:38:53 +0000 http://atbrox.com/?p=110#comment-510 FWIW: virtualenv 1.4.5.post1 seems to work (not very tested) with cygwin & win32 Python if you patch it: http://bitbucket.org/ianb/virtualenv/issue/22/fails-to-install-activate-when-running-win32-python-from-cygwin#comment-119005 FWIW: virtualenv 1.4.5.post1 seems to work (not very tested) with cygwin & win32 Python if you patch it: http://bitbucket.org/ianb/virtualenv/issue/22/fails-to-install-activate-when-running-win32-python-from-cygwin#comment-119005

]]>