Sorry for bring an old thread back up, but it's relevant.
On Tue, Jan 26, 2010 at 4:06 AM, Souheil CHELFOUH wrote:
> The tests pass and nothing has been changed but the imports.
Actually, the base classes for SessionCredentialsPlugin changed, and
no longer include these:
persistent.Persiste
Hi,
Christian Theune wrote:
> On 01/26/2010 03:30 PM, Souheil CHELFOUH wrote:
>> Well, the first step is already to cut the dependencies and get a sane
>> tree and a reusable package.
>> The second step, however, if people feel like it, will be to refactor
>> a bit and _that_ will need careful pl
On 01/26/2010 03:30 PM, Souheil CHELFOUH wrote:
> Well, the first step is already to cut the dependencies and get a sane
> tree and a reusable package.
> The second step, however, if people feel like it, will be to refactor
> a bit and _that_ will need careful planning, yes.
> But, one thing at a t
Well, the first step is already to cut the dependencies and get a sane
tree and a reusable package.
The second step, however, if people feel like it, will be to refactor
a bit and _that_ will need careful planning, yes.
But, one thing at a time :)
However, I'll polish a bit zope.plugabbleauth and
Hi,
On 01/26/2010 03:02 PM, Jan-Wijbrand Kolman wrote:
> Hi,
>
>
> Just my quick 2 euro cents here:
>
> As far as I can tell, what Souheil did so far is no architectural change, but
> a
> change like so many in the recent past where a zope.app.something package has
> been refactored into a z
Hi,
Christian Theune wrote:
> On 01/26/2010 09:32 AM, Souheil CHELFOUH wrote:
>> I hear you and understand you.
>
> Thanks. :)
>
>> I'm not advertizing for an immediate and brainless action.
>> What I did this week end is simply to split the PAU from all the
>> components provided with it (wel
Hi,
On 01/26/2010 09:32 AM, Souheil CHELFOUH wrote:
> Christian,
>
> I hear you and understand you.
Thanks. :)
> I'm not advertizing for an immediate and brainless action.
> What I did this week end is simply to split the PAU from all the
> components provided with it (well, most of it).
> That
Christian,
I hear you and understand you.
I'm not advertizing for an immediate and brainless action.
What I did this week end is simply to split the PAU from all the
components provided with it (well, most of it).
That was motivated by my current work and by the will to see the
dependencies become
Hi,
On 01/26/2010 09:06 AM, Souheil CHELFOUH wrote:
> Hello,
>
> I took the liberty to start the work by a first simple move :
> splitting apart what is "strictly" about PAU's core and the rest.
> PAU and some plugins have been put in :
> http://svn.zope.org/repos/main/zope.pluggableauth/trunk/
>
Hello,
I took the liberty to start the work by a first simple move :
splitting apart what is "strictly" about PAU's core and the rest.
PAU and some plugins have been put in :
http://svn.zope.org/repos/main/zope.pluggableauth/trunk/
The rest has been kept in:
http://svn.zope.org/repos/main/zope.ap
On 01/22/2010 07:59 PM, Souheil CHELFOUH wrote:
> Hello guys,
>
> I'm coding some stuff, using zope.app.authentication and this package
> appears to do too many things, in my opinion.
> Would it be wise to cut off some of the functionalities ? The pure PAU
> components could go in a dedicated pack
I don't think so. The PAU is quite a big chunk and would really
deserve to live on its own piece of land.
zope.authentication is really about the authentication basics, not all
the pluggability and plugin that PAU brings in.
zope.app.authentication is just too confuse as it defines PAU and a
whole
On Fri, Jan 22, 2010 at 7:59 PM, Souheil CHELFOUH wrote:
> I'm coding some stuff, using zope.app.authentication and this package
> appears to do too many things, in my opinion.
> Would it be wise to cut off some of the functionalities ? The pure PAU
> components could go in a dedicated package, li
Hello guys,
I'm coding some stuff, using zope.app.authentication and this package
appears to do too many things, in my opinion.
Would it be wise to cut off some of the functionalities ? The pure PAU
components could go in a dedicated package, like
zope.pluggableauthservice
The whole handling of pr
On Thu, Aug 14, 2008 at 04:00:22PM -0400, Gary Poster wrote:
> If you use the http://download.zope.org/ppix or
> http://download.zope.org/simple
> indexes and try to get zope.app.authentication 3.4.3 (the newest),
> you will get a 404 error.
>
> Looking at PyPI and the zope.org index, it is
On Thu, 2008-08-14 at 16:00 -0400, Gary Poster wrote:
> If you use the http://download.zope.org/ppix or
> http://download.zope.org/simple
> indexes and try to get zope.app.authentication 3.4.3 (the newest),
> you will get a 404 error.
>
> Looking at PyPI and the zope.org index, it is evident
On Aug 14, 2008, at 4:32 PM, Christophe Combelles wrote:
> Gary Poster a écrit :
>> If you use the http://download.zope.org/ppix or
>> http://download.zope.org/simple
>> indexes and try to get zope.app.authentication 3.4.3 (the newest),
>> you will get a 404 error.
>>
>> Looking at PyPI and the
Gary Poster a écrit :
> If you use the http://download.zope.org/ppix or
> http://download.zope.org/simple
> indexes and try to get zope.app.authentication 3.4.3 (the newest),
> you will get a 404 error.
>
> Looking at PyPI and the zope.org index, it is evident why.
>
> http://pypi.python.or
If you use the http://download.zope.org/ppix or http://download.zope.org/simple
indexes and try to get zope.app.authentication 3.4.3 (the newest),
you will get a 404 error.
Looking at PyPI and the zope.org index, it is evident why.
http://pypi.python.org/pypi/zope.app.authentication/3.4.3 on
Previously Christophe Combelles wrote:
> Marius Gedminas a écrit :
> >Something seems to be wrong with zope.app.authentication 3.4.2 and
> >zope.app.container 3.5.5 eggs:
> >
> >Test-module import failures:
> >
> >Module: zope.app.authentication.tests
> >
> >ValueError: line 13 of the d
Marius Gedminas a écrit :
Something seems to be wrong with zope.app.authentication 3.4.2 and
zope.app.container 3.5.5 eggs:
Test-module import failures:
Module: zope.app.authentication.tests
ValueError: line 13 of the docstring for principalfolder.txt has
inconsistent leading whit
Marius Gedminas wrote:
Ideas? Eggs built on Windows? Missing svn:eol-style=native properties? Mixed
\n and \r\n line endings?
Probably mixed line endings.
It's a shame doctest is so fragile to this...
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://
Something seems to be wrong with zope.app.authentication 3.4.2 and
zope.app.container 3.5.5 eggs:
Test-module import failures:
Module: zope.app.authentication.tests
ValueError: line 13 of the docstring for principalfolder.txt has
inconsistent leading whitespace: '\r'
Module: z
Hi Chritophe
> Betreff: Re: [Zope-dev] zope.app.authentication broken!
[...]
> >> btw, did someone run the tests with all packages that depend on
> >> zope.app.container?
> >
> > I would like to do this. How can I know all the packages
> that depend
&g
Christophe Combelles a écrit :
Roger Ineichen a écrit :
hi
I'm pretty sure the container changes are not compatible because of
some bad __init__ methods in inherited classes in other packages.
But that's not the fault of the refactoring that is correct as far as
I can see.
zope.app.authenti
Roger Ineichen a écrit :
hi
I'm pretty sure the container changes are not compatible because of
some bad __init__ methods in inherited classes in other packages.
But that's not the fault of the refactoring that is correct
as far as I can see.
zope.app.authentication.groupfolder.py
class Gro
hi
I'm pretty sure the container changes are not compatible because of
some bad __init__ methods in inherited classes in other packages.
But that's not the fault of the refactoring that is correct
as far as I can see.
zope.app.authentication.groupfolder.py
class GroupFolder(BTreeContainer):
27 matches
Mail list logo
