Pyramid 1.3 and zope.component question

67 views
Skip to first unread message

Iain Duncan

unread,
Aug 28, 2012, 12:23:46 AM8/28/12
to pylons...@googlegroups.com
Hey all (or maybe just Chris? ;), I see in the change log that pyramid 1.3 no longer depends on zope.component. I haven't switched to 1.3, but in my pyramid apps I'm using the zca registry pretty extensively.  I'm wondering a few things:

- is the pyramid registry still the zope registry, or has there been a re-implementation? 
- if it's a re-implementation or some other kind of replacement, is it API compatible to some degree?  
- is there anything I need to beware of if I'm using the registry, as long as I'm not getting with the the zope global registry libraries? ie, can I just happily continue my merry way as long as my registry access all comes from request.registry and my zca use is all done through method calls on said registry?
- are there docs about that up anywhere? 

thanks!
Iain

Chris McDonough

unread,
Aug 28, 2012, 12:50:14 AM8/28/12
to pylons...@googlegroups.com
On 08/28/2012 12:23 AM, Iain Duncan wrote:
> Hey all (or maybe just Chris? ;), I see in the change log that pyramid
> 1.3 no longer depends on zope.component. I haven't switched to 1.3, but
> in my pyramid apps I'm using the zca registry pretty extensively. I'm
> wondering a few things:
>
> - is the pyramid registry still the zope registry, or has there been a
> re-implementation?

Still same. The zope component registry code was moved to
zope.interface, so nothing really changed, just where it was imported from.

> - if it's a re-implementation or some other kind of replacement, is it
> API compatible to some degree?
> - is there anything I need to beware of if I'm using the registry, as
> long as I'm not getting with the the zope global registry libraries? ie,
> can I just happily continue my merry way as long as my registry access
> all comes from request.registry and my zca use is all done through
> method calls on said registry?

Nothing has really changed. Just where we import it from.

> - are there docs about that up anywhere?

Nope.

>
> thanks!
> Iain
>
> --
> You received this message because you are subscribed to the Google
> Groups "pylons-devel" group.
> To post to this group, send email to pylons...@googlegroups.com.
> To unsubscribe from this group, send email to
> pylons-devel...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/pylons-devel?hl=en.

Iain Duncan

unread,
Aug 28, 2012, 1:23:27 AM8/28/12
to pylons...@googlegroups.com
On Mon, Aug 27, 2012 at 9:50 PM, Chris McDonough <chr...@plope.com> wrote:
On 08/28/2012 12:23 AM, Iain Duncan wrote:
Hey all (or maybe just Chris? ;), I see in the change log that pyramid
1.3 no longer depends on zope.component. I haven't switched to 1.3, but
in my pyramid apps I'm using the zca registry pretty extensively.  I'm
wondering a few things:

- is the pyramid registry still the zope registry, or has there been a
re-implementation?

Still same.  The zope component registry code was moved to zope.interface, so nothing really changed, just where it was imported from.

Ah, that explains it. Thanks for the quick reply!

Iain

Reply all
Reply to author
Forward
0 new messages