FYI, the correct location for reporting virtualenv issues is: http://groups.google.com/group/python-virtualenv?hl=en
Ian may see comment you just added to his blog, but actual virtualenv group would be better. Graham On Sep 25, 4:35 pm, Sean DiZazzo <[EMAIL PROTECTED]> wrote: > Call me crazy...but is that a misplaced 'not' in my virtualenv.py ?? > > line 400 create_environment(home_dir, site_packages=not > options.no_site_packages, clear=options.clear, > > It also exists in their > trunk...http://svn.colorstudy.com/virtualenv/trunk/virtualenv.py > > Seems like it would have shown up as a problem on other systems as > well... > > Taking it out makes the environment work perfectly. The option is > inverted. Had we not used it, it would have worked! > > ~Sean > > On Sep 22, 3:59 pm, mbertoldi <[EMAIL PROTECTED]> wrote: > > > I experienced some problems in virtualenv 'isolation', > > on a clean osx install, empty site-packages, all went fine. > > The problems arise when you have some packages in host site-packages, > > easy-install wont pull again (even if virtualenv has --no-site- > > packages option), > > but python can't use them. > > So, it could be also an easy_install problem. > > I did't notice any difference using unzipped eggs instead of zipped > > ones, but i tried a long ago. > > > I'll try with a fresh osx install to find out more. > > > Michele > > On 23 Set, 00:11, Sean DiZazzo <[EMAIL PROTECTED]> wrote: > > > > On Sep 22, 12:56 pm, pa5cau <[EMAIL PROTECTED]> wrote: > > > > > If you do the following in the virtual env: > > > > $ easy_install -Zihttp://www.turbogears.org/2.0/downloads/current/index > > > > tg.devtools > > > > (force to unzip the eggs) > > > > then it works without problems using the default python installation. > > > > Just gave that a try to no avail. It didn't just work. > > > > I was messing around last night with it, and got several different > > > errors when making slight changes to the install process. Finally, I > > > wound up breaking my default python install :/ Don't ask. > > > > >Maybe the answers are in here: > > > > http://groups.google.com/group/python-virtualenv/browse_frm/thread/e3... > > > >If changes talked about in that have been done, maybe try virtualenv > > > >from source repository where ever that is. > > > > I tried using the current trunk (i think) from > > > here:http://svn.colorstudy.com/virtualenv/trunk/, but it still didn't > > > work. It looks like the changes mentioned in the thread you posted > > > are in the source though. > > > > I couldn't figure out an easy way to test the distribution. The best > > > way I found was to download the tg.devtools package, and modify the > > > setup.cfg to look inhttp://www.turbogears.org/2.0/downloads/current/index > > > for packages by adding: > > > > """ > > > [easy_install] > > > add_link = "http://www.turbogears.org/2.0/downloads/current/index"; > > > """ > > > It can't look at PyPi because we know there are no "TurboGears2" > > > project listed yet. > > > > Then I had to modify the setup.py file and change the "TurboGears2" > > > entry to "tg.devtools" I also noticed that "Paste" is not listed in > > > the setup.py as a requirement. > > > > Grabbing at straws, I think there might be a problem with setuptools > > > 0.6c8 and virtualenv on mac. > > > > I'll keep messing around, but at this point, I think that's all I'm > > > doing... > > > > ~Sean --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
