Re: [Zope3-dev] zope.i18n dependency in zope.configuration
On 10/22/06, Baiju M [EMAIL PROTECTED] wrote: So any module imported should be added as a dependency. Then, what about modules imported in test files (*.txt or test*.py files) ? Pretty much; there are cases where a package might import something conditionally in order to improve integration, but if it isn't available, the package as a whole can function just fine on its own. In those cases, no dependency should be recorded. Ideally, dependencies of the implementation and the tests should be separated, but we've been treating them as one so far. Moving to eggs should allow improvements along these lines. -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Every sin is the result of a collaboration. --Lucius Annaeus Seneca ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] More eggification: zope.lifecycleevent, zope.location
Hi, Can any please review this: http://svn.zope.org/zope.lifecycleevent/ http://svn.zope.org/zope.location/ zope.location depends on zope.app.component (ISite interface) How to make eggs for zope.app.component ? Any example zope.app.* egg ? 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] More eggification: zope.lifecycleevent, zope.location
On 10/22/06, Baiju M [EMAIL PROTECTED] wrote:
Hi,
Can any please review this:
http://svn.zope.org/zope.lifecycleevent/
http://svn.zope.org/zope.location/
zope.location depends on zope.app.component (ISite interface)
How to make eggs for zope.app.component ?
Any example zope.app.* egg ?
I tried to create one myself, here it is:
ftp://ftp.berlios.de/pub/zissue/z3/zope.app.container.tar.bz2
Here is the setup.py:
import os
try:
from setuptools import setup, Extension
except ImportError, e:
from distutils.core import setup, Extension
setup(name='zope.app.container',
version='3.4-dev',
url='http://svn.zope.org/zope.app.container',
license='ZPL 2.1',
description='Zope app.container',
author='Zope Corporation and Contributors',
author_email='zope3-dev@zope.org',
long_description=Zope app.container,
packages=['zope',
'zope.app',
'zope.app.container',
'zope.app.container.browser',
'zope.app.container.tests',
'zope.app.container.ftests'],
package_dir = {'': 'src'},
ext_modules=[Extension(zope.app.container._zope_app_container_contained,
[os.path.join('src', 'zope', 'app', 'container',
_zope_app_container_contained.c)
], include_dirs=['include']),
],
namespace_packages=['zope.app',],
tests_require = ['zope.testing'],
install_requires=['persistent',
'BTrees',
'zope.interface',
'zope.cachedescriptors',
'zope.event',
'zope.component',
'zope.location',
'zope.traversing',
'zope.publisher',
'zope.exceptions',
'zope.security',
'zope.lifecycleevent',
'zope.schema',
'zope.dottedname',
'zope.size',
'zope.app.broken',
'zope.app.i18n',
'zope.app.dependable',],
include_package_data = True,
zip_safe = False,
)
Any comments/suggestions ?
P.S. sometimes I feel that I am miss using berlios.de . I think ZF web team
can set up a people.zope.org for adding Zope related files.
Other projects has similar servers, people.freedestop.org, people.debian.org,
people.ubuntu.com etc.
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] Zope Configuration Processing and Side Effects
Baiju M wrote: On 10/21/06, Jim Fulton [EMAIL PROTECTED] wrote: At: http://dev.zope.org/Zope3/ZopeConfigurationProcessingAndSideEffects I have added this page to new wiki: http://zope3.zwiki.org/ZopeConfigurationProcessingAndSideEffects Also updated the index, http://zope3.zwiki.org/Zope3Proposals Thanks. Let's use new wiki now onwards. Sooner or later this will be wiki.zope.org We have to make current wiki read only very soon. Could you add a prominent notice to the old wiki telling prople to use the new wiki instead? 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] Representation for Zope at PyCon 2007
PyCon 2007 will be held in Addison (Dallas) from Feb 23 to 25, and we're fast approaching the talk submission deadline of Oct 31. I'd like to encourage talks about Zope, particularly how to get started with Zope and also the new technologies coming out of Zope 3. Information on both of those topics has been in very short supply at PyCons. We're also approaching the deadline, Nov 15, for half-day tutorials taught on Feb 22. Attendees register separately for these and teachers can earn up to $1500 per half-day, depending upon the number of students. The tutorial format would be ideal for getting someone up to speed on either Zope 2 or Zope 3. Teach a basic intro in the morning and advanced material in the afternoon. And if you're nervous about such a commitment, tutorials are a great opportunity to partner with another teacher or class helper. As a longtime advocate of Zope (both 2 and 3) I'd very much like to see extensive coverage this year of getting started with Zope 3. Zope has a PR problem, partly from the immense power that comes with it, and the difficulty in getting your arms around it all. It evokes strong feelings and has a distinct philosophy and design tradeoff that you have to understand before you're productive. And with the recent formation of the Zope Foundation, putting forth your best image and getting new members into the community should be a priority. PyCon is a significant opportunity for the Zope community to evangelize. In the PyCon's I've attended one challenge is breaking Zope down into teaching chunks that can be taught in 30-40 minutes. It is very easy to leave the audience behind in the buzzwords and concepts of Zope. So please don't try to teach all of Zope + Plone in 30 minutes. ;-) ;-) One possible talk I think would fit, would help someone just getting into Zope 3 and I wish someone would tackle is the Zope 3 component architecture - nothing about the web or databases or security. Start with the abstract concept of interfaces and adapters, as exists in the zope/interface package, and then layer on it the idea of registries, as implemented in the zope/component package. And wrap up with the reasons why interfaces are better than abstract base classes and what kind of problems adapters are good at solving, including some _non-abstract_ examples. If you'd like to get involved, check out the following conference pages: http://us.pycon.org/TX2007/CallForProposals http://us.pycon.org/TX2007/CallForTutorials Django and TurboGears will be at PyCon in force; I hope Zope will be too. Jeff Rush PyCon 2007 Co-Chair ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] More eggification: zope.lifecycleevent, zope.location
Baiju M wrote: Hi, Can any please review this: http://svn.zope.org/zope.lifecycleevent/ http://svn.zope.org/zope.location/ zope.location depends on zope.app.component (ISite interface) How to make eggs for zope.app.component ? Any example zope.app.* egg ? I don't have time to look at these, but I'll make some general comments. I think that, at least in the short term, we'll need a zope.app egg that included zope.component. I would define the boundary of the zope.app egg based on the contents of Packages.cfg file in the src/zope/app directory. IMO, we need to make zope.app a namespace package, so that we can package the other packages in zope.app. I think, based on experience over the last release cycle, that moving packages out of zope.app is going to be too disruptive. I'm working on a set of ZCML proposals that will, among other things, allow us to make zope.app a namespace packages. I'll try to get these posted today. 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
Re: [Zope3-dev] Zope Configuration Processing and Side Effects
I should have read on before posting. Please disregard. :) Jim Jim Fulton wrote: Baiju M wrote: On 10/21/06, Jim Fulton [EMAIL PROTECTED] wrote: At: http://dev.zope.org/Zope3/ZopeConfigurationProcessingAndSideEffects I have added this page to new wiki: http://zope3.zwiki.org/ZopeConfigurationProcessingAndSideEffects Also updated the index, http://zope3.zwiki.org/Zope3Proposals Thanks. Let's use new wiki now onwards. Sooner or later this will be wiki.zope.org We have to make current wiki read only very soon. Could you add a prominent notice to the old wiki telling prople to use the new wiki instead? 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] Re: zope.i18n dependency in zope.configuration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fred Drake wrote: On 10/22/06, Baiju M [EMAIL PROTECTED] wrote: So any module imported should be added as a dependency. Then, what about modules imported in test files (*.txt or test*.py files) ? Pretty much; there are cases where a package might import something conditionally in order to improve integration, but if it isn't available, the package as a whole can function just fine on its own. In those cases, no dependency should be recorded. Ideally, dependencies of the implementation and the tests should be separated, but we've been treating them as one so far. Moving to eggs should allow improvements along these lines. Rkght: we should record that using the extra features of eggs[1] (so that the dependency is pulled in, but only if that feature is required). [1] http://peak.telecommunity.com/DevCenter/setuptools Tres - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFO6Kv+gerLs4ltQ4RApfWAJwPsipjprz88WkzOIRVcpuJFcWsogCgkzsA IVZ9I1duQIthrhTMLeR1lGM= =U686 -END PGP SIGNATURE- ___ 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 Configuration Processing and Side Effects
Philipp von Weitershausen wrote: Jim Fulton wrote: At: http://dev.zope.org/Zope3/ZopeConfigurationProcessingAndSideEffects I've written an informational proposal stating the goal for eliminating side effects, other than import, during the first phase of configuration processing and generally minimizing first phase processing. This will lead toward refactoring most existing configuration directives. I don't expect this to be controversial, but comments are welcome. You only mention one example for side effects (putting a global object into a module and using them later), so I presume that the refactorings will mainly be targeting this case. This is really the only case (other than import) that I can think of. I may be forgetting something. Note that I also proposed moving as much processing into actions as possible, to avoid doing unnecessary work when actions are discarded. Do you already have specific plans on how to move the path resolving/validating into the handlers, I don't plan to move it into handlers. I plan t move it into actions. :) But you raise a good point. We were able to simplify handler implementation using schemas to do much error checking upstream of handlers. Now, by actually moving this downstream into the actions, we'll end up putting more work on handler/action implementors. This is a downside of the proposal. I'll note: 1. When we made ZCML use schemas for upstream validation, we made it *much* slower, so this was a mixed blessing. 2. Making it much easier to implement configuration handlers and actions is important when there are many different handlers and actions. This was true when we moved to schema-based configuration but now many of us would like to see a smaller selection of configuration options. Note that we could probably provide some helper functions that provide a similar level of automation downstream. For example, something like: def importGlobal(id, info): Try to import a global object for the given identifier On success, the imported object is returned. On failure, an exception is raised that includes information from the passed configuration info object, such as configuration file name and line number. and how to provide backward compatibility for 3rd-party directives? I don't anticipate doing anything to break old directives, so I don't see a backward compatibility issue. Right now the proposal is quite high-level... Yes, that's true. That's because it simply states a goal. It also proposes that some specific directives be reworked, which should serve to highlight issues/problems if any. 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
Re: [Zope3-dev] Re: zope.i18n dependency in zope.configuration
Tres Seaver wrote: ... Rkght: we should record that using the extra features of eggs[1] (so that the dependency is pulled in, but only if that feature is required). I'm uncomfortable with this feature of eggs. I should voice my discomfort on the distutils-sig list. Extras seem to me to be a rather complicated way to avoid fine-grained eggs. I don't really think the complexity is worth the bother. 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] RFC: Zope Configuration Egg Support
I've created a small proposal to add egg support to zope.configuration: http://zope3.zwiki.org/ZopeConfigurationEggSupport Comments welcome. 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] Re: Zope Configuration Processing and Side Effects
Jim Fulton wrote: At: http://dev.zope.org/Zope3/ZopeConfigurationProcessingAndSideEffects I've written an informational proposal stating the goal for eliminating side effects, other than import, during the first phase of configuration processing and generally minimizing first phase processing. This will lead toward refactoring most existing configuration directives. I don't expect this to be controversial, but comments are welcome. You only mention one example for side effects (putting a global object into a module and using them later), so I presume that the refactorings will mainly be targeting this case. Do you already have specific plans on how to move the path resolving/validating into the handlers, and how to provide backward compatibility for 3rd-party directives? Right now the proposal is quite high-level... Philipp ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] RFC: Loading Configuration from the zope.app Egg
I've created a proposal to deal with eggifying zope.app: http://zope3.zwiki.org/LoadingConfigurationFromTheZopeAppEgg Comments welcome. 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] RFC: ZCML Filtering Support
I've created a proposal: http://zope3.zwiki.org/ZCMLFilteringSupport to support filtering configuration actions based on keywords. Comments welcome. 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
Re: [Zope3-dev] Re: Zope Configuration Processing and Side Effects
On Sunday 22 October 2006 14:21, Jim Fulton wrote: 2. Making it much easier to implement configuration handlers and actions is important when there are many different handlers and actions. This was true when we moved to schema-based configuration but now many of us would like to see a smaller selection of configuration options. I think the desire to have a smaller set of configuration options is due to the fact that a lot of teams work pretty much in a Python developer environment. In the two projects I am involved in, there is a desire to develop high-level configuration directives to allow another audience to do customization and integration. Zope 3 Developers (be it core Python or template integration developers) are a real scarce at this point, so we need to find solutions to make other developers productive without them knowing the dirt about Zope 3. Thus, I would really hate to see ZCML directive creation to become more difficult. But then, you (Jim) said that you want to be BBB, so I am not worried. Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
