Not right now "Vlad K." <[email protected]> wrote:
> > >Okay, this helped a lot. Installed Pyramid 1.3.2, upgraded >zope.deprecation back to 4.0.0, zope.interface back to 4.0.0, had also >to upgrade transaction to 1.3.0 (dep of zope.sqlalchemy, which I also >upgraded to 0.7.1). > >The only DeprecationWarning left is from Chameleon 2.8.5. > >Now, this is entirely different issue, but is there a way to disable >Pyramid loading Chameleon at all, if we're not using it? > > >.oO V Oo. > > >On 05/19/2012 03:28 PM, Chris McDonough wrote: >> On 05/18/2012 07:05 PM, Angelo Hulshout wrote: >>> Going back to zope.interface 3.8.0 and zope.deprecation 3.5.1 is also >>> the only way to get Configurator to work on Python 3.2 - what is a >>> deprecation warning on 2.x is an error on 3.x - or so it seems on my >>> systems. >>> >>> On May 18, 1:59 pm, "Vlad K."<[email protected]> wrote: >>>> BTW, seems downgrading zope.intarface to 3.8.0 requires also >>>> zope.deprecation< 4.0.0 , the latest of which is 3.5.1 I think. >>>> >>>> .oO V Oo. >>>> >>>> On 05/18/2012 01:12 PM, Vlad K. wrote: >>> >> >> FTR, I just released zope.sqlalchemy 0.7.1 and Pyramid 1.3.1. These >> include fixes that allow them to work with zope.interface 4.0. >> >> - 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.
