[Zope3-dev] zope.annotation egg
The dependencies of the zope.annotation egg have been commented out yesterday: http://svn.zope.org/zope.annotation/trunk/setup.py?rev=72691view=log Do you know the reason for this ? A second question on the topic: i am trying to use zope.annotation outside zope app server - so far without success (problems starting at the zope.app.container.contained dependency). Can you confirm it is possible without writing my own IAttributeAnnotatable implementation ? Michael -- http://zope.org/Members/d2m http://planetzope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Buildout default behaviour
Lennart Regebro wrote: I'm testing buildout, and one thing I want is to have several cfgs, one for development, one for staging and one for production. Now, calling one of the configurations buildout.cfg would make it the default. That means that if you just run bin/bildout, it will try to install that configuration. That's fine for installing, but not for updating. If you install it with -c staging.cfg, and then without -c at all, it will try to switch to the buildut.cfg configuration, which is not what you want. Now, a clever way around this ought to be to have no buildout.cfg at all, and therefore no default, right? Nope, because if you run it then, it will create an empty buildout.cfg, and then promptly go around building it. Which has the effect that everything gets UNINSTALLED! That's not what I want as default behaviour. :-) Can we change this to complaining that buildout.cfg doesn't exist instead? Yes. The existing behavior was added primarily to support bootstrapping, where I still think it makes some sense. Could you report this as a bug on: https://bugs.launchpad.net/zc.buildout/+bugs Also, in the future, I'd prefer that general buildout questions be raised on the distutils-sig mailing list, http://mail.python.org/mailman/listinfo/distutils-sig (Questions about zope3-specific recipes would be best asked here.) Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] import failure in zope.app.broken tests
Hi, There is an import failure when running 'python2.4 test.py -s zope.app.broken' I have a fix here: http://zope3.pastey.net/6899 Commit it ? Regards, Baiju M ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] import failure in zope.app.broken tests
Baiju M wrote: Hi, There is an import failure when running 'python2.4 test.py -s zope.app.broken' I have a fix here: http://zope3.pastey.net/6899 Commit it ? or Should I put that `IBroken` in `interfaces.py`? It is only a marker interface and there are no other interfaces specific to that package. Since `IBroken` is still available from `zope.app.broken.broken`, this fix is backward compatible. Regards, Baiju M ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] regex bug in zope/rdb/gadfly/pygram.py ?
Hi, When I run : python2.4 utilities/finddeps.py -m zope.rdb -p I get an error like this: http://zope3.pastey.net/6903 This is the code: pycommentre = r(#.*) pywhiteoutre = r([ \t\r\014]|[\]\n)*%s? % pycommentre pywhiteout = re.compile(pywhiteoutre) If I change the second line like this, the error goes. pywhiteoutre = r([ \t\r\014]|[\\]\n)*%s? % pycommentr I am not sure about the problem/solution, I was just trying to find the dependencies of zope.rdb. Regards, Baiju M ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Correctly sending ObjectModifiedEvents [was SVN: zope.webdav/trunk/src/zope/webdav/ Emit an ObjectModifiedEvent on successfully modifying a property with]
Michael Kerrin wrote: Log message for revision 72694: Emit an ObjectModifiedEvent on successfully modifying a property with the proppatch method. ... +if changed: +zope.event.notify(ObjectModifiedEvent(self.context)) + Just emitting an ObjectModifiedEvent like that is pretty useless, IMO. With this you have no clue - whether the object or the object's annotations were modified - which properties of which schema were modified. The good news is that the ObjectModifiedEvent API actually supports this kind of stuff, you just need to use it: info = Attributes(ITheSchema, 'foo', 'bar', 'blergh') notify(ObjectModifiedEvent(obj, info)) (Attributes is importable from zope.lifecycleevent). Note that the object must not necessarily provide ITheSchema, it could also be that the ITheSchema(obj) adapter was changed (this is useful when sending modified events for annotation adapters like IZopeDublinCore). Unfortunately, not many places in Zope 3 itself are good examples of this. In fact, not even formlib sends this extra information along with the events, something I've been meaning to report and fix. (Thanks for reminding me to do so :)). Philipp -- http://worldcookery.com -- Professional Zope documentation and training Next Zope 3 training at Camp5: http://trizpug.org/boot-camp/camp5 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: zope.annotation egg
Michael Haubenwallner wrote: The dependencies of the zope.annotation egg have been commented out yesterday: http://svn.zope.org/zope.annotation/trunk/setup.py?rev=72691view=log Do you know the reason for this ? I wish I did. The log message is pretty useless, unfortunately. I can only urge committers to answer the Why in their log messages, not (only) the What. Most of us who read the commit messages understand the What, but not always the Why. That's what log messages are for... A second question on the topic: i am trying to use zope.annotation outside zope app server - so far without success (problems starting at the zope.app.container.contained dependency). Can you confirm it is possible without writing my own IAttributeAnnotatable implementation ? Well, we've got plans to make zope.app a namespace package as well and distribute pretty much independent packages like zope.app.container as independent eggs. I hope that this will somewhat alleviate your problem, though perhaps zope.annotation's dependency on zope.app.container should be made optional as well. -- http://worldcookery.com -- Professional Zope documentation and training Next Zope 3 training at Camp5: http://trizpug.org/boot-camp/camp5 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: import failure in zope.app.broken tests
Baiju M wrote: Hi, There is an import failure when running 'python2.4 test.py -s zope.app.broken' I have a fix here: http://zope3.pastey.net/6899 Commit it ? What's causing the failure? And how does your patch fix it? Without this information, it'll be hard for us to comment on them. (The same is true for commit messages). -- http://worldcookery.com -- Professional Zope documentation and training Next Zope 3 training at Camp5: http://trizpug.org/boot-camp/camp5 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Buildout default behaviour
On 2/20/07, Jim Fulton [EMAIL PROTECTED] wrote: That's not what I want as default behaviour. :-) Can we change this to complaining that buildout.cfg doesn't exist instead? Yes. The existing behavior was added primarily to support bootstrapping, where I still think it makes some sense. Could you report this as a bug on: https://bugs.launchpad.net/zc.buildout/+bugs Also, in the future, I'd prefer that general buildout questions be raised on the distutils-sig mailing list, http://mail.python.org/mailman/listinfo/distutils-sig (Questions about zope3-specific recipes would be best asked here.) Sure thing! -- Lennart Regebro: Python, Zope, CPS, Plone consulting. +33 661 58 14 64 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Correctly sending ObjectModifiedEvents [was SVN: zope.webdav/trunk/src/zope/webdav/ Emit an ObjectModifiedEvent on successfully modifying a property with]
Philipp von Weitershausen wrote: Michael Kerrin wrote: Log message for revision 72694: Emit an ObjectModifiedEvent on successfully modifying a property with the proppatch method. ... +if changed: +zope.event.notify(ObjectModifiedEvent(self.context)) + Just emitting an ObjectModifiedEvent like that is pretty useless, IMO. With this you have no clue - whether the object or the object's annotations were modified - which properties of which schema were modified. The good news is that the ObjectModifiedEvent API actually supports this kind of stuff, you just need to use it: info = Attributes(ITheSchema, 'foo', 'bar', 'blergh') notify(ObjectModifiedEvent(obj, info)) (Attributes is importable from zope.lifecycleevent). Note that the object must not necessarily provide ITheSchema, it could also be that the ITheSchema(obj) adapter was changed (this is useful when sending modified events for annotation adapters like IZopeDublinCore). Very interesting - I never even knew you could do this :-) All modifications made by the PROPPATCH will be done via the adapter lookup you just mentioned so it is really nice that this is supported. Unfortunately, not many places in Zope 3 itself are good examples of this. In fact, not even formlib sends this extra information along with the events, something I've been meaning to report and fix. (Thanks for reminding me to do so :)). Thanks for the tip, I will definitely update webdav to use it. Michael ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: import failure in zope.app.broken tests
Philipp von Weitershausen wrote: Baiju M wrote: Hi, There is an import failure when running 'python2.4 test.py -s zope.app.broken' I have a fix here: http://zope3.pastey.net/6899 Commit it ? What's causing the failure? This is the output I am getting when running: python2.4 test.py -s zope.app.broken Running tests at level 1 Test-module import failures: Module: zope.app.broken.tests ImportError: cannot import name IBroken Total: 0 tests, 0 failures, 0 errors Test-modules with import problems: zope.app.broken.tests In broken.py we are importing IAnnotations before IBroken definition So the import cycle is like this: (Pdb) where ... /var/tmp/wa/Zope3trunk/src/zope/app/broken/broken.py(26)?() - from zope.annotation.interfaces import IAnnotations /var/tmp/wa/Zope3trunk/src/zope/annotation/__init__.py(20)?() - from zope.annotation.factory import factory /var/tmp/wa/Zope3trunk/src/zope/annotation/factory.py(21)?() - import zope.app.container.contained /var/tmp/wa/Zope3trunk/src/zope/app/container/contained.py(41)?() - from zope.app.broken.broken import IBroken (Pdb) next ImportError: 'cannot import name IBroken' And how does your patch fix it? In broken.py define IBroken before importing IAnnotations Also I moved the original defintion of IBroken to zope.app.broken.interfaces Regards, Baiju M ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
RE: [Zope3-dev] Re: Broken tests since last checkout
Hi Philipp
Subject: [Zope3-dev] Re: Broken tests since last checkout
Roger Ineichen wrote:
Since the newest Zope3 trunk checkout, some tests are not running.
This tests are based on a custom test layer.
Exception raised:
Traceback (most recent call last):
...
raise ConfigurationError('No registered publisher found '
ConfigurationError: No registered publisher found for (GET/)
Does anybody have any hints why the publisher is missing?
Looks to me something's going wrong when loading
zope.app/configure.zcml. This was refactored recently (you're
now supposed to load zope.app.zcmlfiles/configure.zcml), but
backwards-compatibility should've been provided.
Thanks for the feedback. I changed this earlier. My problem
was, that the new layer concept needs it's own ftesting.zcml
file setup.
Roger Ineichen
_
END OF MESSAGE
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: Broken tests since last checkout
On 20 Feb 2007, at 17:04 , Jamu Kakar wrote: Philipp von Weitershausen wrote: Looks to me something's going wrong when loading zope.app/configure.zcml. This was refactored recently (you're now supposed to load zope.app.zcmlfiles/configure.zcml), but backwards-compatibility should've been provided. FYI, backwards compatibility is broken in revisions beyond r71953. That sucks. Can you describe how exactly backwards compatibility broke? Baiju, I think you were the one who did the refactoring. Can you look after this issue? Thanks. ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: zope.annotation egg
On Feb 20, 2007, at 8:59 AM, Philipp von Weitershausen wrote: Michael Haubenwallner wrote: The dependencies of the zope.annotation egg have been commented out yesterday: http://svn.zope.org/zope.annotation/trunk/setup.py?rev=72691view=log Do you know the reason for this ? I wish I did. The log message is pretty useless, unfortunately. I can only urge committers to answer the Why in their log messages, not (only) the What. Most of us who read the commit messages understand the What, but not always the Why. That's what log messages are for... Agreed. Let me introduce Alex Heavner. Alex is a student who is working with me to try to advance some of the eggification efforts. We're working on trying to get to the point where some of our application buildouts can be built from eggs without using Zope 3 checkouts. In doing this, he's trying to untangle some of the dependencies and commented these in a moment of desperation. This was a mistake that he is aware of an is fixing (or maybe has fixed by now). A second question on the topic: i am trying to use zope.annotation outside zope app server - so far without success (problems starting at the zope.app.container.contained dependency). Can you confirm it is possible without writing my own IAttributeAnnotatable implementation ? Well, we've got plans to make zope.app a namespace package as well and distribute pretty much independent packages like zope.app.container as independent eggs. I hope that this will somewhat alleviate your problem, though perhaps zope.annotation's dependency on zope.app.container should be made optional as well. The dependencies are a bit of a mess. I was working over the weekend on trying to demonstrate how easy it was to use zope.component outside of Zope and was dismayed by the tangle of dependencies. It is going to take some time, patience and dedication to sort these dependencies out. Jim -- Jim Fulton mailto:[EMAIL PROTECTED]Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: [Zope Package Dependencies] This is just an experimental page
I don't know how to interpret this note. Are you suggesting that these should be the dependencies? I don't know what the relevence of the flat is better than nested quote or of the indentation in the list below. (Perhaps that was an accidental result of using tabs. In any case, look at what I did to zope.component. In particular, see the use of extras to try to limit and segment the dependencies. http://svn.zope.org/zope.component/trunk/setup.py?rev=72722view=auto Yes, I've commented some dependencies for the moment because they aren't currently realizable. :( There are a few things to note: - I need zope.component to be easily installable now. :) In particular, for a course I'm teaching at PyCon on Tuesday. - I used a separate test extra to capture test dependencies. - The zcml support currently causes a dependency on all of zope. : ( This makes it impossible to run the tests for the zcml support without a zope checkout. We need to fix this. What do people think of using extras this way? I think it makes a lot os sense for tests. Jim On Feb 20, 2007, at 10:48 AM, BaijuMuthukadan wrote: From Zen of Python (``import this``):: ... Flat is better than nested. Sparse is better than dense. ... = = Package Runtime Dependency Testing Dependency = = zope.annotation - ZODB - setuptools - zope.app.container - zope.component - zope.interface - zope.testing zope.cachedescriptors - zope.testing zope.component- ZODB - zope.configuration - zope.deferredimport - zope.deprecation - zope.event - zope.exceptions - zope.hookable - zope.i18nmessageid - zope.interface - zope.proxy - zope.security - zope.testing zope.configuration- zope.deprecation - zope.i18nmessageid - zope.interface - zope.schema - zope.testing zope.contentprovider - zope.app.pagetemplate - zope.app.testing - zope.component - zope.contentprovider - zope.interface - zope.location - zope.publisher.interfaces - zope.schema - zope.security - zope.tales - zope.testing zope.contenttype - None zope.copypastemove- zope.annotation - zope.app.component - zope.app.container - zope.app.container.tests - zope.app.principalannotation - zope.component - zope.event - zope.exceptions - zope.interface - zope.lifecycleevent - zope.location - zope.testing zope.datetime - None deferredimport- zope.proxy - zope.testing dependencytool- None zope.deprecation - zope.testing zope.documenttemplate - zope.security - zope.security.untrustedpython - zope.structuredtext - zope.testing zope.dottedname - zope.testing zope.dublincore - ZODB - zope.annotation - zope.app.component - zope.app.testing - zope.component - zope.datetime - zope.event - zope.i18nmessageid - zope.interface - zope.lifecycleevent - zope.location - zope.schema - zope.security
[Zope3-dev] Re: zope.annotation egg
Jim Fulton wrote: On Feb 20, 2007, at 8:59 AM, Philipp von Weitershausen wrote: Michael Haubenwallner wrote: The dependencies of the zope.annotation egg have been commented out yesterday: http://svn.zope.org/zope.annotation/trunk/setup.py?rev=72691view=log Do you know the reason for this ? I wish I did. The log message is pretty useless, unfortunately. I can only urge committers to answer the Why in their log messages, not (only) the What. Most of us who read the commit messages understand the What, but not always the Why. That's what log messages are for... Agreed. Let me introduce Alex Heavner. Alex is a student who is working with me to try to advance some of the eggification efforts. We're working on trying to get to the point where some of our application buildouts can be built from eggs without using Zope 3 checkouts. Yay! I think many of us (certainly I) are looking forward to this! A second question on the topic: i am trying to use zope.annotation outside zope app server - so far without success (problems starting at the zope.app.container.contained dependency). Can you confirm it is possible without writing my own IAttributeAnnotatable implementation ? Well, we've got plans to make zope.app a namespace package as well and distribute pretty much independent packages like zope.app.container as independent eggs. I hope that this will somewhat alleviate your problem, though perhaps zope.annotation's dependency on zope.app.container should be made optional as well. The dependencies are a bit of a mess. I was working over the weekend on trying to demonstrate how easy it was to use zope.component outside of Zope and was dismayed by the tangle of dependencies. It is going to take some time, patience and dedication to sort these dependencies out. Agreed, but at least jotting them down is a start. -- http://worldcookery.com -- Professional Zope documentation and training Next Zope 3 training at Camp5: http://trizpug.org/boot-camp/camp5 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] PyCon 2007 web frameworks panel
On Oct 31, 2006, at 8:58 AM, Jim Fulton wrote: Benji York wrote: Titus Brown is putting together a web framework panel for the next PyCon: http://us.pycon.org/TX2007/WebFrameworksPanel. I just stuck my name on this. :) If someone else wants badly to do this, I'm willing to yield. In any case, I'd like to represent some other people's opinions. If anyone wants to send me their answers, I'd be happy to incorporate them into my presentation, with attribution. The Zope community is diverse and I expect many people to have opinions that differ from mine and I'd like to represent them. Some especially juicy areas include ideas about templating and o/r mapping. I think I'll set up a Wiki page to describe some of my ideas and to solicit others. Well, a little late, but: http://wiki.zope.org/zope3/PyCon2007WebPanel Comments and corrections are welcome, although time is very short. :) Jim -- Jim Fulton mailto:[EMAIL PROTECTED]Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] PyCon 2007 web frameworks panel
On Oct 31, 2006, at 1:54 PM, Martijn Faassen wrote: Jim Fulton wrote: Benji York wrote: Titus Brown is putting together a web framework panel for the next PyCon: http://us.pycon.org/TX2007/WebFrameworksPanel. I just stuck my name on this. :) If someone else wants badly to do this, I'm willing to yield. In any case, I'd like to represent some other people's opinions. I'm happy to see you do this. I can't make it to that PyCon, unfortunately. As to representing other people's opinion: Talk about Grok. I mention it. I even mention it positively. Better yet, show Grok code. I can't. I don't Grok Grok [snip] I think I'll set up a Wiki page to describe some of my ideas and to solicit others. Okay, let us know. http://wiki.zope.org/zope3/PyCon2007WebPanel Jim -- Jim Fulton mailto:[EMAIL PROTECTED]Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: PyCon 2007 web frameworks panel
Jim Fulton wrote: On Oct 31, 2006, at 1:54 PM, Martijn Faassen wrote: Jim Fulton wrote: Benji York wrote: Titus Brown is putting together a web framework panel for the next PyCon: http://us.pycon.org/TX2007/WebFrameworksPanel. I just stuck my name on this. :) If someone else wants badly to do this, I'm willing to yield. In any case, I'd like to represent some other people's opinions. I'm happy to see you do this. I can't make it to that PyCon, unfortunately. As to representing other people's opinion: Talk about Grok. I mention it. I even mention it positively. Great :) Better yet, show Grok code. I can't. I don't Grok Grok I tried to explain grok a little on the wiki page. I also adapted the example app (Hello World) to grok. It admittedly doesn't look that much different, except that it requires much less configuration (because like most browser pages, it follows a common default, it's public, has the same name as the class, etc.) I don't know if it helps at such short notice, but I recently prepared a little screencast demonstrating a small grok application: http://www.archive.org/details/grok_todo_part1. This is a 15 minute watch, so perhaps something for the plane ;). http://wiki.zope.org/zope3/PyCon2007WebPanel I also added a note about AJAX. While I'm not an AJAX expert myself, I do like what some Plone folks have come up with. They call it KSS and it works indepedently from Plone on both Zope 2 and Zope 3. It allows you to write AJAX using server-side Python and client-side CSS-like stylesheets. That's probably why I as an AJAX-non-expert like it :). -- http://worldcookery.com -- Professional Zope documentation and training Next Zope 3 training at Camp5: http://trizpug.org/boot-camp/camp5 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: Broken tests since last checkout
Philipp von Weitershausen wrote: On 20 Feb 2007, at 17:04 , Jamu Kakar wrote: Philipp von Weitershausen wrote: Looks to me something's going wrong when loading zope.app/configure.zcml. This was refactored recently (you're now supposed to load zope.app.zcmlfiles/configure.zcml), but backwards-compatibility should've been provided. FYI, backwards compatibility is broken in revisions beyond r71953. That sucks. Can you describe how exactly backwards compatibility broke? Baiju, I think you were the one who did the refactoring. Can you look after this issue? Thanks. Yes, I did that refactoring and the original proposal was from Jim. I couldn't find Jamu Kakar's original reply to zope3-dev list. As Philipp said, can you give more details about how backwards compatibility is broken. This thread is started by Roger Ineichen and his problem was test layer related, see: http://mail.zope.org/pipermail/zope3-dev/2007-February/021786.html Regards, Baiju M ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: [Zope Package Dependencies] This is just an experimental page
Jim Fulton wrote: I don't know how to interpret this note. Are you suggesting that these should be the dependencies? I don't know what the relevence of the flat is better than nested quote or of the indentation in the list below. (Perhaps that was an accidental result of using tabs. I was starting to think about reducing dependencies. I used `src/utilities/finddeps.py` to find dependencies. Later I will classify those dependencies as you said below (install_requires, tests_require and extras_require). That quote is added as motivation for me :) Now I have enough motivation, so I will remove it :) In any case, look at what I did to zope.component. In particular, see the use of extras to try to limit and segment the dependencies. http://svn.zope.org/zope.component/trunk/setup.py?rev=72722view=auto +1 I think we can follow this line. Yes, I've commented some dependencies for the moment because they aren't currently realizable. :( There are a few things to note: - I need zope.component to be easily installable now. :) In particular, for a course I'm teaching at PyCon on Tuesday. This is a requirement for me also for 2nd March at FOSS.NITC : http://www.foss.nitc.ac.in I will be talking about Zope Component Architecture, I have 2 hour time, but the audience may not be Python programmers :( Any advise ? - I used a separate test extra to capture test dependencies. Why we requires these two: tests_require = ['zope.testing'], extras_require = dict( test = ['zope.testing'], ), Let's use 'tests_require' for test requirements and 'extras_require' for other requirements ? - The zcml support currently causes a dependency on all of zope. : ( This makes it impossible to run the tests for the zcml support without a zope checkout. We need to fix this. May be I can help, any pointer to start? What do people think of using extras this way? I think it makes a lot os sense for tests. As I said above, use 'extras_require' for other requirements and 'tests_require' only for test requirements? Regards, Baiju M ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Remove src/zope/annotation/setup.py
Hi, Please remove src/zope/annotation/setup.py from here: svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/annotation/setup.py It's already added to svn://svn.zope.org/repos/main/zope.annotation/trunk/setup.py Regards, Baiju M ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Zope 3 added to ohloh.net
Hi, Few days back I found that Zope 2, Plone, Schooltool etc. are already added to ohloh.net So, I just added Zope 3 here: http://www.ohloh.net/projects/4495 This is the Ohloh Summary: * Very large, active development team http://www.ohloh.net/projects/4495/factoids/79432 * Mature, well-established codebase http://www.ohloh.net/projects/4495/factoids/79433 * Declining development activity http://www.ohloh.net/projects/4495/factoids/79434 1558 files still using Zope Public License 2.0, should we change it to ZPL 2.1 ? You can edit details about the project. Let's use http://cia.navi.cx/ also ? I think this will be really useful, especially their IRC bot. Regards, Baiju M ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
