I did a quick experiment. When zope.component is not installed, the test works fine, when it is installed, it seems zope.interface tries to use it (instead of whatever approach it uses otherwise - I am no zope expert).
Angelo On May 20, 9:34 am, Chris McDonough <[email protected]> wrote: > Thank you. When I get free I'll try to reproduce. > > > > > > > > Angelo Hulshout <[email protected]> wrote: > >I'll try it later today and let you know whether it installs correctly > >now. > > >As for the zope.component issue, I'll have another look at that as > >well. Somehow (on Windows + Python 3.2), creating a start scaffold and > >then running setup.py test -q results in the error below. > > >====================================================================== > >ERROR: test_my_view (speqs.tests.ViewTests) > >---------------------------------------------------------------------- > >Traceback (most recent call last): > > File "<mypath>\speqs\speqs\tests.py", line 7, in setUp > > self.config = testing.setUp() > > File "<mypath>\SpeqsToolProto1\lib\site-packages\pyramid-1.3.1- > >py3.2.egg\pyramid\testing.py", line 830, in setUp > > have_zca and hook_zca and config.hook_zca() > > File "<mypath>\SpeqsToolProto1\lib\site-packages\pyramid-1.3.1- > >py3.2.egg\pyramid\config\zca.py", line 12, in hook_zca > > from zope.component import getSiteManager > > File "<mypath>\SpeqsToolProto1\lib\site-packages > >\zope.component-3.12.1-py3.2.egg\zope\component\__init__.py", line 21, > >in <module> > > from zope.component.interfaces import ComponentLookupError > > File "<mypath>\SpeqsToolProto1\lib\site-packages > >\zope.component-3.12.1-py3.2.egg\zope\component\interfaces.py", line > >115 > > interface=Interface, name=u'', > > ^ > >SyntaxError: invalid syntax > > >---------------------------------------------------------------------- > >Ran 1 test in 0.062s > > >FAILED (errors=1) > > >Process finished with exit code 1 > >On May 20, 2:19 am, Chris McDonough <[email protected]> wrote: > >> On 05/19/2012 06:31 PM, Chris McDonough wrote: > > >> > I'll investigate the packaging issue. Pyramid does not depend on > >> > zope.component though. > > >> Pyramid 1.3.2 is out that hopefully corrects the packaging issue. > > >> > Angelo Hulshout<[email protected]> wrote: > > >> >> Thankis for that, Chris. > > >> >> A few remarks though: > > >> >> 1) The package contains a directory name "Pyramid (with the leading > >> >> double quote), which blocks installation at least on Windows. > >> >> 2) Creating a starter scaffold works fine, but running the tests > >> >> (setup.py test -q) fails on Python 3.2, because (even the latest) > >> >> zope.component uses old syntax ( name=u'' in a.o. interfaces.py). > >> >> Apart from that, running the scaffold's default server is no problem, > >> >> so unless I missed something a fix for Zope should solve all issues. > > >> >> Angelo > > >> >> On May 19, 3:35 pm, Chris McDonough<[email protected]> wrote: > >> >>> Pyramid 1.3.1 has been released. It is a maintenance release in the > >> >>> 1.3 > >> >>> series. Here's what happened since the last release: > > >> >>> 1.3.1 (2012-05-19) > >> >>> ================== > > >> >>> Bug Fixes > >> >>> --------- > > >> >>> - Add ``REMOTE_ADDR`` to the ``prequest`` WSGI environ dict for > >> >>> benefit of the debug toolbar, which effectively requires it to be > >> >>> present to work properly. > > >> >>> - When an asset specification was used as a Mako ``renderer=`` > >> >>> argument and a ``mako.modules_directory`` was specified, Pyramid > >> >>> would fail to render the template and instead would raise an > >> >>> error > >> >>> when attempting to write the file to the modules directory. > >> >>> Example symptom: ``WindowsError: [Error 267] The directory name > >> >>> is > >> >>> invalid: > > >> >>> 'c:\\docume~1\\chrism\\locals~1\\temp\\tmp9jtjix\\pyramid.tests:fixtures'`` > >> >>> . > >> >>> We now replace the colon in the Mako module filename with a > >> >>> dollar > >> >>> sign, so it can work on Windows. See > >> >>> https://github.com/Pylons/pyramid/issues/512formoreinformation. > > >> >>> - When no authentication policy was configured, a call to > >> >>> ``pyramid.security.effective_principals`` would unconditionally > >> >>> return the empty list. This was incorrect, it should have > >> >>> unconditionally returned ``[Everyone]``, and now does. > > >> >>> - Fix incompatibility with recently released zope.interface 4.0. > >> >>> Symptom: ``TypeError: Class advice impossible in Python3. Use the > >> >>> @provider class decorator instead.`` > > >> >>> The documentation for the 1.3.1 release is available > >> >>> athttp://docs.pylonsproject.org/projects/pyramid/en/1.3-branch/ > > >> >>> You can install 1.3.1 via PyPI: > > >> >>> easy_install Pyramid==1.3.1 > > >> >>> Enjoy, and please report any issues you find to the issue tracker > >> >>> athttps://github.com/Pylons/pyramid/issues > > >> >>> Thanks! > > >> >>> - C > > >> >> -- > >> >> 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 > >> >> athttp://groups.google.com/group/pylons-discuss?hl=en. > > >-- > >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 > >athttp://groups.google.com/group/pylons-discuss?hl=en. -- 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.
