[moving to the list because it might be of wider interest]
* Jim Fulton [EMAIL PROTECTED] [2006-09-22 07:27]:
On Sep 22, 2006, at 4:23 AM, Wolfgang Schnerring wrote:
Hi Jim,
Theuni and I refactored zope.decorator and put its contents into
zope.proxy and zope.security, respectively.
The
Philipp von Weitershausen wrote:
Wichert Akkerman wrote:
Previously Philipp von Weitershausen wrote:
Jim Fulton wrote:
Uh, why are we parsing the entries file?
To get the current revision of the Zope 3 checkout...
Why not use svn info --xml?
or even just svn info...
I think we
Previously Dmitry Vasiliev wrote:
Ugh, it was me. I switched ZopeVersion from CSV to SVN, moreover the first
revision (25322) used 're' module to parse .svn/entries and later (41452)
has been switched to use 'xml.dom.minidom'. I think extract information
from .svn/entries is more safe way
Baiju M wrote:
On 9/22/06, Jim Fulton [EMAIL PROTECTED] wrote:
snip
Finally, I'm experimenting with using launchpad for bugs:
https://launchpad.net/products/zc.buildout/+bugs
and feature requests:
https://features.launchpad.net/products/zc.buildout/
So far this is working OK. I
Jim Fulton wrote:
On Sep 22, 2006, at 1:31 PM, Stephan Richter wrote:
On Friday 22 September 2006 12:52, Martijn Faassen wrote:
I hope we can move to a pattern where projects gain a homepage somewhere
on zope.org, including doctests and some other information, and the
cheeseshop is used for
Jim Fulton wrote:
On Sep 22, 2006, at 12:52 PM, Martijn Faassen wrote:
While I'm happy with the way this works now as it's agile, I am also
hoping that eventually we can move away from the cheeseshop as the
prime documentation site of a project; it's not ideally suited for that.
It's not
Wichert Akkerman wrote:
Previously Dmitry Vasiliev wrote:
Ugh, it was me. I switched ZopeVersion from CSV to SVN, moreover the first
revision (25322) used 're' module to parse .svn/entries and later (41452)
has been switched to use 'xml.dom.minidom'. I think extract information
from
Martijn Faassen wrote:
I also consider it very important that we have at least a *list* on
zope.org of zope 3 projects. :)
I'd suggest something that links back to PyPi, like the TurboGears
GogBin: http://www.turbogears.org/cogbin/
--
Benji York
Senior Software Engineer
Zope Corporation
Benji York wrote:
Martijn Faassen wrote:
I also consider it very important that we have at least a *list* on
zope.org of zope 3 projects. :)
I'd suggest something that links back to PyPi, like the TurboGears
GogBin: http://www.turbogears.org/cogbin/
Yes, that may be enough for many of the
Baiju M wrote:
On 9/22/06, Jim Fulton [EMAIL PROTECTED] wrote:
snip
Finally, I'm experimenting with using launchpad for bugs:
https://launchpad.net/products/zc.buildout/+bugs
and feature requests:
https://features.launchpad.net/products/zc.buildout/
So far this is working OK. I
Martijn Faassen wrote:
Benji York wrote:
Martijn Faassen wrote:
I also consider it very important that we have at least a *list* on
zope.org of zope 3 projects. :)
I'd suggest something that links back to PyPi, like the TurboGears
GogBin: http://www.turbogears.org/cogbin/
Yes, that may
Hello,
uh... I just realised that I have messed up. I was going to co the Zope2
trunk but after wondering why it never finished, I discovered that I
somehow managed to co *all* of zope2, including all the branches, etc. :-P
I am not doing that any more. I apologise for any incovenience this may
On Sep 22, 2006, at 7:40 PM, Philipp von Weitershausen wrote:
Jim Fulton wrote:
Uh, why are we parsing the entries file?
To get the current revision of the Zope 3 checkout...
That seems excessive to me. Let's stop.
Jim
--
Jim Fulton mailto:[EMAIL PROTECTED]
On Sep 25, 2006, at 3:25 AM, Wolfgang Schnerring wrote:
[moving to the list because it might be of wider interest]
* Jim Fulton [EMAIL PROTECTED] [2006-09-22 07:27]:
On Sep 22, 2006, at 4:23 AM, Wolfgang Schnerring wrote:
Hi Jim,
Theuni and I refactored zope.decorator and put its contents
Benji York wrote:
Martijn Faassen wrote:
Benji York wrote:
Martijn Faassen wrote:
I also consider it very important that we have at least a *list* on
zope.org of zope 3 projects. :)
I'd suggest something that links back to PyPi, like the TurboGears
GogBin:
Hi,
Jim Fulton wrote:
Yes, now that you mention it. Proxies should be as transparent as
possible. As such, they shouldn't add additional attributes if they can
avoid it. I think it's best to leave things as they are, with a comment
pointing out that the difference is in the version of
On Sep 25, 2006, at 11:04 AM, Christian Theune wrote:
Hi,
Jim Fulton wrote:
Yes, now that you mention it. Proxies should be as transparent as
possible. As such, they shouldn't add additional attributes if
they can
avoid it. I think it's best to leave things as they are, with a
comment
Hi all
How drops the bforest package out of the zope package?
Do we get bforest package back or should we drop the
API doc registration too for bforest too?
Traceback (most recent call last):
File z3.py, line 64, in ?
run()
File z3.py, line 60, in run
main(argv[1:])
File
On Sep 25, 2006, at 12:18 PM, Roger Ineichen wrote:
Hi all
How drops the bforest package out of the zope package?
Do we get bforest package back or should we drop the
API doc registration too for bforest too?
Hm. I ran the tests before checking in the removal.
bforest was added in the
Jim Fulton wrote:
It isn't at the most basic level. Security gets rather difficult if you
let non-fully-trusted people create subscribers.
OK, wasn't specifically worrying about security, but why do you see this
as being an issue?
We already have persistent subscribers now, in a round
Philipp von Weitershausen wrote:
Listen, we were over this.
Apparently, some of us are not ;-)
(and the problems caused by having two repositories for the same piece
of software keep emerging!)
I wrote whole proposal about this months ago
already [1] and it was disputed heavily.
Right,
Jim Fulton wrote:
It would *also* require that we
implement the no side-effects during parsing policy (my other favorite
dead horse in arguments about ZCML's implementation / usage).
Beat away. :) I've been in favor of this for some time. This is
definitely a goal.
Can we have a papal
Martijn Faassen wrote:
configuration. This way, if we grow Python-based configuration or
automatic configuration, the system will still work.
I do care about this, because I hate zcml(tm) but how would you see
disabling working in a python-based config?
cheers,
Chris
--
Simplistix -
Tres Seaver wrote:
How should I do things such that they can do that?
I'm just wondering whether you really need the disabling feature.
I've wanted it. My major beef with the way we are *using* ZCML now is
that we expect package authors to provide policy-laden configuration for
their
Stephan Richter wrote:
This has been proposed and approved, but implementation has been delayed due
to missing XPath features.
http://www.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/ZCMLEnhancements
I like all of the ideas on there, I'm a little confused though.
How much of what
Jim Fulton wrote:
I have a feeling that xpath is overkill.
I wish it was, but I don't think it is..
It alsoi won't work for
actions defined in Python.
Wasn't aware you could do this, where can I find examples?
I'd rather see some sort of identifier system.
But that would mean every
On Sep 25, 2006, at 1:44 PM, Chris Withers wrote:
Jim Fulton wrote:
It would *also* require that we
implement the no side-effects during parsing policy (my other
favorite
dead horse in arguments about ZCML's implementation / usage).
Beat away. :) I've been in favor of this for some
On Sep 25, 2006, at 1:20 PM, Chris Withers wrote:
Jim Fulton wrote:
It isn't at the most basic level. Security gets rather difficult
if you let non-fully-trusted people create subscribers.
OK, wasn't specifically worrying about security, but why do you see
this as being an issue?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
On Sep 25, 2006, at 1:44 PM, Chris Withers wrote:
Jim Fulton wrote:
It would *also* require that we
implement the no side-effects during parsing policy (my other
favorite
dead horse in arguments about ZCML's
29 matches
Mail list logo
