Comments on: Tornado with VirtualEnv and Pip Quickstart http://dready.org/blog/2009/10/09/tornado-with-virtualenv-and-pip-quickstart/ musings on internationalized identifiers: domain names, OpenID, TLDs Sat, 08 Jun 2013 08:17:07 +0000 hourly 1 http://wordpress.org/?v=3.4.1 By: Matthew http://dready.org/blog/2009/10/09/tornado-with-virtualenv-and-pip-quickstart/comment-page-1/#comment-31242 Matthew Sun, 20 Nov 2011 12:14:56 +0000 http://dready.org/blog/?p=243#comment-31242 When are you in South Wales re: Llanelli area? Would love to come and see you perform. Thanks. Matthew When are you in South Wales re: Llanelli area? Would love to come and see you perform. Thanks.

Matthew

]]> By: wil http://dready.org/blog/2009/10/09/tornado-with-virtualenv-and-pip-quickstart/comment-page-1/#comment-29935 wil Sat, 10 Jul 2010 03:34:45 +0000 http://dready.org/blog/?p=243#comment-29935 Hey David, I haven't used epoll because using the mac for dev, and freebsd for prod. However, pip *should* do the normal setup.py stuff even when installing from git. Maybe you're using Python 2.6 and from what I can see tornado's setup.py refuses to build epoll.c unless you're on Linux and *not* using 2.6. I've also found the <code>--install-option</code> argument to pip install command to be invaluable when you need to pass additional args to setup.py. Hey David,

I haven't used epoll because using the mac for dev, and freebsd for prod.

However, pip *should* do the normal setup.py stuff even when installing from git. Maybe you're using Python 2.6 and from what I can see tornado's setup.py refuses to build epoll.c unless you're on Linux and *not* using 2.6.

I've also found the <code>–install-option</code> argument to pip install command to be invaluable when you need to pass additional args to setup.py.

]]> By: @dpn http://dready.org/blog/2009/10/09/tornado-with-virtualenv-and-pip-quickstart/comment-page-1/#comment-29934 @dpn Fri, 09 Jul 2010 23:24:28 +0000 http://dready.org/blog/?p=243#comment-29934 Hey wil, thanks for the post. have you figured out how to get the epoll.c module to build using pip? when you add a requirement from git it seems to just add the source code to the virtualenv and not compile the module. this of course is not acceptable for a production deployment! Any advice you may have would be very helpful! Hey wil, thanks for the post.

have you figured out how to get the epoll.c module to build using pip?

when you add a requirement from git it seems to just add the source code to the virtualenv and not compile the module. this of course is not acceptable for a production deployment!

Any advice you may have would be very helpful!

]]> By: wil http://dready.org/blog/2009/10/09/tornado-with-virtualenv-and-pip-quickstart/comment-page-1/#comment-29898 wil Mon, 17 May 2010 12:47:32 +0000 http://dready.org/blog/?p=243#comment-29898 The cleanest way is to recreate the virtual environment in other machines. To do that, you would want to produce a requirements file with pip, which details the exact version of all the packages you have installed in that virtual env. $ pip freeze > requirements.txt On the new machine, after you have created the empty virtualenv, and installed pip, you would just do: $ pip install -r requirements.txt There are other ways of doing it (like making your virtual env relocatable, etc.) but if you depend on modules that link to C libraries, and the machines are different, it won't work. There are also other things are likely to break. The cleanest way is to recreate the virtual environment in other machines. To do that, you would want to produce a requirements file with pip, which details the exact version of all the packages you have installed in that virtual env.

$ pip freeze > requirements.txt

On the new machine, after you have created the empty virtualenv, and installed pip, you would just do:

$ pip install -r requirements.txt

There are other ways of doing it (like making your virtual env relocatable, etc.) but if you depend on modules that link to C libraries, and the machines are different, it won't work. There are also other things are likely to break.

]]> By: snakejuice http://dready.org/blog/2009/10/09/tornado-with-virtualenv-and-pip-quickstart/comment-page-1/#comment-29897 snakejuice Mon, 17 May 2010 11:33:20 +0000 http://dready.org/blog/?p=243#comment-29897 What's the best way (or any way) to package the resulting virtual environment and deploy it to another machine (staging, production, etc.) ? What's the best way (or any way) to package the resulting virtual environment and deploy it to another machine (staging, production, etc.) ?

]]> By: wil http://dready.org/blog/2009/10/09/tornado-with-virtualenv-and-pip-quickstart/comment-page-1/#comment-29294 wil Thu, 24 Dec 2009 08:52:07 +0000 http://dready.org/blog/?p=243#comment-29294 I didn't know that, thanks for the tip! Text has been fixed. I didn't know that, thanks for the tip! Text has been fixed.

]]> By: Nick http://dready.org/blog/2009/10/09/tornado-with-virtualenv-and-pip-quickstart/comment-page-1/#comment-29293 Nick Thu, 24 Dec 2009 08:11:00 +0000 http://dready.org/blog/?p=243#comment-29293 Thanks for posting this! I just have one correction: it should be #egg=tornado, not #egg=Tornado. (The capitalization matters.) Thanks for posting this! I just have one correction: it should be #egg=tornado, not #egg=Tornado. (The capitalization matters.)

]]>