Thank you very much, this answer is so acurate! i did some locate, after reading your post, and you were right, there is some kind of mess as i have several python webhelpers:
/usr/lib/pymodules/python2.5/webhelpers/paginate.py /usr/lib/pymodules/python2.6/webhelpers/paginate.py /usr/local/lib/python2.6/dist-packages/WebHelpers-0.6.4-py2.6.egg/ webhelpers/paginate.py /usr/share/pyshared/webhelpers/paginate.py i don't know where does that mess come from as i don't remember i used easy_install for anything appart formBuild. So i think i first need to clean a bit of this mess. And then i'll use a sandbox a you suggest in your second point. Thanks again. On 30 oct, 16:21, cd34 <[email protected]> wrote: > First, Pylons 1.0 is current, debian is a little bit behind. 0.10 is > essentially Pylons 1.0 with deprecation warnings to ease transition > from 0.9.x. I use paginate in a number of projects the way you > describe using: > > Pylons 1.0 > WebHelpers 1.2 > SQLAlchemy 0.6.5 > > exactly how you describe. Paginate was broken a while back during the > transition to Pylons 1.0. Your environment has webhelpers in the > wrong place and is loading the wrong version. Debian doesn't install > its packages into /usr/local/lib so I'm reasonably sure that is the > issue. The question is, how did it get there. If you did an easy- > install as root, it might have placed it there, but, cleaning that is > probably the first step to diagnosing it. > > I believe you can edit easy-install.pth in the /usr/local/lib/ > python2.6/dist-packages directory and possibly remote the > WebHelpers-0.6.4 directory which would remove that library. Make a > backup of that directory first just in case. > > Second, I really would suggest you use a virtual environment for doing > pylons development. This way, when you're developing code or multiple > projects, you don't have a ton of dependencies installed on your main > machine. Projects that you've written that haven't changed can stay > on the same version without fear that the API will change when you do > an apt-get upgrade. > > http://pylonshq.com/docs/en/1.0/gettingstarted/#installing contains > some basic instructions. > > or > > wgethttp://pylonshq.com/download/1.0/go-pylons.py > python go-pylons.py --no-site-packages pylons > cd pylons > source bin/activate > easy_install mysql-python > paster create -t pylons project > cd project > > (edit development.ini to alter the IP address, port, sqlalchemy url, > etc) > > paster serve --reload development.ini > > This creates a subdirectory named pylons whereever you are. Perhaps > you want to use /var/www/pylons or /home/username/pylons as the > location. When you go back to doing development, you cd /var/www/ > pylons, source bin/activate and your environment is modified to run > in a sandbox. Whatever you do in that virtual environment doesn't > affect the main system. apt-get upgrades don't affect your sandbox > either. So, if debian upgrades to a version of software that would > break your project, your virtual environment insulates you from the > system change. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
