I'll investigate the packaging issue.  Pyramid does not depend on 
zope.component though.

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/512for more information.
>>
>>    - 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 at 
>http://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.

Reply via email to