Re: Pyramid 1.3 DeprecationWarning

[Vlad K.]

On 05/18/2012 10:53 AM, Brian Sutherland wrote: Try sticking to zope.interface 3.8.x for now: http://pypi.python.org/pypi/zope.interface Okay, yeah, Pyramid's setup.py says zope.interface >= 3.8.0, I guess that's safe then. Thanks for pointing that out. However I've just noticed another problem. Having piped stderr to devnull to avoid cron scripts mailing deprecation warnings, I didn't see another problem, only to find out later that my scripts weren't working. Traceback (most recent call last): File "src/scripts/gateway_export.py", line 19, in <module> from sqlalchemy.orm import subqueryload File "build/bdist.linux-i686/egg/sqlalchemy/__init__.py", line 52, in <module> File "build/bdist.linux-i686/egg/sqlalchemy/types.py", line 33, in <module> except NameError: File "build/bdist.linux-i686/egg/sqlalchemy/processors.py", line 98, in <module> File "build/bdist.linux-i686/egg/sqlalchemy/cprocessors.py", line 7, in <module> File "build/bdist.linux-i686/egg/sqlalchemy/cprocessors.py", line 4, in __bootstrap__ File "/home/rm/virtualenv/lib/python2.6/site-packages/setuptools-0.6c11-py2.6.egg/pkg_resources.py", line 882, in resource_filename File "/home/rm/virtualenv/lib/python2.6/site-packages/setuptools-0.6c11-py2.6.egg/pkg_resources.py", line 1351, in get_resource_filename File "/home/rm/virtualenv/lib/python2.6/site-packages/setuptools-0.6c11-py2.6.egg/pkg_resources.py", line 1373, in _extract_resource File "/home/rm/virtualenv/lib/python2.6/site-packages/setuptools-0.6c11-py2.6.egg/pkg_resources.py", line 962, in get_cache_path File "/home/rm/virtualenv/lib/python2.6/site-packages/setuptools-0.6c11-py2.6.egg/pkg_resources.py", line 928, in extraction_error pkg_resources.ExtractionError: Can't extract file(s) to egg cache The following error occurred while trying to extract file(s) to the Python egg cache: [Errno 13] Permission denied: '//.python-eggs' The Python egg cache directory is currently set to: //.python-eggs Perhaps your account does not have write access to this directory?  You can change the cache directory by setting the PYTHON_EGG_CACHE environment variable to point to an accessible directory. Of course, adding export PYTHON_EGG_CACHE="/home/rm" to the common bootstrap script for all cron scripts (that also sources virtualenv) fixed the problem. But I'd like to know what changed between my old virtualenv (established for Pyramid 1.2.1) and this new one. Both have been installed exactly the same way: cd /home/rm virtualenv --no-site-packages virtualenv (fetch source from git repo) source virtualenv/bin/activate python setup.py develop Plus, this //.python-eggs looks like something's missing between two / /. And yeah, I should use setup.py console_scripts section and make the scripts properly, based on initdb example in the sqlalchemy template, with commands installed in virtualenv's bin because what I have now is relic cobbled together since Pyramid 1.1 days :) .oO V Oo. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.