[Grok-dev] Session based auth in Grok 1.1rc1

Jeffrey D Peterson bgpete at gmail.com
Thu Apr 8 08:52:32 EDT 2010

I suspected it wasn't intentional and if the solution was including those I
was ok with that too.  The only thing that threw me is usually you don't
have to and being pretty green with the zope3 ways, it just wasn't obvious
to me.  Live and learn.  On the upside it uncovered and got an issue solved
for the full release, so that is a positive.  

Thanks for all the help!


> -----Original Message-----
> From: grok-dev-bounces at zope.org [mailto:grok-dev-bounces at zope.org] On
> Behalf Of Kevin Teague
> Sent: Wednesday, April 07, 2010 7:21 PM
> To: grok-dev at zope.org
> Subject: Re: [Grok-dev] Session based auth in Grok 1.1rc1
> On Apr 7, 3:21 pm, "Jeffrey D Peterson" <bgp... at gmail.com> wrote:
> > Yeah, I guess I wasn't very clear.  Knowing you have to include these
> and
> > moreover having to include these at all seems counter to the way
> things are
> > generally done in Grok.  I guess I am surprised it's not just grokked
> along
> > with everything else. But if I must, I must.
> >
> > Is this due to it being a release candidate and not a full on
> release?
> >
> Grok only groks your own packages. For packages included with Grok,
> such as zope.pluggableauth, there is no grokking that takes place -
> all of that configuration is loaded explicitly through ZCML. This is
> because historically Zope 3 began life as a ZCML-only creation, and
> those Zope Toolkit packages which Grok uses continue to be used by
> ZCML-only projects, such as existing Zope 3 apps or BlueBream.
> As for why the configuration isn't loaded with everything else - this
> is a bug with 1.1rc1, the previous 1.1 releases didn't use
> zope.pluggableauth, that changeover was recently introduced in 1.1rc1.
> The zope.pluggableauth package wasn't listed in the install_requires
> for the grok package. It was getting included as part of the
> versions.cfg for Grok, so the code was being installed. However, the
> z3c.autoinclude package, which Grok uses to automatically include all
> configure.zcml configuration in all packages specified in the
> install_requires dependencies wasn't being triggered to include the
> zope.pluggableauth configuration, since it wasn't listed. (previously,
> in Zope 3, people had to manually update ZCML files when they
> installed packages ... )
> I've added zope.pluggableauth to install_requires for the setup.py for
> the grok package in SVN on trunk, so the next release candidate of
> Grok 1.1 shouldn't exhibit this bug.
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> https://mail.zope.org/mailman/listinfo/grok-dev

More information about the Grok-dev mailing list