[{"user_id": 34550, "stars": [], "topic_id": 37223, "date_created": 1306639432.324625, "message": "i have been using virtualenv for quite a logn time, but things can get very messy. pythonbrew is a very good way to manage multiple python on the same platform. but the problem is how does pythonbrew substitute the role of virtualenv when it comes to django installation? or was it never intended to???", "group_id": 81, "id": 1215968}, {"user_id": 213, "stars": [], "topic_id": 37223, "date_created": 1306668665.963469, "message": "@johnwong518 pythonbrew isn't supposed to be a virtualenv replacement, but simply a way to install multiple Python versions easily. Each version can be a source for virtualenv's --python option, of course, but true isolation on a per-project basis isn't covered.", "group_id": 81, "id": 1216900}, {"user_id": 34550, "stars": [], "topic_id": 37223, "date_created": 1306678650.532207, "message": "when i say broken i mean the python being used in the virtualenv after creating it is using 2.6.6 although python 2.7.1 is activated and is being used.", "group_id": 81, "id": 1217581}, {"user_id": 34550, "stars": [], "topic_id": 37223, "date_created": 1306678518.475852, "message": "yeah i realized that and at the moment i am trying to install different version of python for different virtulenv i created. however, the switch that pythonbrew offers is broken (simply back to 2.6.6).. i got this by using yolk -l   still thinking how to achieve this. it's definitely a great tool : thanks jezdez. i will look into this more", "group_id": 81, "id": 1217573}]