Re: [Zope-dev] Subversion externals versus mirroring
What about upgrading server to 1.6. Subversion 1.6 has many new features. From http://subversion.tigris.org/svn_1.6_releasenotes.html : * Improved handling of authentication data * Repository root relative URLs * Improvements to svn:externals * Detection of tree conflicts * Filesystem storage improvements * Ctypes Python Bindings * Improved interactive conflict resolution * Sparse directory exclusion * Logging support for svnserve * New public HTTP URI syntax for examining history * Command-line client improvements * API changes, improvements, and much language bindings work * More than 65 new bug fixes, enhancements Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.12.0a2 released
On Thu, Apr 23, 2009 at 12:27 PM, Tres Seaver tsea...@palladion.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Jung wrote: Am 19.04.2009 um 10:52 schrieb Andreas Jung: Supported, documented and recommended installation methods should be - virtualenv + easy_install (see above) I just released http://pypi.python.org/pypi/zope.z2release/0.1 that allows us to build an Zope 2 related index based on the versions.cfg file of the Zope 2 package. Easy_installing becomes pretty easy using this approach: virtualenv foo cd foo source bin/activate bin/easy_install -i http://some.url/index/2.12.0a3 Zope2 - - The 'source bin/activate' part should be unnecessary (I never use it, and I use *lots* of virtualenvs). - - I propose the following for the index URL: http://download.zope.org/Zope2/index/2.12.0a3 What about dropping that index from URL, like this: http://download.zope.org/Zope2/2.12.0a3 Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] z3c.javascript license question
On Fri, Apr 17, 2009 at 2:48 PM, Tres Seaver tsea...@palladion.com wrote: [snip Now that the copyrights are transferred to the Zope Foundation, essentially *nobody* can check in non-ZPL code, without a special exemption from the ZF board or its delegate (nobody is yet appointed to handle this). BTW, there is an exemption for this area: http://svn.zope.org/repos/main/non-zpl-doc-resources/ (It was created when I asked for adding some resource file for buildout.org) From the readme file: Non-ZPL documentation resources can be checked into this directory if you have received explicit permission from the Zope Foundation to do so. The workflow currently is simply to mail Martijn Faassen (faas...@startifact.com) with a description of what you want to do. In order to use these documentation resources in your own sphinx project, create a subdirectory here and an svn:external to that subdirectory from the sphinx project in question. -- Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] who wants to maintain Zope 3?
On Fri, Apr 10, 2009 at 11:33 AM, Martijn Faassen faas...@startifact.com wrote: Hi there, Is anyone interested in maintaining Zope 3? With Zope 3 I mean: * the thing with the ZMI - do you care about the ZMI? * the thing that can be installed as a particular development platform - do you care about the installation story for Zope 3? (as opposed to Grok or your own application's?) * the thing that has some kind of documentation website - do you care about providing documentation for Zope 3 as opposed to documentation for Grok or individual libraries? People who are interested in these aspects please speak up, so we can figure out what this all means for the future of Zope 3. If nobody is interested, we should perhaps stop talking about it entirely. If people are just interested in the ZMI, perhaps we should form a ZMI project. What I'm *not* talking about is: * maintaining, documenting and installing Grok. * maintaining and documenting any particular Zope Toolkit library (outside of those bits that do ZMI-stuff, those aren't supposed to be in the toolkit) We know people are interested in doing all that. Does Zope Tookit support building a web application out of the box without relying on Grok, Zope 2 or any other framework ? (I am Ok to use a Buildout for building application from Zope Toolkit packages) If the answer to this question is No, then I am interested to maintain the packages necessary to create a simple application out of the box. This is just an academic interest :) Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] naming Zope
On Wed, Apr 8, 2009 at 10:54 AM, Shane Hathaway sh...@hathawaymix.org wrote: Martijn Faassen wrote: If we don't call Zope Framework 4.0, we'll be fine. We should call its first release 1.0 and there's no implication of a progression. +1 on calling it Zope Framework 1.0. We need the people who have been burned by past Zope releases to take another look, because we believe Zope is finally getting simpler. Those people would assume Zope-anything 4.0 is just piling on more complexity, while a version 1.0 release would invalidate that assumption and suggest they take another look. +1 for Zope Framework 1.0 Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zope.app.generations/trunk/src/zope/app/generations/README.txt made blocks consistent
On Mon, Apr 6, 2009 at 11:56 AM, Benji York be...@zope.com wrote: On Mon, Apr 6, 2009 at 11:47 AM, Baiju M mba...@zeomega.net wrote: On Mon, Apr 6, 2009 at 12:46 AM, Michael Howitz m...@gocept.com wrote: Am 05.04.2009 um 22:00 schrieb Baiju M: In reStructuredText, I think two colons :: is required to make it source text ? No, double colons mark literal blocks [1]. Doctest blocks are marked by at the beginning of the line. [2] [1] http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#literal-blocks [2] http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#doctest-blocks Why we cannot use literal blocks for source code ? From the above documentations, I can see that it works for doctest. And we have used it in many places. Also in PyPI (long_description), it looks better. Please see http://mail.zope.org/pipermail/zope-dev/2008-August/033010.html So we should not use either single colon (:) or indent doctest ? Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] setuptools dependency for zope.interface (was Re: [Checkins] SVN: zope.interface/trunk/src/zope/__init__.py 'setuptools' is not a dependency, reverting r97875)
Hi,
I am sorry, I made a mistake in the beginning of this month by removing
the fall-back import of 'pkgutil' from zope.interface
And this is made into 3.5.1 release, so it will a break for those who
don't have 'setuptools' installed. I have reverted that change now.
Can anyone give me access to PyPI entry or make a new release.
My PyPI ID is 'baijum'.
BTW, should we make 'setuptools' as a dependency for 'zope.interface'
Regards,
Baiju M
On Sat, Mar 28, 2009 at 3:11 PM, Baiju M baiju.m.m...@gmail.com wrote:
Log message for revision 98434:
'setuptools' is not a dependency, reverting r97875
Changed:
U zope.interface/trunk/src/zope/__init__.py
-=-
Modified: zope.interface/trunk/src/zope/__init__.py
===
--- zope.interface/trunk/src/zope/__init__.py 2009-03-28 16:58:29 UTC (rev
98433)
+++ zope.interface/trunk/src/zope/__init__.py 2009-03-28 20:11:50 UTC (rev
98434)
@@ -1 +1,7 @@
-__import__('pkg_resources').declare_namespace(__name__)
+# this is a namespace package
+try:
+ import pkg_resources
+ pkg_resources.declare_namespace(__name__)
+except ImportError:
+ import pkgutil
+ __path__ = pkgutil.extend_path(__path__, __name__)
___
Checkins mailing list
check...@zope.org
http://mail.zope.org/mailman/listinfo/checkins
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] PyCon?
I reached here today morning, now attending some tutorials. I am stying in Hyatt with my colleague. Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Please use launchpad bugtracking/blueprints more
On Wed, Mar 25, 2009 at 10:52 AM, Sidnei da Silva sidnei.da.si...@canonical.com wrote: Hi Martijn, On Wed, Mar 25, 2009 at 11:54 AM, Martijn Faassen faas...@startifact.com wrote: One question is what launchpad project we should use. The current launchpad is for Zope 3. The steering group isn't about Zope 3. It's about a whole bunch of libraries. Creating a separate launchpad project for each library in the framework seems like a bit of overkill at this stage, though it would please those people who come at us at the perspective from libraries the most. It smells like 'Zope Framework' (zope-framework) should be a Project Group then, and there should be a 'Zope Steering Group Project' (zope-steering-group-project) as part of it, and sibling of Zope 3 and any other libraries that are part of Zope Framework. If possible, I think it is better to rename current 'zope3' as 'zope-framework', then create another 'zope3' project. So that we will get all bugs and blueprints as part of 'zope-framework'. Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Please use launchpad bugtracking/blueprints more
On Wed, Mar 25, 2009 at 12:16 PM, Sidnei da Silva sidnei.da.si...@canonical.com wrote: On Wed, Mar 25, 2009 at 1:49 PM, Baiju M mba...@zeomega.net wrote: If possible, I think it is better to rename current 'zope3' as 'zope-framework', then create another 'zope3' project. So that we will get all bugs and blueprints as part of 'zope-framework'. If 'zope-framework' is a project group containing 'zope3', you would already get that. See: https://bugs.launchpad.net/chameleon-template-engine https://bugs.launchpad.net/lazr But making 'zope3' as a part of 'zope-framework' is not not good idea. Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Namespace declaration using pkgutil vs pkg_resources
Hi All,
Now we have 'setuptools' as a dependency for all packages.
(I guess this is to make Buildout happy ?)
So, it is certain that 'pkg_resources' module will be always
available as it is bundled with 'setuptools'. If that is the case,
why do we need a fall-back import of 'pkgutil' to declare
a namespace package?
So instead of:
try:
import pkg_resources
pkg_resources.declare_namespace(__name__)
except ImportError:
import pkgutil
__path__ = pkgutil.extend_path(__path__, __name__)
Just this line would be enough to declare a namespace:
__import__('pkg_resources').declare_namespace(__name__)
Am I missing something ?
Regards,
Baiju M
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Namespace declaration using pkgutil vs pkg_resources
On Wed, Mar 11, 2009 at 10:56 PM, Zvezdan Petkovic zvez...@zope.com wrote: On Mar 11, 2009, at 10:29 AM, Martijn Faassen wrote: Since Jim says you're not missing something, I'm going to add to the Zope Framework Steering Group decisions that this is enough and we could clean up __init__.py's to this if we would want to. So, let me try to understand the decision process here: 1. The extras_require is banned to enable building with regular distutils. extras_require is _not_ banned yet. There is no such decision here: http://docs.zope.org/zopeframework/steeringgroup/decisions.html Though I can see this: We can consider removing extra dependencies for particular Zope Framework packages in order to make the dependency graph easier to reason about. We will do this on a case by case basis though. 2. pkgutil is now banned which will prevent regular distutils from working properly. 'setuptools' is a hard-dependency for all packages now, without removing that, there is no point in keeping that fall-back import of 'pkgutil'. Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Namespace declaration using pkgutil vs pkg_resources
On Thu, Mar 12, 2009 at 12:52 AM, Shane Hathaway sh...@hathawaymix.org wrote:
Martijn Faassen wrote:
Since ``setuptools`` is a dependency of our packages anyway, we
can instead do the following::
__import__('pkg_resources').declare_namespace(__name__)
Feel free to use that and also feel free to simplify existing
``__init__.py`` modules. Just make sure ``setuptools`` is a declared
dependency of the package.
Nit: In this case, two lines are better than one.
import pkg_resources
pkg_resources.declare_namespace(__name__)
There's no need to use the lesser known __import__ function when an
ordinary import statement will do.
Actually three lines will be required to replace that single line:
import pkg_resources
pkg_resources.declare_namespace(__name__)
del(pkg_resources)
BTW, I am +1 for single line __import__ approach.
Regards,
Baiju M
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] the Zope Framework project
On Wed, Mar 4, 2009 at 2:34 PM, Hermann Himmelbauer du...@qwer.tk wrote: [snip] - I think, Zope 3 is not only about some seperate packages, but about a complete programming experience. Thus there needs to be some integrating force, that draws together all these packages, writes some documentation / tutorial / website etc. +1 I believe packages developed as part of the Zope 3 project is here to stay for a long time (of course, after dependency cleanup some of them may become obsolete). This will happen even if some of the frameworks based on it are no more available. Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] the Zope Framework project
On Wed, Mar 4, 2009 at 9:55 PM, Martijn Faassen faas...@startifact.com wrote: [snip] The steering group isn't intended to take a responsibility for the entirety of the Zope software. Zope 2, Grok and the Zope 3 app server (which would be a distinct entity) would manage themselves and the Zope Framework steering group would not have a say over the libraries and configuration they add. [snip] I do also think that we should go to a smaller set of libraries. We currently share a huge amount of code that only one consumer actually uses. For instance, I think all of the zope.app.* packages which contain ZMI code can eventually be left to the management of the Zope 3 developers, meaning they'd not be part of the Zope Framework anymore. [snip] As a service to the users of the Zope Framework, the Zope developers also make available lists of version numbers of core libraries that have been tested to work together as a Known Good Set. This receives a version number and is the Zope Framework release. Users of the Zope framework can use this list, but may also diverge from it where they see fit. Other projects (such as the Zope 3 application server and the Grok project) also have a Known Good Sets that expand on the Zope framework list (and may diverge from it). Each of these consumer projects can of course have their own release process, schedule and version numbering. [snip] It may very well be true that in some time we'll develop clusters of libraries that can be more or less managed on their own. The ZMI is such a cluster that I hope will eventually emerge (and that the Zope Framework Steering Group doesn't care about directly). That'd reduce the coordination overhead. But sometimes we do need to take coordinated action, and I don't see that need disappearing entirely. I think those who care about Zope 3 (framework/app server/libraries/ or whatever) should form a team and mailing list to discuss about the future development. All other major consumers of the Zope Framework Project has their on mailing list for discussions. I guess very soon zope-dev list will become inappropriate to discuss about Zope 3. Just like Grok,Repoze etc. it is better to create a list for Zope 3, may be re-activate zope3-dev list to discuss about the Zope 3 (framework/app server/libraries/ or whatever). Well, if no one cares about Zope 3, let's leave it. Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Dependency of zope.deprecation in zope.configuration
Hi, zope.deprecation is used in zope.configuration *only* to turn off deprecation warning when accessing attribute of an object in one place. But there is no test case or comment about when such a warning will occur. I have pasted the relevant code here: def resolve(self, dottedname): Resolve a dotted name to an object. try: zope.deprecation.__show__.off() obj = getattr(mod, oname) zope.deprecation.__show__.on() return obj except AttributeError: zope.deprecation.__show__.on() # No such name, maybe it's a module that we still need to import try: return __import__(mname+'.'+oname, *_import_chickens) except ImportError: if sys.exc_info()[2].tb_next is not None: # ImportError was caused deeper raise raise ConfigurationError( ImportError: Module %s has no global %s % (mname, oname)) Can anyone point the reasoning behind turning off deprecation warning there. What kind of deprecation is expected, and why it should not be displayed ? Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Dependency of zope.deprecation in zope.configuration
On Thu, Mar 5, 2009 at 11:26 AM, Tres Seaver tsea...@palladion.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Baiju M wrote: Hi, zope.deprecation is used in zope.configuration *only* to turn off deprecation warning when accessing attribute of an object in one place. But there is no test case or comment about when such a warning will occur. I have pasted the relevant code here: def resolve(self, dottedname): Resolve a dotted name to an object. try: zope.deprecation.__show__.off() obj = getattr(mod, oname) zope.deprecation.__show__.on() return obj except AttributeError: zope.deprecation.__show__.on() # No such name, maybe it's a module that we still need to import try: return __import__(mname+'.'+oname, *_import_chickens) except ImportError: if sys.exc_info()[2].tb_next is not None: # ImportError was caused deeper raise raise ConfigurationError( ImportError: Module %s has no global %s % (mname, oname)) Can anyone point the reasoning behind turning off deprecation warning there. What kind of deprecation is expected, and why it should not be displayed ? Stephan added that code in revision 29143, four years ago now. He actually added the deprecation framework in that same revision. I would rip it out and see what warnings happen during a big test run: suppressing them doesn't look like a good plan to me. How to run these kind of big test run now-a-days, any pointer ? Thanks, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zope.file/trunk/ Update package mailing list address. Remove zpkg stuff.
On Tue, Mar 3, 2009 at 2:35 PM, Dan Korostelev nad...@gmail.com wrote: 2009/3/2 Tres Seaver tsea...@palladion.com: -include package=zope.file/ I believe people still use the ZCML slug files like the above. They certainly aren't related to 'zpkg'. The intent of the slugs was to allow for something like 'sites-available' / 'sites-enabled' (the pattern in a stock Debian Apache2 install). I think it is particularly unfortunate to remove support for explicit, granular configuration at the same time as folks seem to be jumping to implicit (aka majyk) tools. Please revert this part of the change. I just reverted the change, however, I don't think that the slug files are useful anymore. I cannot see similar slugs in other packages either. -- Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] the Zope Framework project
On Mon, Mar 2, 2009 at 10:41 PM, Chris McDonough chr...@plope.com wrote: - focusing on externalizing software; each egg should stand on its own as something that a non-Zope person would be able to understand and use in isolation. This means documentation for each thing, as well as a sane dependency graph. This is *less* about giving this collection of software a group name (the zope framework) and more about making people *forget* that it is a part of some larger thing. When a piece of software does not have a purpose in isolation but still lives in its own egg, kill it off and merge it back into whatever thing its most closely related to. +1 - Stop trying to version control and treat all this software in some overall release. Let each piece of software have its own life. Likewise if a piece of software does not have its own life, kill it. +1 I think this is how Zope 3 packages are evolving now. Every package (library/framework) should be possible to release individually. Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: Zope/trunk/README.txt The zope-lice...@zope.org address is bouncing.
Can anyone please verify this change. As it is related to license, I thought just get confirmation from here. Regards, Baiju M On Thu, Feb 26, 2009 at 4:58 PM, Baiju M baiju.m.m...@gmail.com wrote: Log message for revision 97294: The zope-lice...@zope.org address is bouncing. So, replaced it with zope-dev@zope.org Changed: U Zope/trunk/README.txt -=- Modified: Zope/trunk/README.txt === --- Zope/trunk/README.txt 2009-02-26 11:23:12 UTC (rev 97293) +++ Zope/trunk/README.txt 2009-02-26 11:28:04 UTC (rev 97294) @@ -21,7 +21,7 @@ --- The Zope License is included in ``ZopePublicLicense.txt``. Send your -feedback about the license to zope-lice...@zope.org. +feedback about the license to zope-...@zope.org. Bug tracker --- ___ Checkins mailing list check...@zope.org http://mail.zope.org/mailman/listinfo/checkins ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.publisher dependencies
On Wed, Feb 25, 2009 at 12:39 PM, Lennart Regebro rege...@gmail.com wrote: On Wed, Feb 25, 2009 at 04:05, Shane Hathaway sh...@hathawaymix.org wrote: Stephan Richter wrote: On Tuesday 24 February 2009, Shane Hathaway wrote: Brainstorming deeper: we could apply a naming convention where the specification package is named with the suffix spec, so zope.location would be split into zope.location and zope.locationspec. what about zope.ilocation? Maybe. I'd lean toward zope.locationspec because it would appear right after zope.location in a sorted list, making it more apparent that they are related. zope.location.interfaces? This will not make any change in dependency graph unless zope.location become a namespace package. -- Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zopeproject and KGS
Hi, What about using zope 3.5 development KGS in the trunk of zopeproject ?. To maintain zopeproject 0.4.2, we can create 0.4 branch. Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] GSOC 2009
On Fri, Feb 13, 2009 at 12:59 PM, Adam GROSZER agros...@gmail.com wrote: Hello, There are rumours that Google kicked off the 2009 Summer of Code. Anyone knowing further details? Any chance for us to take part again? They published FAQ here (announced in list): http://code.google.com/opensource/gsoc/2009/faqs.html Important dates are also given, from March 9th onwards mentoring organization can start submitting applications. Let's move this discussion to g...@zope.org list. I have CCed to that list. Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] opensp...@pycon 2009 about Zope/Repoze/Grok/Deliverence etc.
I am also coming to PyCon this year :) Is there any plan for Zope sprint ? /me was never been outside India. Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] opensp...@pycon 2009 about Zope/Repoze/Grok/Deliverence etc.
On Tue, Feb 10, 2009 at 6:07 PM, Lennart Regebro rege...@gmail.com wrote: On Tue, Feb 10, 2009 at 13:32, Baiju M mba...@zeomega.net wrote: Is there any plan for Zope sprint ? Nothing official yet, but I'm sure there will be sprinting done. There seems to be more Zope people this year than last. There was talk about having a security sprint at PyCon, but after security seemed to be in a good state already that petered out, I think. We can announce a Big Fat Zope sprint and put up a wiki page for that too, and people can add topics they want to sprint on. Could be a good idea? It looks like this time there are few formalities to arrange a sprint: http://us.pycon.org/2009/sprints/call-for-projects/ Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Syntax error in python2.6
How did you change it ? If you change with there, it may break backward compatibility, I am afraid. Regards, Baiju M Bristow Thankachan wrote: Thank you for the quick response. I made the change and got the syntax error corrected. with regards Bristow. On Mon, Jul 21, 2008 at 4:57 PM, Tino Wildenhain [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Bristow Thankachan wrote: Hi everybody, During the porting of Zope2 to Python2.6, I am stuck with a syntax error in the module AccessControl, which is given below. def reorder(s, with=None, without=()): ^ SyntaxError: invalid syntax in line 56 of /home/zope/ztrunk26/lib/python/RestrictedPython/Utilities.py. The same code when run in python2.4 and python2.5 didn't give any syntax errors. Can anybody suggest the reason for this syntax error in python2.6. I'd say, with is now a keyword. http://docs.python.org/ref/keywords.html btw, shouldn't this already give a warning in 2.5? Cheers Tino ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] import error in python2.6
Bristow Thankachan wrote: Hi all, During the porting of Zope2, I am stuck with import errors in many modules. The same code works well in python2.5 and 2.4. Can anybody give the details of this import error in python2.6 and how to get the error corrected? Please provide details about failure. Please don't send these kind of mails to python-dev list, this will be off-topic there. Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.container 3.5.4 bugfix release
- Christophe Combelles [EMAIL PROTECTED] wrote: Baiju M a écrit : - Christophe Combelles [EMAIL PROTECTED] wrote: I've added a tag for the 3.5.4 bugfix release of zope.app.container. Could someone please add me on the owners list on pypi so that I can upload it? Your PyPI ID ? ccomb Done. -- Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Buildout site
Hi all, Few weeks back Buildout site become live, Jens Vagelpohl setup the site at http://buildout.zope.org/ But I couldn't work further on the site. If anyone want contribute to the content please add it here: svn co svn://svn.zope.org/repos/main/buildout-website/trunk/ Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.container 3.5.4 bugfix release
- Christophe Combelles [EMAIL PROTECTED] wrote: I've added a tag for the 3.5.4 bugfix release of zope.app.container. Could someone please add me on the owners list on pypi so that I can upload it? Your PyPI ID ? -- Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] status of buildout.zope.org
Martijn Faassen wrote: Hi there, So, what's the status of buildout.zope.org? It's not up and running yet. What's holding it up? Can I do something to help? (I won't actually do anything about the content or layout, but I can talk to people if it's somehow blocked) We are still working on it. A site with content basic design will be ready by next week. I mean, the initial site doesn't need to be much more work than, say, asking Rene Dudfield for permission to reuse his recent blog entry and dropping into some website with a reasonable layout, and then telling people what to do if they want to add content. http://renesd.blogspot.com/2008/05/buildout-tutorial-buildout-howto.html There's plenty of good content on buildout available, just gather it and put it into a single site. I will post details about adding content soon after the site is up and running. Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Heads up - package lost on pypi!
Roger Ineichen wrote: Hi all The z3c.configurator package is gone on PyPi. Does sombody know what's happen? And more important, how can we recover this? AFAIK, only owners can delete it. May be deleted by an owner by mistake. I am not sure whether we can recover it. Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] paver: buildout is utterly doomed
Martijn Faassen wrote: Hi there, I just found out about this site: http://www.blueskyonmars.com/projects/paver/ I know that the author has used buildout in the past. He apparently decided to roll his own. I have no idea what the technical qualities of paver are. To get your attention, let me spell out a strongly worded and opinionated message nonetheless: zc.buildout is toast. It's on the way out now. Paver is going to compete it away and buildout is doomed to be a niche project only used by weird zope people. That's strongly worded. I'll admit it's drastically overstated. It's based on virtually no technical information! But that's exactly how many programmers will judge the projects: on community aspects, and not primarily technical. Paver has this in its favor: * Paver actually has a nice website that speaks to Python programmers of simplicity. zc.buildout has cheeseshop page with a lot of doctest documentation people have said was hard to understand. (including the author of paver!) * the author is well connected in the Python community. I'd say TurboGears and Pylons people are likely to go for Paver. * it's *already* showing up on programmer's sites like programming.reddit.com, where I just found it. Nobody bothers to link to buildout, as there's no easily digestable message about it available. So, I fear very much that this, or some other alternative, will wash away the undoubtedly more feature-rich and technically robust zc.buildout, if buildout doesn't present itself better. Without better presentation, fast, buildout is doomed to be a Zope-specific thing forever. You Can Save Buildout! So, who is up to make a nice clean looking website and a few tutorials for buildout? It needs a website. Buildout has been around for a few years without a proper website already, Paver for 5 minutes and it's got one. I'm not going to do it, but someone should. Our company (ZeOmega) is willing to volunteer to do this work. Jeff Rush, who presented a tutorial about Buildout in last PyCon will be helping us to create this site [1]. I think it is better not to associate Buildout with zope.org domain. So, either we can create a new domain www.buildout.org or if you all agree a subdomain of python.org : buildout.python.org I hope we can use ZF's server infrastructure for hosting, otherwise we can also provide it. BTW, we already started creating some content here: http://wiki.python.org/moin/buildout/ http://wiki.python.org/moin/buildout/newsite_notes [1] http://us.pycon.org/2008/tutorials/EggsRush/ Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] paver: buildout is utterly doomed
- Martijn Faassen [EMAIL PROTECTED] wrote: Hi there, On Wed, Apr 23, 2008 at 8:30 AM, Baiju M [EMAIL PROTECTED] wrote: [snip] Our company (ZeOmega) is willing to volunteer to do this work. Jeff Rush, who presented a tutorial about Buildout in last PyCon will be helping us to create this site [1]. Great! [we already had some private communication about this] I think it is better not to associate Buildout with zope.org domain. So, either we can create a new domain www.buildout.org or if you all agree a subdomain of python.org : buildout.python.org I don't think python.org will be handing out subdomains, so I think we can forget about that. I'm fine with a domain name like buildout.org, and if the price is reasonable, I'm sure the Foundation can be approached for paying for it. We would like at least some reference back to Zope on it, but that's about it. I hope we can use ZF's server infrastructure for hosting, otherwise we can also provide it. All right, for the server infrastructure, Jens is setting it up. If you want a website set up, you'll have to follow his guidelines, as he wants to manage it carefully. Alternatively if it's more efficient for you, I don't think there's an objection to you hosting it, with the provision we'd like to reserve the right to be able to move it to the Foundation's hosting infrastructure at some point. OK, we decided to go ahead with this work. And we will be using a subdomain of zope.org and it will be hosted using ZF server infrastructure. I will contact Jens once content and site is ready. Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] paver: buildout is utterly doomed
- Martijn Faassen [EMAIL PROTECTED] wrote: Hi there, On Wed, Apr 23, 2008 at 7:39 PM, Baiju M [EMAIL PROTECTED] wrote: [snip] OK, we decided to go ahead with this work. And we will be using a subdomain of zope.org and it will be hosted using ZF server infrastructure. I will contact Jens once content and site is ready. Great! To prevent future deployment problems, could you tell Jens about what technology you intend to use for the site as soon as possible? We need to select something that both you and the community will be effective with. Plone 3 would be good as we already are deploying this for www.zope.org anyway, and grok.zope.org as well. We can take buildouts from those projects. Something like Sphinx to generate plain HTML pages from ReST might also be fine for a large part of the documentation; that'd involve just the publishing of static pages. We'll be exploring this for part of the Grok documentation eventually. We will be using Sphinx for the site. It will require: 1. Python 2.4 2. Sphinx 3. docutils 4. Pygments Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: [Checkins] SVN: z3c.formjs/branches/pcardune-extjs/ creating a branch to see what I can do about extjs integration.
Paul Carduner wrote: Log message for revision 85449: creating a branch to see what I can do about extjs integration. I found Jim removing two of his extjs related libraries from svn due to license issues (r85246, r85248). Please make sure that there is no license issue for your work committed to svn. Since extjs is released under LGPL, I guess you can release the library in a similar license, but only ZPL licensed thing can be committed to our svn :( /me wonder what will become a library and application from the pont of view of LGPL and Javascript. Regards, Baiju M P.S: CCed to zope-dev to see if there is any other opinion. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Request for commit access for updating zope.sendmail
Darryl Cousins wrote: Hi Matthew, On Fri, 2008-01-25 at 09:51 +1300, Matthew Grant wrote: Hi! I have recently been doing a lot of work on zope.sendmail, and would like to commit a lot of fixes, namely for: 1) Handling of SMTP error 451 etc. 2) Cleaning stale lock links out of the queue 3) Handling Server disconnection 4) Handling of connect() failure The above are fixes for Bug #157104 https://bugs.launchpad.net/zope3/+bug/157104 5) A bit of a clean up QueueProcessorThread so that it complies with IMailQueueProcessor in interfaces.py This all looks very cool. In order to become a zope contributor I believe this FAQ [1] is still valid and requires firstly to send a signed copy of this agreement [2] to the Zope Corporation. (I'm sure I'll be corrected if this has changed). [1] http://www.zope.org/DevHome/Subversion/ContributorFAQ [2] http://dev.zope.org/Subversion/Contributor.pdf Please include name of an existing contributor who is familiar with you and your work. (Based on Jim's mail: http://mail.zope.org/pipermail/zope-dev/2007-September/029734.html) Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: getting RestrictedPython working on Python 2.5
- Benji York [EMAIL PROTECTED] wrote: Philipp von Weitershausen wrote: On 5 Dec 2007, at 15:46 , Chris Withers wrote: The neat thign about the buildout way is that - it's an absolute no-brainer If you know what magic to incant ;-) All you have to remember is python boostrap.py and bin/buildout. Not very hard. The advantage is that every single sandbox can be set up like this. I deploy all my sites like this now, be it Grok, Zope 3 or even Plone: checkout the project from SVN and enter the two command - done! Maybe we should have a default GETTING-STARTED.txt that goes along with bootstrap.py. May be we can add it to top-level README.txt of all packages. Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: unregistering components?
- Philipp von Weitershausen [EMAIL PROTECTED] wrote: Wichert Akkerman wrote: Previously Ross Patterson wrote: Chris Withers [EMAIL PROTECTED] writes: Hi All, Does the component architecture support un-registering adapters and the like? From zope.component.interfaces: class IComponentRegistry(interface.Interface): Register components snip... def unregisterUtility(component=None, provided=None, name=u''): Unregister a utility snip... def unregisterAdapter(factory=None, required=None, provided=None, name=u''): Register an adapter factory snip... def unregisterSubscriptionAdapter(factory=None, required=None, provides=None, name=u''): Unregister a subscriber factory. snip... def unregisterHandler(handler=None, required=None, name=u''): Unregister a handler. snip... That'll do it, I think. :) You need a bit of extra information that is not in the interface: where to find the registry. To get the global registry you can do this: from zope.component.globalregistry import base as base_registry I think you should use zope.component.getGlobalSiteManager() for this. FWIW, I started documenting the complete API here: http://www.muthukadan.net/docs/zca.html Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] A book about Zope Component Architecture
Hi all, I started writing a book about Zope Component Architecture. http://www.muthukadan.net/docs/zca.html http://www.muthukadan.net/docs/zca.pdf If you have any suggestions/comments please send it to me. The book's source is hosted here: https://edge.launchpad.net/zcadoc BTW, I have used CSS available in Zope 3 source and LaTeX style available in Grok project's repository. Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] A book about Zope Component Architecture
Nando Quintana wrote:
Hi Baiju
I started writing a book about Zope Component Architecture.
Great news! Thank you for this effort!
If you have any suggestions/comments please send it to me.
We've taken a quick look at it and We've seen something strange on
page 21:
... def register(self): ... next_id = get_next_id() ...
guests_db[next_id] = { ... ’name’: guest.name, ... ’place’:
guest.place, ... ’phone’: guest.phone ... }
Here you should write self.guest.name instead of guest.name,
shouldn't you? or am I missing shometing?
Yes, that is an error. Thanks for pointing this out.
Regards,
Baiju M
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] buildout tests_require analogue
Chris McDonough wrote: Is there an equivalent for tests_require in buildout.cfg/zc.recipe.testrunner? The reason I ask is this... currently the zope.18n distribution has an install_requires that looks something like this: install_requires=[ 'setuptools', 'pytz', 'zope.i18nmessageid', 'zope.component [zcml]', 'zope.configuration', ] That's actually a no-good pack of lies, though. ;-) I'd like to change setup.py to something like this: test_suite = __main__.alltests, # to support setup.py test tests_require=[ 'zope.testing', 'pytz', 'zope.component [zcml]', 'zope.configuration', ], install_requires=[ 'setuptools', 'pytz', 'zope.i18nmessageid', 'zope.component', # *we* do not require zope.configuration at all. Our tests # do (for silly reasons) and the framework which uses our zcml # does. ], But I want buildout tests to continue to work. -1 for using different methods for running tests. Testing packages should be done in same way by all developers. If one person run tests in one way and another one in another way is not good. IMO, we should have a policy to use Buildout for development of Zope packages. Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SVN configuration guidelines
Christian Theune wrote: Hi, the most current version I found was this: http://www.zope.org/DevHome/Subversion/ZopeSVNFAQ Can we update the rules for setting the global ignores to include '.egg-info' directories? +1 Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope on Python 2.5?
Hi Limi, Alexander Limi wrote: Sorry if this has been asked hundreds of times before — I couldn't find any info on this apart from the Summer of Code project related to Zope 3. Now only the packages under `zope` `zope.app` packages works using Python 2.5 . I don't know the status of packages in `zc`, `z3c` and other namespaces. I also heard Grok is working fine with Python 2.5, but not yet officially blessed/supported. Will Zope 2 ever run on Python 2.5, or is that postponed indefinitely? We see an increasing amount of users trying to use Zope 2 with their systems that have Python 2.5 as default. Nikhil, who worked on Python 2.5 porting of Zope 3, told me that he will be working Zope 2 porting after his exams. Nikhil, can you send the status to this list ? Well, now you are not a GSoC student, so, this question is not official ;) Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: zope.app.error 3.5.1 not listed on distribution list
Philipp von Weitershausen wrote: I wish we wouldn't have to specify http://download.zope.org/distribution at all in our buildout.cfg. I think we're close to this point. +1 I think PSF is going to get another machine for PyPI [1]. Let's hope it will improve performance of PyPI. [1] http://www.python.org/psf/records/board/minutes/2007-09-10/ Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 5 OK
Zope Tests Summarizer wrote: Summary of messages to the zope-tests list. Period Thu Oct 18 12:00:00 2007 UTC to Fri Oct 19 12:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --- Is it possible to configure this mail notification in such way that it send mail only if there is any test failure ? Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] z3c.rml test failures
Hi Stephan, I am getting some test failure in z3c.rml trunk. One issue is due to the use of non-existing 'font' tag. I can't find this tag in 'rml.dtd' and reference. (But I can see a single use of 'font' tag in reference, but it is in a different context, I think should should be replaced as described below) All the places where 'font' tag used is as a child of 'title' tag. And 'face' is the only attribute used for the font tag in tests. Now 'title' has a 'fontName' attribute, from the DTD and reference I deduced that tests should use this instead of 'font' tag, is it correct ? There is another issue when I run tests in level 2, this can be solved by using few more arguments to Popen . (see the patch attached) There is one more remaining issue while parsing 'tag-textField.xml' I have given the trace back below, but if I parse this file individually, there is no test failure ! May be this is due to tests are not cleaned up properly. Regards, Baiju M Error in test runTest (z3c.rml.tests.test_rml.tag-textField) Traceback (most recent call last): File /baiju/usr//lib/python2.4/unittest.py, line 260, in run testMethod() File /home/baiju/office/z298i/z3c.rml/src/z3c/rml/tests/test_rml.py, line 60, in runTest rml2pdf.go(self._inPath, self._outPath) File /home/baiju/office/z298i/z3c.rml/src/z3c/rml/rml2pdf.py, line 64, in go doc.process(outputFile) File /home/baiju/office/z298i/z3c.rml/src/z3c/rml/document.py, line 281, in process self.canvas.save() File /home/baiju/office/z298i/z3c.rml/src/reportlab/pdfgen/canvas.py, line 877, in save self._doc.SaveToFile(self._filename, self) File /home/baiju/office/z298i/z3c.rml/src/reportlab/pdfbase/pdfdoc.py, line 219, in SaveToFile f.write(self.GetPDFData(canvas)) File /home/baiju/office/z298i/z3c.rml/src/reportlab/pdfbase/pdfdoc.py, line 241, in GetPDFData return self.format() File /home/baiju/office/z298i/z3c.rml/src/reportlab/pdfbase/pdfdoc.py, line 384, in format IOf = IO.format(self) File /home/baiju/office/z298i/z3c.rml/src/reportlab/pdfbase/pdfdoc.py, line 778, in format fcontent = format(content, document, toplevel=1) # yes this is at top level File /home/baiju/office/z298i/z3c.rml/src/reportlab/pdfbase/pdfdoc.py, line 95, in format f = element.format(document) File /home/baiju/office/z298i/z3c.rml/src/reportlab/pdfbase/pdfform.py, line 175, in format return proxy.format(document) File /home/baiju/office/z298i/z3c.rml/src/reportlab/pdfbase/pdfpattern.py, line 54, in format L.append(format(value, document)) File /home/baiju/office/z298i/z3c.rml/src/reportlab/pdfbase/pdfdoc.py, line 93, in format return document.Reference(element).format(document) File /home/baiju/office/z298i/z3c.rml/src/reportlab/pdfbase/pdfdoc.py, line 475, in Reference raise ValueError, object named but not registered ValueError: object named but not registered Index: src/z3c/rml/tests/input/tag-blockTableStyle-2.rml === --- src/z3c/rml/tests/input/tag-blockTableStyle-2.rml (revision 80889) +++ src/z3c/rml/tests/input/tag-blockTableStyle-2.rml (working copy) @@ -19,7 +19,7 @@ /stylesheet story -titlefont face=Courierlt;blockTableStylegt;/font Tag Demo/title +title fontName=Courierlt;blockTableStylegt; Tag Demo/title para This demo ensures that a table style can be applied multiple times. Index: src/z3c/rml/tests/input/tag-keepInFrame.rml === --- src/z3c/rml/tests/input/tag-keepInFrame.rml (revision 80889) +++ src/z3c/rml/tests/input/tag-keepInFrame.rml (working copy) @@ -13,7 +13,7 @@ /template story -titlefont face=Courierlt;keepInFramegt;/font Tag Demo/title +title fontName=Courierlt;keepInFramegt; Tag Demo/title para This tag allows keeping a set of flowables in a confined space. /para @@ -28,7 +28,7 @@ keepInFrame maxWidth=3cm maxHeight=2cm onOverflow=shrink name=second - titlefont face=Courierlt;keepInFramegt;/font Tag Demo/title + title fontName=Courierlt;keepInFramegt; Tag Demo/title para This tag allows keeping a set of flowables in a confined space. /para Index: src/z3c/rml/tests/input/tag-blockTable-bulkData.rml === --- src/z3c/rml/tests/input/tag-blockTable-bulkData.rml (revision 80889) +++ src/z3c/rml/tests/input/tag-blockTable-bulkData.rml (working copy) @@ -11,7 +11,7 @@ story -titlefont face=Courierlt;bulkDatagt;/font Tag Demo/title +title fontName=Courierlt;bulkDatagt; Tag Demo/title blockTable bulkData doc:example=![CDATA[ Product,Profit Index: src/z3c/rml/tests/input/tag-pto.rml === --- src/z3c/rml/tests/input/tag-pto.rml (revision 80889) +++ src/z3c/rml/tests/input/tag
Re: [Zope-dev] z3c.rml test failures
Baiju M wrote: Hi Stephan, I am getting some test failure in z3c.rml trunk. One issue is due to the use of non-existing 'font' tag. I can't find this tag in 'rml.dtd' and reference. (But I can see a single use of 'font' tag in reference, but it is in a different context, I think should should be replaced as described below) All the places where 'font' tag used is as a child of 'title' tag. And 'face' is the only attribute used for the font tag in tests. Now 'title' has a 'fontName' attribute, from the DTD and reference I deduced that tests should use this instead of 'font' tag, is it correct ? There is another issue when I run tests in level 2, this can be solved by using few more arguments to Popen . (see the patch attached) There is one more remaining issue while parsing 'tag-textField.xml' I have given the trace back below, but if I parse this file individually, there is no test failure ! May be this is due to tests are not cleaned up properly. Um, it looks like if 'font' tag come as child of 'story' tag there is no test failure. But which is the best for the tests failing ? use 'fontName' attribute in 'title' or use 'story' tag ? -- Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] AW: I'd lobe to merge the zope3-dev and zope-dev lists
Philipp von Weitershausen wrote: Waiting-for-this-discussion-to-die-down-ly I just counted votes here, there was 11 positive votes and 2 negative votes. +1 (Baiju M) +100 (Philipp von Weitershausen) +1 (Michael R. Bernstein) +1 Lennart Regebro +1 Andreas Jung +1 Jens Vagelpohl +1 Chris Withers +1 Martijn Faassen +1 Wichert Akkerman +1 Jodok Batlogg +1 Tres Seaver -1 Stephan Richter -1 Roger Ineichen Jim, I think you can proceed with merge now. Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
