On Tue, Apr 17, 2012 at 3:10 AM, krastanov.ste...@gmail.com <krastanov.ste...@gmail.com> wrote: > On 17 April 2012 05:20, Aaron Meurer <asmeu...@gmail.com> wrote: >> On Sun, Apr 15, 2012 at 11:31 PM, Joachim Durchholz <j...@durchholz.org> >> wrote: >>> Am 16.04.2012 01:46, schrieb Aaron Meurer: >>> >>>> I guess you should either create a separate virtualenv subdirectory, >>>> or else put it somewhere else completely. From what I understand, it >>>> doesn't really matter where it is in relation to the sympy directory >>>> or anything, because once you ./activate, you just install sympy and >>>> it goes in there. >>> >>> >>> Ah, I hadn't thought that that was possible, but it makes sense. >>> >>> My understanding is that you install any modules once per virtualenv >>> directory. So if you want to configure modules on a per-project level, you >>> need per-project virtualenv directories. >>> Did I get that right? >> >> Yeah, I think so. That way, they are all isolated from one another. >> > > But you can have also one project with differently configured dependencies. > > example - virtenv with old numpy: > # create the virtenv (a hidden folder automatically created somewhere > that you do not care about) > # activate it (now all installations go there automatically) > # install old numpy (just pip numpy an_old_version, and automatically > the old version of numpy is installed in this virtenv) > # cd to sympy which has nothing to do with virtenv and run sympy with old > numpy > # deactivate the virtenv (so now all PATH variables point to the > system PATH not the virtenv one) > # run sympy from the same folder. this time it will import the system > version of numpy > > i.e. you do not need to install sympy in the virtenv if you are using > it only from the sympy folder. > If you wish you can install it with setup.py. If you have activated > the virtenv it will be installed in the virtenv folder. If you did not > it will be installed in the system python modules folder.
Oh, I guess this way works pretty well too. By the way, if you're just using virtualenv to run the tests and nothing else, you should use tox, which does all of this for you automatically (see the tox.ini.sample file in the sympy repo). Aaron Meurer > > I think of virtenv just as a script that changes PATH and PYTHON_PATH > and does some bookkeeping. -- You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to sympy@googlegroups.com. To unsubscribe from this group, send email to sympy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
