Hi Paul,
Paul Winkler wrote:
But this conflicts with third parties being able to deliver bytecode
instead of source, which is a standard python feature (if not common in
the zope world). Since we can't tell the difference between "stale" and
"we never had source in the first place", deleting byt
Hi,
For our application the standard securitypolicy was fine.
Until today. Now a requirement came up that the object permissions
have to depend _also_ on an object state (the object's property).
As I checked my friend is the zope.app.securitypolicy.zopepolicy.py.
Securitypolicy gets set in the ins
Hi,
Adam Groszer wrote:
> Hi,
>
> For our application the standard securitypolicy was fine.
> Until today. Now a requirement came up that the object permissions
> have to depend _also_ on an object state (the object's property).
> As I checked my friend is the zope.app.securitypolicy.zopepolicy.p
Adam Groszer wrote:
For our application the standard securitypolicy was fine.
Until today. Now a requirement came up that the object permissions
have to depend _also_ on an object state (the object's property).
zc.sharing might be a good fit. You'll have to change the sharing
settings on the
Baiju M wrote:
Hi all,
Since we are going for eggification, it is necessary
to add buildbot support for indiviaul packages.
Generally: yes. The reason being to allow the individual packages to be
self-contained when it comes to development and testing.
Can we make sure 'python setu
On Tue, Oct 10, 2006 at 08:13:23PM -0400, Jim Fulton wrote:
> Paul Winkler wrote:
> >Posting this here because the code in question lives in zope.testing...
> >
> >After accidentally nuking my mxODBCZopeDA installation simply by running
> >"bin/zopectl test" in a zope 2.9 instance, I quickly conclu
Paul Winkler wrote:
> On Tue, Oct 10, 2006 at 08:13:23PM -0400, Jim Fulton wrote:
[...]
> >
> > See: http://www.python.org/pypi/zope.testing#running-without-source-code
>
> Thanks for the pointer.
> AFAICT the current docs confirm my understanding.
> --usecompiled would be useful if I wanted to r
Previously Andrew Bennetts wrote:
> The real problem as you noted in your original message is that there's no way
> to
> distinguish between a pyc file that is only intended to be used as a cache of
> bytecode for a py file, and a pyc file that is intended to be used standalone.
Isn't the existin
Wichert Akkerman wrote:
Previously Andrew Bennetts wrote:
The real problem as you noted in your original message is that there's no way to
distinguish between a pyc file that is only intended to be used as a cache of
bytecode for a py file, and a pyc file that is intended to be used standalone.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
> Wichert Akkerman wrote:
>> Previously Andrew Bennetts wrote:
>>> The real problem as you noted in your original message is that
>>> there's no way to
>>> distinguish between a pyc file that is only intended to be used as a
>>> cache
On Wed, Oct 11, 2006 at 11:43:13PM +0200, Wichert Akkerman wrote:
> Previously Andrew Bennetts wrote:
> > The real problem as you noted in your original message is that there's no
> > way to
> > distinguish between a pyc file that is only intended to be used as a cache
> > of
> > bytecode for a p
On 10/7/06, Jim Fulton <[EMAIL PROTECTED]> wrote:
Fred Drake wrote:
> So whatever the ZF's plans for dealing with zope.org, I think there's
> no way to go wrong with the wikis except by keeping what we have now.
> While it's nice to use a Zope-based solution, I think we need to just
> get a solut
12 matches
Mail list logo
