Re: [Zope3-dev] Let's move over to zope-dev
Jim Fulton wrote: I think we have agreement (or an absense of anyone who is willing to publicly admit to disagree) to retire this list and move over to zope-dev. Let's do so. I'll wait a little while before trying to actively prevent posts here. I suggest we let any existing threads run out and start new threads on zope-dev. So, this is the last thread. Good bye zope3-dev ! :( 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] 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 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] StabilizeEggPackages wiki page
Hi Theune, I updated instructions here: http://wiki.zope.org/zope3/StabilizeEggPackages . Can you please review 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
[Zope3-dev] Re: [Zope-dev] I'd lobe to merge the zope3-dev and zope-dev lists
Jim Fulton wrote: Any objections? This would basically involve retiring the zope3-dev list and moving zope3 developers to the zope-dev list. +1 What about retiring #zope3-dev IRC channel and only using #zope ? 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: Release process closure
Jim Fulton wrote: On Oct 4, 2007, at 6:51 AM, Philipp von Weitershausen wrote: On 4 Oct 2007, at 00:59 , Jim Fulton wrote: On Oct 3, 2007, at 3:44 PM, Philipp von Weitershausen wrote: Jim Fulton wrote: I'd really like to get to closure on the current approved release process. Philipp, would you mind separating the release process into a separate file? Or do you mind if I do it? Done: http://svn.zope.org/*checkout*/Sandbox/philikon/foundation/releasing-software.txt Cool. I think you can delete 5b. You already update the date, as you should, on the trunk or branch. You want the actual release date to be part of the change log, so it has to be entered before making the tag. Done. I think we need to split d into: d) Create a source release e) Test the source release. At a minimum, rerun the package tests using the source release. (I really need to add a buildout option to help with this.) So how would I do this? This feels a bit complicated: 1. Create a source distribution with:: $ python setup.py sdist 2. Extract the tarball:: $ tar xzf dist/foo.package-X.Y.tgz 3. Edit buildout.cfg to make the result of the tarball a develop egg *instead* of the stuff in 'src':: [buildout] develop = foo.package-X.Y 4. Rerun the buildout:: $ bin/buildout 5. Run the tests:: $ bin/test No. :) Currently, you could: - Create the source distro. (Note that I always use sparkling clean Pythons, so the command you give doesn't work for me as setuptools isn't importable. I always use: bin/buildout setup . sdist Why you cannot install setuptools ? 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] i18n message factory in zope domain
Hi, Should we create separate message factory in 'zope' domain for each packages ? If so, can anyone explain why it should be like that. Few weeks back a new message factory is created in zope.i18nmessageid [1] . And now some packages use this directly. I am bit confused now ... [1] http://svn.zope.org/?rev=80022view=rev 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] Release process closure
Jim Fulton wrote: I'd really like to get to closure on the current approved release process. Philipp, would you mind separating the release process into a separate file? Or do you mind if I do it? Some comments on the current draft at: http://svn.zope.org/*checkout*/Sandbox/philikon/foundation/maintaining-software.txt WRT version numbers in setup.py. I'm inclined to endorse Philipp's recommendation for now. If there was a way to specify a version number on the command line (or in a buildout.cfg) when creating develop eggs, then I'd have a different position, but given current technology, I think Philipp's recommendation, as I understand it, is best. +1 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] Re: [Zope] Static Zope 3 APIDOC available!
Stephan Richter wrote: Hi everyone, I am happy to announce that the second Foliage sprint task is completed. Julian Bonilla, Graham Stratton and I worked on the outstanding issues on creating a functional version of the APIDOC, which comes with Zope. Thanks to Jens Vagelpohl, the static APIDOC is now available at: http://apidoc.zope.org I have also uploaded a TGZ archive to: http://download.zope.org/distribution/static-apidoc.tgz I hope that this development will spark renewed interest in the tool. In the future I plan to make more packages available in APIDOC and make it work with eggs. If you are interested, please let me know! Great news ! Congratulations to you all !! 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: faulty releases and pypi access [update]
Philipp von Weitershausen wrote: On 27 Sep 2007, at 13:47 , Stephan Richter wrote: On Thursday 27 September 2007 07:18, Philipp von Weitershausen wrote: These are four separate cases where I've actually witnessed myself or other people mess up. We're forgetful, we can't do anything about that. We can, however, force us to catch our mistakes. I believe that if we made everybody create the tarballs from the tag, it would improve the situation a lot. Of course, an additional or other approach would be to implement a tool that checks various things. I agree that the problems you listed are solvable with doing the release from the tag, but there are cases that are not caught: 1. In your last case, if bajium would have used svn switch --relocate the file would still be around and the release would work. I imagine that most people would use svn switch because making another checkout is just a package management mess. Why is making another checkout a package management mess? Go to /tmp or ~/temp or whatever, get the checkout, do your release stuff and delete it again. Is this so hard? Sorry, but I fail to see how this is messy. Also, regardless of what you imagine people do, if the process says get a new, fresh checkout then this is what people should do. If they use svn switch instead, then they're not following the process. End of story. Release from a fresh tag check out is always good. personal I have released eggs before and after my mistake. After my mistake, I created check list for my convenience here: http://wiki.zope.org/zope3/BaijuMuthukadan An now I am making release from tag checkouts. /personal 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] faulty releases and pypi access [update]
Christian Theune wrote: Am Mittwoch, den 26.09.2007, 08:49 + schrieb Christian Theune: Hey, here is an update. The issue is that the eggs were released as ZIP files and for some reason those don't work correctly with the data files. I can reproduce the problem by creating the packages myself as ZIP files (doesn't work) and then as tar files (does work). My proposal for what to do (Roger, maybe you can do that?): - Remove the broken files. - Create tags for the wrong trunk releases - Create a new release and tag in tar format. I'll show what I mean by releasing a fix for zope.app.i18n. Hmm. While doing that I also noticed that we were at 3.4.0a1 yesterday evening. The stable release was made from that without making a maintenance branch and bumping the trunk to 3.5. We decided not to bump minor release in trunk recently while making these final release, is it ? (But I have already bumped some of them earlier, but we can change it unless a 3.5 release has come out) 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] faulty releases and pypi access [update]
Christian Theune wrote: Am Mittwoch, den 26.09.2007, 11:53 +0200 schrieb Stefan H. Holek: WinZip has the habit of ignoring files it deems empty and paths it deems too long. Best to avoid. Nothing about winzip. The files are in there. I also couldn't find an issue in the egg info files. When I manually download and extract zope.app.appsetup zip file I can see a 'schema' folder and a ZCML file under that. But when I easy_install, that 'schema' directory is missing. 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] faulty releases and pypi access [update]
Baiju M wrote: Christian Theune wrote: Am Mittwoch, den 26.09.2007, 11:53 +0200 schrieb Stefan H. Holek: WinZip has the habit of ignoring files it deems empty and paths it deems too long. Best to avoid. Nothing about winzip. The files are in there. I also couldn't find an issue in the egg info files. When I manually download and extract zope.app.appsetup zip file I can see a 'schema' folder and a ZCML file under that. But when I easy_install, that 'schema' directory is missing. Oops, that is not a ZCML file but a schema.xml file -- 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: What does python 3000 mean for zope?
Philipp von Weitershausen wrote: David Pratt wrote: Hi. I am concerned about the announcement of python 3000 today that will break backwards compatibility. Zope and twisted are my favorite frameworks. The code base for both frameworks are not small. I haven't evaluated the changes but I can say this is a not great day for the python community either. I can see this dividing folks between present and future. Particularly, I'm thinking about incompatibilities developing around packages and dependencies through some sort of drawn out transition by the python community that may take years. Has anyone thoughts or comments about python 3000 implications for zope? Unfortunately, my first thoughts are that Python 3000 feels like Y2K for python :-(. Many thanks. We're currently struggling to get to Python 2.5 (which isn't exactly fresh out of the oven) mostly due to incompatibilities that it introduced compared to Python 2.4. So when Guido says Py3k will allow incompatible changes for the first time, it'll be hard to imagine how big the implications really are. It's especially hard to imagine because Py3k isn't done yet. Will the stdlib be reorganized? Who knows. I sure would like to see this '2to3' tool tackle the Zope codebase. C extensions, anyone? In fact Python 2.5 porting was not as much difficult as predicted in an old thread [1]. Nikhil has completed porting to Python 2.5 as part of Google Summer of Code project [2]. But we cannot officially support Python 2.5 until Zope 2 is also ported. (This is a policy of Zope Foundation, I guess) But we can give support for individual packages, is it ? May be we can try Python 3.0 porting in next GSoC ? :) [1] http://mail.zope.org/pipermail/zope3-dev/2006-September/020569.html [2] http://wiki.zope.org/zope3/ModuleImplementationStatus http://wiki.zope.org/zope3/Zope3UsingPython25 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: What does python 3000 mean for zope?
Andreas Jung wrote: --On 1. September 2007 16:00:19 +0530 Baiju M [EMAIL PROTECTED] wrote: May be we can try Python 3.0 porting in next GSoC ? :) -1 on that. I am pretty sure that this will lead to two different codebases which are hard to maintain over long period of time. We should stick with Python 2.X for the time being. Otherwise we risk compatibility issues with the current deployed Zope installations. We must not jump on every train just because it stop in front of out door. I hope your -1 is for porting to Python 3.0 in next year itself. May be we should consider it after Python 3.0 final release ? Otherwise how long will be the time being ? If packages like ZODB, zope.interface zope.component is not ported that will be great loss for Python 3.0 programmers. 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] Re: broken zope.lifecycleevent 3.4.0 on cheeseshop?
Philipp von Weitershausen wrote: Martijn Faassen wrote: Hi there, I see today a zope.lifecycleevent 3.4.0 was released to the cheeseshop (but not to download.zope.org/distribution). Unfortunately it seems to break when I install it into my buildout, with the following error: Running easy_install: /home/faassen/bin/python2.4 -c from setuptools.command.easy_install import main; main() -mUNxd /home/faassen/buildout-eggs/tmpA1S-YF -q /home/faassen/.buildout/download-cache/dist/zope.lifecycleevent-3.4.0.tar.gz path=/home/faassen/bin/eggs/setuptools-0.6c6-py2.4.egg error: /tmp/easy_install-NCwbAA/zope.lifecycleevent-3.4.0/CHANGES.txt: No such file or directory An error occured when trying to install zope.lifecycleevent 3.4.0.Look above this message for any errors thatwere output by easy_install. Something in its setup.py appears to be referring to a CHANGES.txt which evidently then cannot be found. What is going on? The tarball Baiju uploaded this afternoon is broken. I wanted to upload a fixed one, but it turns out I don't have permissions on PyPI. I already tried pinging Theuni and Baiju about this, but no response so far. I'm CCing them and Jim now, hoping one of them can give me access to PyPI. Sorry, I forgot to add CHANGES.txt to svn while making source egg. Now I have uploaded a new egg to PyPI and download.zope.org BTW, do we need to upload eggs to http://download.zope.org/distribution/ any more ? These two repositories are working very fine: http://download.zope.org/ppix/ http://pypi.python.org/simple/ Sorry again for the problems, 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.sendmail having dependency on zope.app.comonent
Wichert Akkerman wrote: Previously Philipp von Weitershausen wrote: On 30 Aug 2007, at 14:19 , Michael Howitz wrote: Am 22.08.2007 um 15:53 schrieb Philipp von Weitershausen: Michael Howitz wrote: while looking at the dependencies of packages in the zope.* namespace at gocept we found out that zope.sendmail depends on zope.app.component. Just to make sure: If we ever had a formal distinction of the zope.* and zope.app.* namespaces, I think we've abandoned it a while ago already. So, it doesn't matter whether a package is in zope.* or zope.app.*, we need to take all interdependencies (also the ones in zope.app.*) into account. So all in all I don't think it's a big problem in zope.sendmail depended on zope.app.component, as long as zope.app.component wouldn't depend on a gazillion other things... So, you suggest to leave this dependency as it is as long no-one complains? In general, yes. That said, zope.app.component isn't the lightest dependency. It draws in almost all of zope.app.* zope.sendmail needs zope.app.component.vocabulary.UtilityVocabulary to define a vocabulary for the utilities implementing zope.sendmail.interfaces.IMailDelivery. So we'd suggest to move zope.app.component.vocabulary.UtilityVocabulary out of the zope.app.* namespace because it is a generic vocabulary. Possible places for UtilityVocabulary could be zope.component (because the concept of utilities is defined there) or zope.schema (because the concept of vocabularies is defined there). zope.schema seems to be the better place because zope.component does not depend on zope.schema yet. But zope.schema does in no way depend on zope.component. Yes, you are right. So we would introduce a dependency from zope.schema to zope.comonent. The only way to get lost of the zope.app dependency seems to be a new package zope.app.sendmail (including deprecation!). But there is already a zope.app.mail which is deprecated and will be removed in 3.5. I don't understand why that is the only way and why we have to create more packages in that dreadful zope.app.* namespace. One way to break this dependency is to move the UtilityVocabulary out to a separate package, e.g. zope.utilityvocabulary. Another way is to simply stop using UtilityVocabulary; this would also be an opportunity to replace it with a source. zc.sourcefactory is supposed to make this quite easy (and from what I've seen, it does), but unfortunately its dependencies aren't exactly light-weight either. Is there documentation on sources anywhere? The last time I checked there was nothing that I could understand either in zope.* or on the wiki. There are some docs here: http://pypi.python.org/pypi/zc.sourcefactory 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 3.4 Release Date?
Christian Theune wrote: Am Dienstag, den 28.08.2007, 23:21 -0400 schrieb Tom Hoffman: Since Zope 3.4 can't be added to Debian/Ubuntu until the final comes out, we're stuck. At this point, the horse is probably out of the barn for Gutsy, but I'd rather not have to write this email again in December for Gutsy+1. True. We have a todo list of the rc which includes getting all the small packages to a stable release ASAP (which means checking back for critical bugs and if there are none go to stable finally) and then make an RC of 3.4 hopefully with a final release only one week later. Is that TODO list available online somewhere? I think I can spend sometime for this in this week. I am starting with zope.annotation , for zope.annotation the next release is marked as b1 in setup.py . So I wonder, should we make a b1 release or a final release ? This is the case for some other packages also. Is there any easy way to find bugs related to a particular package in launchpad. Regardds, 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.security problems related to Python 2.5 update? (Was: Removed zope.security 3.4b4)
Was this problem related to Python 2.5 update ?
I checked Nikhil's (GSoC student) commit (r78089), but cann't find any issue
with that changes.
Index: CHANGES.txt
===
--- CHANGES.txt(revision 78088)
+++ CHANGES.txt(revision 78089)
@@ -1,5 +1,8 @@
zope.security package changelog
===
+Next release
+
+- zope.security now works on Python 2.5
3.4.0b2 - 2007/06/15
Index: src/zope/security/checker.py
===
--- src/zope/security/checker.py(revision 78088)
+++ src/zope/security/checker.py(revision 78089)
@@ -701,6 +701,7 @@
type(iter([])): _iteratorChecker, # Same types in Python 2.2.1,
type(iter(())): _iteratorChecker, # different in Python 2.3.
type(iter({})): _iteratorChecker,
+type(iter(set())): _iteratorChecker,
type({}.iteritems()): _iteratorChecker,
type({}.iterkeys()): _iteratorChecker,
type({}.itervalues()): _iteratorChecker,
Index: src/zope/security/untrustedpython/tests.py
===
--- src/zope/security/untrustedpython/tests.py(revision 78088)
+++ src/zope/security/untrustedpython/tests.py(revision 78089)
@@ -16,13 +16,18 @@
$Id$
import unittest
-from zope.testing import doctestunit
+import re
+from zope.testing import doctestunit,renormalizing
def test_suite():
+checker = renormalizing.RENormalizing([
+ (re.compile(r'ImmutableModule' object),
+r'object'),
+ ])
return unittest.TestSuite((
doctestunit.DocFileSuite('builtins.txt',
'rcompile.txt',
- 'interpreter.txt',
+ 'interpreter.txt',checker=checker
),
))
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] how-to dig SVN log of the satellites
Adam Groszer wrote: Hello, Seems like it's not so easy to get a complete history log of the satellites. (e.g. zope\app\authentication\principalfolder.py). Where shall I look for it? If you don't use --stop-on-copy switch of svn log, you will get complete log. 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] RFC: Don't need $Id$ string any more
Jim Fulton wrote: I originally wanted $Id$ RCS keywords in module doc strings so that we could create tools that determined run-time version information. Unfortunately, subversion makes using this a bit difficult, as it doesn't update this information by default. If you add the following lines to svn configuration (~/.subversion/config) , all new Python files will get that property. [miscellany] enable-auto-props = yes [auto-props] *.py = svn:keywords=Id # enable id for Python files 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] Merge experimental-zwiki branch to trunk
Hi, I would like merge `baijum-experimental-zwiki` to zwiki trunk. http://svn.zope.org/zwiki/branches/baijum-experimental-zwiki/ The major changes are: 1) Added buildout support 2) Moved code to `src` folder 3) Use a test layer for functional testing Any comments ? 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 3 wiki cleanup
Simon Michael wrote: FYI - I installed a cleaned-up http://wiki.zope.org/zope3/FrontPage (the old one is at http://wiki.zope.org/zope3/FrontPage1). I think it's a step forward, hope you agree. Very nice, keep up the good work! Regrads, 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] Getting 403 error from download.zope.org
Christian Theune wrote:
Am Sonntag, den 22.04.2007, 15:11 -0400 schrieb Benji York:
David Pratt wrote:
Any idea what is happening with the site?
Getting distribution for zope.app.zptpage Error: Can't download
http://download.zope.org/distribution/zope.app.zptpage-3.4.0a1.tar.gz:
403 Forbidden
That file isn't world-readable. scp (appears to be) using the file
permissions as they are on the uploading file system. We need
some way to guarantee that the resulting permissions are such that
files placed in /distribution/ will be accessible. (Someone who
has sudo on that machine will have to fix those permissions, I
can't.)
A chmod in a cron job is the best idea I have. Others?
Gnarf. Right. That's my fault. My personal settings are user/group
readable on my machine and scp blindly takes over those files.
IMHO tweaking the masks on the target system could help, but I have
no idea.
Can anyone fix the permissions of these packages in server.
Or should we release '3.4.0a1-1' ?
from pkg_resources import parse_version
parse_version('3.4.0a1') parse_version('3.4.0a1-1')
True
btw, some packages are not tagged:
-RestrictedPython
-ZConfig
-zdaemon
-zodbcode
-zope.app.applicationcontrol
-zope.app.component
-zope.app.form
-zope.app.pagetemplate
-zope.app.publisher
-zope.app.traversing
-zope.decorator
-zope.deferredimport
-zope.documenttemplate
-zope.dottedname
-zope.event
-zope.exceptions
-zope.sequencesort
-zope.thread
I have compiled a list of eggs to be created in
'releases/eggs-to-created.txt' now.
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] Is Zope3.4 eggs going to be backwards compatible with Zope3.3 zpkg?
Ignas Mikalajunas wrote: Hi, I have accidentally tried upgrading from Zope3.3 branch checkout to Zop3.4 eggs, How you are doing this? can you elaborate? and it seems that at least: include package=zope.app / instead of throwing a deprecation warning (the way switching to Zope3.4 branch does IIRC) just stopped working. An egg based release is different from zpkg based release. In this case to get the proper warning you require more packages like 'zope.app.zcmlfiles', which are available as eggs. When working with eggs, there should be some mechanism to glue these eggs together, using zc.buildout is a good solution for that. Is there something wrong with my setup or will this way of upgrading things just not work? I can migrate Zope3.3 zpkg - Zope3.4 zpkg - Zope3.4 eggs. So, to change from zpkg based release to an egg based one, applications need to undergo some change in it's way of developing it. For example, if you want to use use zc.buildout, you can also use recipes like zc.zope3recipes, zc.recipe.filestorage, zc.recipe.testrunner etc for building and deploying a Zope 3 application. These recipe doesn't support anything like package-includes by default. Please see this for an example: svn://svn.zope.org/repos/main/zwiki/branches/baijum-experimental-zwiki Just that naming Egg release 3.4 seems a bit unfair, as one would expect 3.4 to be backwards compatible with 3.3. Well, what about creating an egg which lists all packages in Zope 3.4 as dependencies ? I think it will be useful for those who changing from zpkg based release to egg based release for development. In fact I have created one egg like that for my convenience: http://www.baijum.info/z3/download/zope33to34-3.4.0a1.tar.gz If anyone else want this, I can upload this to Python's cheeseshop. 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 3 without ZODB (redux)
Brian Sutherland wrote: Ok, I'm mostly done with what I wanted to do on that branch. I want to give people a chance to review it (feel free to commit directly to the branch) so I'll leave it on the branch for about 2 weeks before trying to merge it to the trunk. I am getting an error when running from an instance after removing zodb section in etc/zope.conf File ./bin/runzope, line 48, in ? run() File ./bin/runzope, line 44, in run main([-C, CONFIG_FILE] + sys.argv[1:]) File /mbaiju/wa/jinty-zodbless/src/zope/app/twisted/main.py, line 76, in main service = setup(load_options(args)) File /mbaiju/wa/jinty-zodbless/src/zope/app/twisted/main.py, line 145, in setup app_factory = appsetup.setup_app_factory(options.databases) File /mbaiju/wa/jinty-zodbless/src/zope/app/appsetup/appsetup.py, line 221, in setup_app_factory db = multi_database(database_factories)[0][0] IndexError: list index out of range 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: Cleaning up dependencies for Zope 3.4 eggs
On 4/9/07, Jim Fulton [EMAIL PROTECTED] wrote: On Apr 6, 2007, at 6:13 AM, Philipp von Weitershausen wrote: Fred Drake wrote: On 4/5/07, Baiju M [EMAIL PROTECTED] wrote: Since we almost eggified all packages under zope.app namespace, should we keep the all-in-one zope.app egg ? I've been making it a point to not depend on the zope.app egg; depending on it brings in things I don't want, and that's what we're trying to get away from in the first place. Right. The current zope.app egg also includes never-ever released things. It's simply the Zope3/src/zope/app directory from svn (which still has some old, never used and probably dangerous stuff in it). I don't know that unpublishing the already-published versions is needed; they can sit unused forever, and that won't break anything for the people who choose to depend on it. Apart from the fact that we should clean out the Zope3/src/zope/app directory in svn, we should also delete all traces of the zope.app egg. As mentioned, it contains unreleased stuff and is therefore not production or release material. Keeping it around would be misleading. +1 I removed the cheeseshop entry and also removed it from svn. Please remove it from downnload.zope.org/distribution . 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] Cleaning up dependencies for Zope 3.4 eggs
On 4/5/07, Christian Theune [EMAIL PROTECTED] wrote: Hi, I'd start adding those more specific version dependencies to zope.app and the other eggs. Since we almost eggified all packages under zope.app namespace, should we keep the all-in-one zope.app egg ? Can we remove this egg from PyPI and it's svn repository? (So far only development versions are released) 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] Where is source code of this tools : http://amy.gocept.com/~ctheune/XXXreport.html
KLEIN Stéphane wrote: Hello, I see this tools : http://amy.gocept.com/~ctheune/XXXreport.html I like this tools and I would like use it in my stuff. Where can I found the source code of this tools ? It's available in Zope 3 trunk/utilities/XXXreport2html.py (svn://svn.zope.org/repos/main/Zope3/trunk/utilities) 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] Re: [Checkins] SVN: zope.testing/trunk/setup.cfg This file is a recipe for bad releases
Jim Fulton wrote: Log message for revision 73922: This file is a recipe for bad releases Changed: D zope.testing/trunk/setup.cfg I am asking for a resolution here, do we want this file in svn for other packages ? In my experience I found this file is not required. To make a release with svn revision number just get the number from 'svn info' and copy-paste it in setup.py, then 'buildout setup . sdist' I agree with Jim says in the log message. Yes, it's YAGNI ! 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 3.4 release
Christian Theune wrote: Hi, we (Jim, Nathan, Michael and me) did some planning on how we're going to release Zope 3.4 and the future Zope 3 releases that are based on eggs. I tried to catch up and did my writing here: http://wiki.zope.org/zope3/DefiningZope34Release There is also a project in the repository in Zope3.buildout that tries to implement the proposal and is a work in progress that doesn't work right now. I think we need not to mimic the zpkg based release for 3.4, rather we should use zpkg for this release also. Because, - there is no particular advantage for mimicking zpkg based release using zc.buildout - we are gradually moving towards an egg based releases - applications are better to build using zc.buildout - our 3.4 alpha 1 release date is approaching, we follow time-based release ! (And our policy is to drop a feature, if it's not ready at time, is it?) In addition to this zpkg based release, we can release all eggs (as mentioned in the proposal) and make it available for download from a location. I think we are going to stop current way of releasing Zope 3 sooner or later, so we should advocate the use of eggs and zc.buildout for building and deploying Zope 3 applications. 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] Some thoughts for future releases of Zope 3
Hi, (Please correct me, if I am wrong) All eggs of a particular release will be available from : http://download.zope.org/distribution/zope3/ . Here is some future locations: 3.4.0 - distribution/zope3/3.4.0 3.4.1 - distribution/zope3/3.4.1 3.5.0 - distribution/zope3/3.5.0 For 3.4.0 all individual packages will be having a unique version number (3.4.0), but this won't be the case for 3.5.0, in Zope 3.5.0 zope.interface may be still in 3.4.0 version. In PyPI we will put all latest stable releases of individual packages, so a package in PyPI may be a newer version compared to the latest Zope 3 release. Then, to install a particular Zope 3 release, user should always use download.zope.org as eggs location (--find-links option in easy_install or zc.buildout). We *should* make 'zpkg' based releases, until 3.6 release. Anything to add here? 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] Some thoughts for future releases of Zope 3
Christian Theune wrote: Hi, Am Freitag, den 23.03.2007, 14:00 +0530 schrieb Baiju M: For 3.4.0 all individual packages will be having a unique version number (3.4.0), but this won't be the case for 3.5.0, in Zope 3.5.0 zope.interface may be still in 3.4.0 version. In PyPI we will put all latest stable releases of individual packages, so a package in PyPI may be a newer version compared to the latest Zope 3 release. Then, to install a particular Zope 3 release, user should always use download.zope.org as eggs location (--find-links option in easy_install or zc.buildout). I think we can have a meta-package for the Zope application that defines a dependency for all packages, some of those might still be 3.4.0 whilst others might be 3.5.1 etc. I don't think we really need the download areas to gather the eggs. I think putting all eggs in one place for each release will be useful for those who make offline installation/deploy. So they can easily make use the 'download-cache' and 'install-from-cache' options of zc.buildout without any hurdle. 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] Some thoughts for future releases of Zope 3
Christian Theune wrote: Hi, Am Freitag, den 23.03.2007, 14:43 +0530 schrieb Baiju M: I think putting all eggs in one place for each release will be useful for those who make offline installation/deploy. So they can easily make use the 'download-cache' and 'install-from-cache' options of zc.buildout without any hurdle. I don't think that this requires a central download location for each release. Yes, but users can grab all packages from one location and put together along with their packages. Some other egg based web frameworks follows this line, for example Pylons has a location like this: http://pylonshq.com/download/0.9.2 , http://pylonshq.com/download/0.9.3 , http://pylonshq.com/download/0.9.4 And this is a good way for archiving our upcoming releases. And another thing is that we need not to solely depend on PyPI. 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] Buildout recipe for building Zope 3 application soley from egg ?
(Reply to my own mail) Baiju M wrote: Hi, Is there a Buildout recipe for building Zope 3 application soley from egg ? I can see a note in zc.zope3recipes readme [1] like this: (In the future, there will be an application recipe that will work with Zope soley as eggs.) Jim, are you working on it ? [1] http://svn.zope.org/zc.zope3recipes/trunk/zc/zope3recipes/README.txt?rev=73115view=markup Just to experiment, I satrted to work on a recipe for this. Now I can create a Zope 3 application solely from eggs using Buildout. If anyone want to try this, here is the steps: $ svn co svn://svn.zope.org/repos/main/Sandbox/baijum/z3hello/trunk z3hello $ cd z3hello $ python2.4 bootstrap.py $ ./bin/buildout -N $ ./bin/instance start Now, from your browser go to : http://localhost:8080/hello 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: [Zope-dev] Re: [Zope3-dev] Google Summer of Code
Hi, I have added a new page under this wiki page: http://wiki.zope.org/zope3/SummerOfCode2007 to motivate students. See the page here: http://wiki.zope.org/zope3/Zope3UsingPython25 Please edit/correct that page details. So far only four ideas are added to the wiki page. No more ideas to add ? 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] Community opinion about search+filter
I think general questions can be posted to zope3-users list. No need to cross-post it to zope3-dev list also. 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: [Zope-dev] Re: [Zope3-dev] Google Summer of Code
Martijn Pieters wrote: On 3/5/07, Philipp von Weitershausen [EMAIL PROTECTED] wrote: Great. I've added you to http://wiki.zope.org/zope3/SummerOfCode2007. If you happen to have any project suggestions, feel free to add them to the list. Not a project suggestion, but relevant nonetheless: an excellent GSoC mentoring How-To: http://plone.org/products/plone/releases/SoC-2007 I added it to the Wiki page. It should be mandatory reading for any potential mentor! I think you added (by mistake?) this link instead: http://pyre.third-bit.com/blog/archives/863.html I found this one also useful: http://primates.ximian.com/~federico/docs/summer-of-code-mentoring-howto/index.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
[Zope3-dev] Bug days before 3.4 alpha release ?
Hi Theuni, What about organizing one or two bug days before 3.4 alpha release ? I am still not clear how 3.4 release will look like for a user with eggs and buildouts. How a user will install it ? Will there be an all-in-one Zope 3 tar ball for off line installation? Will there be an all-in-one windows setup file? BTW, eggification proposal ( http://wiki.zope.org/zope3/EggificationOfZopePackages ) for packages in `zope` namespace is completed. Thanks to all those who implemented it. It was really a simple but massive task. Another task which become necessary was test layer support for individual packages, again it was also simple but massive task. 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] Increment version number to 3.4dev ?
Hi, We have already incremented version number of many Zope 3 package to 3.4dev in trunk. Can I increment version number of the following packages in trunk to 3.4dev ? $ find . -name setup.py|xargs grep version=|grep -v 3.4dev ./zope.tales/setup.py: version='3.3dev', ./zope.modulealias/setup.py:version=0.1dev, ./zope.proxy/setup.py: version='3.4.0a1', ./zope.testing/setup.py:version='3.0', ./zope.exceptions/setup.py: version='3.3dev', ./zope.schema/setup.py: version='3.3dev', ./zope.dottedname/setup.py:version=0.1dev, ./zope.deprecation/setup.py:version='3.3.0', ./zope.decorator/setup.py:version=0.1dev, ./zope.documenttemplate/setup.py: version='3.3dev', ./zope.security/setup.py: version='3.3dev', ./zope.xmlpickle/setup.py: version='0.1dev', ./zope.event/setup.py:version='3.3.0', ./zope.i18n/setup.py: version='3.3dev', ./zope.testrecorder/setup.py: version='0.2', ./zope.pagetemplate/setup.py: version='3.3dev', ./zope.tal/setup.py: version='3.3dev', ./zope.thread/setup.py: version='3.3dev', ./zope.deferredimport/setup.py:version='1.0', ./zope.dublincore/setup.py:version=0.1dev, ./zope.publisher/setup.py: version='3.3dev', ./zope.sequencesort/setup.py:version=0.1dev, ./zope.structuredtext/setup.py: version='3.3dev', May be I shouldn't change zope.proxy (it is 3.4.0a1 now) ? 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.fssync dependency on zope.app.file
Fred Drake wrote: On 3/6/07, Baiju M [EMAIL PROTECTED] wrote: We have distributed zope.app.file with Zope 3.3 so zope.app.file should be distributed with zope.app egg when Zope 3.4 is released. And we are not distributed zope.fssync with Zope 3.3, but now zope.fssync is dependency for zope.app.file . The only dependencies I see from zope.app.file on any of the fssync stuff comes from the zope.app.file.fssync sub-package; this is intentional. The idea was that that package could be distributed separately; it should be a separate egg from zope.app.file. There are several cases of sub-packages named fssync which should be treated in this way (most of them, in fact); each of the type-specific fssync packages should depend on the package in which they are embedded and on zope.app.fssync. There should be no need to distribute any of them with a stock Zope 3.4. How can I exclude zope.app.file.fssync from zope.app package ? In zope.app, I have set zope.app.file as an svn:external, so everything under that package is included. 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.fssync dependency on zope.app.file
Hi, We have distributed zope.app.file with Zope 3.3 so zope.app.file should be distributed with zope.app egg when Zope 3.4 is released. And we are not distributed zope.fssync with Zope 3.3, but now zope.fssync is dependency for zope.app.file . So I am going include zope.fssync as a dependency for zope.app package. Also since zope.fssync uses zope.app.fssync we have to include this as part of zope.app egg. Any comments ? 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 Component Architecture wiki page
Hi, I have created a wiki page for Zope Component Architecture here: http://wiki.zope.org/zope3/ZopeComponentArchitecture Comments ? Please update that page with relevant details. 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] Re: SVN: Zope3/trunk/src/zope/configuration/tests/test_xmlconfig.py Make sure including zope.app.zcmlfiles in configuration works.
Philipp von Weitershausen wrote: Baiju M wrote: Log message for revision 72757: Make sure including zope.app.zcmlfiles in configuration works. I fail to see the point of this test. This is a doctest, I would at least expect one line explaining why we need to test loading zope.app.zcmlfiles. Also, why does this need to be in zope.configuration? It seems wrong introducing this kind of dependency, evne if it's just for testing. I realise that the place of that test is wrong, I will revert it. I do realize that zope.configuration now has some code to support backward compatibility of include package=zope.app /. *This* would be something worthwile testing, I suppose, though perhaps in a way that would prevent actually loading all of the zope.app configuration (perhaps toggling the execution of ZCML actions to false would be a solution). This test loads a fair bit of stuff, pretty close to a functional test setup. This has to be torn down (which is pretty hard to do, hence the functional layers so far don't implement tearDown). Since xmlconfig.include method only parse and not execute ZCML, toggling the execution of ZCML actions to false is not required. + try: +... xmlconfig.include(context, 'file_not_exists.zcml', zope.app.zcmlfiles) +... except IOError, msg: +... 'OK' +'OK' + I think the preferred way to test for exceptions in doctests is: xmlconfig.include(context, 'file_not_exists.zcml', zope.app.zcmlfiles) Traceback (most recent call last): IOError: ... Thanks, I will change the other tests like that. 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.component dependency on zope.testing
Hi,
zope.testing is a dependency for zope.component because
zope.testing.cleanup.addCleanUp method is used in
zope.component.globalregistry
This code only works when running tests ?
Can we can make zope.testing dependency optional like this:
Index: src/zope/component/globalregistry.py
===
--- src/zope/component/globalregistry.py(revision 72734)
+++ src/zope/component/globalregistry.py(working copy)
@@ -138,9 +138,13 @@
base = BaseGlobalComponents('base')
-from zope.testing.cleanup import addCleanUp
-addCleanUp(lambda: base.__init__('base'))
-del addCleanUp
+try:
+from zope.testing.cleanup import addCleanUp
+except:
+pass
+else:
+addCleanUp(lambda: base.__init__('base'))
+del addCleanUp
globalSiteManager = base
def getGlobalSiteManager():
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] Re: Zope 3 added to ohloh.net
Philipp von Weitershausen wrote: Baiju M wrote: Hi, Few days back I found that Zope 2, Plone, Schooltool etc. are already added to ohloh.net I just tried to go to this page, but couldn't connect. What is ohloh.net? What do they do with our code? What's the benefit? I don't know much about this project. I found some other free/open source projects using it, so I just tried to add Zope 3. It's showing some statistics based on svn commits. I think, it's not that much useful. May be we can delete Zope 3 from there? 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. Useful for what? Again, I don't know much about this. They call it as a system for tracking open-source projects in real-time. When I join #plone irc channel I can see their svn commits always coming there. We get commit messages from mailing list, so this is not required for us. 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
Jamu Kakar wrote: Hi Baiju, Baiju M wrote: 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 Sorry for the late reply. It turns out that the problem I was seeing was also test layer related. It appears that dealing with the test layer problems have us working with Zope trunk again (as of today). Yay! :) Sorry for the false alarm. Don't feel sorry about it. Always please reply to list. Anyway I am sending this information to zope3-dev list for record. With thanks and 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] 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] 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
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
Re: [Zope3-dev] Broken tests since last checkout
On 2/18/07, Roger Ineichen [EMAIL PROTECTED] 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):
File D:\trunk\Zope3\src\zope\testing\doctest.py, line 1361, in __run
compileflags, 1) in test.globs
File doctest README.txt[4], line 1, in ?
manager.open('http://localhost/sampledata.html')
File D:\trunk\Zope3\src\zope\testbrowser\browser.py, line 223, in
open
self.mech_browser.open(url, data)
File D:\trunk\Zope3\src\mechanize\_mechanize.py, line 177, in open
return self._mech_open(url, data)
File D:\trunk\Zope3\src\mechanize\_mechanize.py, line 202, in
_mech_open
response = UserAgent.open(self, self.request, data)
File D:\trunk\Zope3\src\mechanize\_opener.py, line 234, in open
response = urlopen(self, req, data)
File C:\Python24\lib\urllib2.py, line 376, in _open
'_open', req)
File C:\Python24\lib\urllib2.py, line 337, in _call_chain
result = func(*args)
File D:\trunk\Zope3\src\zope\testbrowser\testing.py, line 123, in
http_open
return self.do_open(PublisherConnection, req)
File C:\Python24\lib\urllib2.py, line 993, in do_open
h.request(req.get_method(), req.get_selector(), req.data, headers)
File D:\trunk\Zope3\src\zope\testbrowser\testing.py, line 80, in
request
self.response = self.caller(request_string, handle_errors)
File D:\trunk\Zope3\src\zope\app\testing\functional.py, line 592, in
__call__
environment)
File D:\trunk\Zope3\src\zope\app\testing\functional.py, line 625, in
chooseRequestClass
return chooseClasses(method, environment)
File D:\trunk\Zope3\src\zope\app\publication\httpfactory.py, line
33, in chooseClasses
factory = factoryRegistry.lookup(method, content_type, environment)
File
D:\trunk\Zope3\src\zope\app\publication\requestpublicationregistry.py,
line 97, in lookup
raise ConfigurationError('No registered publisher found '
ConfigurationError: No registered publisher found for (GET/)
Does anybody have any hints why the publisher is missing?
I am not getting this error when running 'python2.4 test.py' in Zope 3
trunk checkout.
How did you run this test?
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] Eggification and some random files/packages
Hi, How we will be installing Zope 3.4, can I do it like this: easy_install zope3 If this is the case, the zope3 package will contain few files/packages which are not separately eggified? What are the minimum files required in this zope3 package? I assume some scrips,docs etc. will be there. There are few tests which are located outside any particular package. zope.app.ftests and zope.app.tests Either we can distribute it with our huge zope.app egg or move it to some other places. What about moving those tests to zope.app.zcmlfiles ? 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] Eggification and some random files/packages
(Replying to myself!) Baiju M wrote: There are few tests which are located outside any particular package. zope.app.ftests and zope.app.tests Either we can distribute it with our huge zope.app egg or move it to some other places. What about moving those tests to zope.app.zcmlfiles ? When I looked at zope.app.tests, I can see that it is a deprecated package. So no need to moving anywhere. But zope.app.ftests has a test case (reusable?) Again I couldn't find any advantage for moving this too. So I will simply put it as svn:externals in zope.app egg package. May be we have to deprecate zope.app.ftests too? 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] Eggification and some random files/packages
Baiju M wrote: (Replying to myself!) Baiju M wrote: There are few tests which are located outside any particular package. zope.app.ftests and zope.app.tests Either we can distribute it with our huge zope.app egg or move it to some other places. What about moving those tests to zope.app.zcmlfiles ? When I looked at zope.app.tests, I can see that it is a deprecated package. So no need to moving anywhere. But zope.app.ftests has a test case (reusable?) Again I couldn't find any advantage for moving this too. So I will simply put it as svn:externals in zope.app egg package. May be we have to deprecate zope.app.ftests too? Well, after few more looks into test cases, I am planning to move src/zope/app/ftests/test_functional.py to src/zope/app/testing/ftests.py And move src/zope/app/ftests/doctest.txt to src/zope/app/testing/doctest.txt I have done this in my checkout. Can anyone review this: http://zissue.berlios.de/z3/zope-app-testing-diff.txt I have also added a test layer for these ftests. 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] Checkins mails and zope egg changes
Hi, I am not getting any changes (through checkins mailing list) made to zope eggs recently by 'alex' (committer id) alex, I read your commit mesage: Remove setup.cfg.in, INSTALL.txt, CHANGES.txt, test.py, MANIFEST.in and README.txt because they are no longer needed. Why these files are no longer needed? test.py may not be required after buildout. Also please revert r72507 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] Checkins mails and zope egg changes
Jim Fulton wrote: On Feb 15, 2007, at 3:02 AM, Baiju M wrote: Hi, I am not getting any changes (through checkins mailing list) made to zope eggs recently by 'alex' (committer id) alex, I read your commit mesage: Remove setup.cfg.in, INSTALL.txt, CHANGES.txt, test.py, MANIFEST.in and README.txt because they are no longer needed. Could you remind me which package (or svn revision) you are refering to? *r72589, **r72588 and few others.* Why these files are no longer needed? test.py may not be required after buildout. I'll turn that around. What are they needed for? You should only need a setup.py and, if buildout is used, a buildout.cfg. The examples alex showed me seemed out of date with the current way of doing things. I particularly don't want setup.cfg.in, and MANIFEST.in as these aren't really necessary and tend to cause problems. Agreed. Anyway, atleast we will be required a README.txt and CHANGES.txt Also please revert r72507 Why? In r72507 a setup.py is added to Zope3/trunk/src/zope/annotation/setup.py This should be in zope.annotation/trunk/setup.py (It's already there, also alex later modified 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] Test layers for zope.app.* packages
Jim Fulton wrote: On Feb 5, 2007, at 4:40 AM, Baiju M wrote: We have to add test layer for each packages in zope.app namespace. I think we should. I'm not sure we *need* to. I certainly don't want to do this if it will delay full eggification. As I've mentioned before, I'd be perfectly happy to see a large zope.app egg containing everything we had in previous releases as a start. We could always break packages off later. I have created zope.app egg two weeks back (http://svn.zope.org/zope.app/trunk/) I have used setuptools.find_packages function, so setuptools is a dependency. Should we need compatibility with distutils.core ? 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] development checkout
Chris Withers wrote: Is there a how-to somehwere? Yes, http://wiki.zope.org/zope3/SettingUpAZope3Sandbox If possible, please update this wiki page based on other replies. 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] sys._getframe magic and z.a.t.functional.defineLayer
Hi, We are using sys._getframe magic in many places. Sometimes it is the only way. But I wonder why we required a function like : 'z.a.t.functional.defineLayer' Yes, it saves few typing, but if we are defining layers directly using LayerName = ZCMLLayer(...) It will be more explicit and understandable code. I wrote an example here: http://pastey.net/5739-48en 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] Re: SVN: zope.app.annotation/ Add zope.app.annotation as a top-level package.
Philipp von Weitershausen wrote: Baiju M wrote: [snip] I thought we can create individual eggs instead of a big zope.app egg for Zope 3.4. Well, I don't think we have to make every single subpackage its own egg. We should pick our battles and start with those individual eggs that can actually be used w/o Zope 3, e.g. zope.app.container, zope.app.form, etc. I don't think we need to create individual eggs for each package, especially those that will disappear soon anyway because of BBB. So I started working on eggification of zope.app.* packages in alphabetical order :) (zope.app.annotation was the first package) I suggest we come up with a prioritized list instead of alphabetical. I agree, this is a good suggestion. I will start another thread for the packages to be eggified later (or any other taker ?). Then, we will be having a zope.app egg + individual zope.app.* eggs zope.app egg will not contain any packages which is officially eggified seperatly (zope.app.container, zope.app.form, 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
[Zope3-dev] Re: SVN: zope.app.annotation/ Add zope.app.annotation as a top-level package.
Philipp von Weitershausen wrote: Baiju M wrote: Log message for revision 72044: Add zope.app.annotation as a top-level package. Changed: A zope.app.annotation/ A zope.app.annotation/branches/ A zope.app.annotation/tags/ A zope.app.annotation/trunk/ -=- Is it really necessary to create the BBB packages in zope.app (annotation, traversing, etc.) as separate eggs? They're gonna go away in Zope 3.5 anyway. I think they could be part of the zope.app egg in Zope 3.4. I thought we can create individual eggs instead of a big zope.app egg for Zope 3.4. So I started working on eggification of zope.app.* packages in alphabetical order :) (zope.app.annotation was the first package) We can eggify all packages except those in Spring cleanup proposal [1] BTW, There will be a Zope 3 Egg Day ! [2] on next Saturday (20-Jan-2007) and it will continue on Sunday [3] if there is interest. [1] http://wiki.zope.org/zope3/SpringCleaning07 [2] http://mail.zope.org/pipermail/zope3-dev/2007-January/021491.html [3] http://mail.zope.org/pipermail/zope3-dev/2007-January/021492.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: [Zope3-checkins] SVN: zope.testing/branches/mgedmin-fixes/src/zope/testing/testrunner Implement a --list-modules option that lists all modules matching your pattern,
Marius Gedminas wrote: [snip] And all tests are passed with message Ran 123 tests with 0 failures and 0 errors in 18.783 seconds. Which Python version do you have? I get 4 failures with Python 2.4.4c1 (Ubuntu Edgy) with the zope.testing trunk. These are now fixed on the mgedmin-fixes branch. I am using a manually installed 2.4.4 final release. All tests pass, but some other error is coming, here is the output: Running unit tests: Ran 123 tests with 0 failures and 0 errors in 54.110 seconds. Error in atexit._run_exitfuncs: Traceback (most recent call last): File /var/tmp/zopy/usr//lib/python2.4/atexit.py, line 24, in _run_exitfuncs func(*targs, **kargs) File /var/tmp/zopy/usr//lib/python2.4/logging/__init__.py, line 1333, in shutdown h.close() File /var/tmp/zopy/usr//lib/python2.4/logging/__init__.py, line 772, in close StreamHandler.close(self) File /var/tmp/zopy/usr//lib/python2.4/logging/__init__.py, line 674, in close del _handlers[self] KeyError: logging.FileHandler instance at 0xb7a1dc8c Error in sys.exitfunc: Traceback (most recent call last): File /var/tmp/zopy/usr//lib/python2.4/atexit.py, line 24, in _run_exitfuncs func(*targs, **kargs) File /var/tmp/zopy/usr//lib/python2.4/logging/__init__.py, line 1333, in shutdown h.close() File /var/tmp/zopy/usr//lib/python2.4/logging/__init__.py, line 772, in close StreamHandler.close(self) File /var/tmp/zopy/usr//lib/python2.4/logging/__init__.py, line 674, in close del _handlers[self] KeyError: logging.FileHandler instance at 0xb7a1dc8c Any idea why this is happens? 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] Re: [Zope3-checkins] SVN: zope.testing/branches/mgedmin-fixes/src/zope/testing/testrunner Implement a --list-modules option that lists all modules matching your pattern,
Marius Gedminas wrote: Log message for revision 71953: Implement a --list-modules option that lists all modules matching your pattern, but does not actually run any tests. I hope this will help me figure out why test.py -s zope.testing in a Zope 3 checkout runs 0 tests. If I comment 'zope[.]testing' line in test.py, I can run 'test.py -s zope.testing'. And all tests are passed with message Ran 123 tests with 0 failures and 0 errors in 18.783 seconds. Index: test.py === --- test.py (revision 71953) +++ test.py (working copy) @@ -50,7 +50,7 @@ '|' 'zdaemon' '|' - 'zope[.]testing' + #'zope[.]testing' '|' ')[.]'] 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 Egg Day !
Hi, I am thinking about organizing a Zope 3 Egg Day for eggification of zope.app.* packages. Anyone interested? Eggification of zope.app.* packages is a massive effort, so it's not yet added to the release goal of Zope 3.4. If this egg day become successful, I think we can add it to the release goal. There are 90+ packages in zope.app namespace. Details about eggification is available from this proposal: http://wiki.zope.org/zope3/EggificationOfZopePackages I suggest 20-Jan-2007 (Saturday) as Zope 3 Egg Day. 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] Builbot mail not working ?
Baiju M wrote:
Hi, Can anyone verify that buildbot [1] send test failure error mails
to list? There is one test failure in Zope 3 trunk now [2]. But it's
not in Zope3-dev list archive [3].
[1] http://buildbot.zope.org [2]
http://buildbot.zope.org/Zope3%20trunk%202.4%20Linux%20zc-buildbot/builds/832/test_2/0
[3] http://mail.zope.org/pipermail/zope3-dev/
I am still getting this error in trunk, see the traceback:
Failure in test
/var/tmp/zopy/pkgs/Zope3trunk/src/zope/app/ftests/doctest.txt
Failed doctest test for doctest.txt
File /var/tmp/zopy/pkgs/Zope3trunk/src/zope/app/ftests/doctest.txt,
line 0
--
File /var/tmp/zopy/pkgs/Zope3trunk/src/zope/app/ftests/doctest.txt,
line 20, in doctest.txt
Failed example:
print http(r
GET /@@contents.html HTTP/1.1
)
Differences (ndiff with -expected +actual):
HTTP/1.1 401 Unauthorized
+ Cache-Control: no-store, no-cache, must-revalidate
- Content-Length: ...
? ^^^
+ Content-Length: 3987
?
Content-Type: text/html;charset=utf-8
+ Expires: Mon, 26 Jul 1997 05:00:00 GMT
+ Pragma: no-cache
WWW-Authenticate: basic realm=Zope
BLANKLINE
- !DOCTYPE html PUBLIC ...
+ !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
+ BLANKLINE
+ html xmlns=http://www.w3.org/1999/xhtml; xml:lang=en
+ lang=en
+ BLANKLINE
+ head
+ titleZ3: /title
+ BLANKLINE
+ style type=text/css media=all@import
url(http://localhost/@@/zope3_tablelayout.css);/style
+ BLANKLINE
+ BLANKLINE
+ BLANKLINE
+ meta http-equiv=Content-Type
content=text/html;charset=utf-8 /
+ BLANKLINE
+ BLANKLINE
+ BLANKLINE
+ BLANKLINE
+ BLANKLINE
+ !-- Basic zope3 javascript's --
+ script type=text/javascript
+ src=http://localhost/@@/zope3.js;
+ /script
+ BLANKLINE
+ BLANKLINE
+ !-- Ugly is better than lobotomized. --
+ script type=text/javascript
+ src=http://localhost/@@/xmltree.js;
+ /script
+ BLANKLINE
+ BLANKLINE
+ BLANKLINE
+ BLANKLINE
+ BLANKLINE
+ BLANKLINE
+ BLANKLINE
+ BLANKLINE
+ BLANKLINE
+ link rel=icon type=image/png
+ href=http://localhost/@@/favicon.png; /
+ /head
+ BLANKLINE
+ body onload=loadtree('http://localhost/', 'http://localhost/');
+ table id=layout border=0 cellspacing=0 cellpadding=0
+ tr
+ td colspan=2 id=top
+ BLANKLINE
+ div id=global
+ div id=userDetails
+ BLANKLINE
+ User:
+ Unauthenticated User
+ BLANKLINE
+ BLANKLINE
+ BLANKLINE
+ a
href=@@login.html?nextURL=http%3A//localhost/%40%40contents.html[Login]/a
+ BLANKLINE
+ BLANKLINE
+ /div
+ BLANKLINE
+ a
+ href=http://localhost/@@SelectedManagementView.html;
+ name=topimg src=http://localhost/@@/zope3logo.gif; //a
+ BLANKLINE
+ /div
+ BLANKLINE
+ /td
+ /tr
+ tr
+ td colspan=2
+ BLANKLINE
+ div id=breadcrumbs
+ Location:nbsp;a
+ href=http://localhost/@@SelectedManagementView.html;[top]/a
+ /
+ /div
+ BLANKLINE
+ /td
+ /tr
+ tr
+ td id=navigation
+ BLANKLINE
+ div id=navigators
+ !-- Navigation tree box --
+ BLANKLINE
+ !-- Ugly is better than lobotomized. --
+ div class=box id=navigationTree
+ h4Navigation/h4
+ div xmlns=http://www.zope.org/zope3xmltree;
+ id=navtreecontents class=body
+ onclick=treeclicked(event);Loading.../div
+ /div
+ BLANKLINE
+ BLANKLINE
+ /div
+ BLANKLINE
+ /td
+ td id=content
+ div id=workspace
+ BLANKLINE
+ BLANKLINE
+ !-- OnlineHelp with popup support --
+ !-- note, we reverse the actions list 'cos
they're packed to the
+ screen from the right --
+ BLANKLINE
+ BLANKLINE
+ div id=viewspace
+ div id=message
+ /div
+ div id=body
+ div
+ BLANKLINE
+ h1Unauthorized/h1
+ BLANKLINE
+ pYou are not authorized/p
+ BLANKLINE
+ /div
[Zope3-dev] Test layers for zope.* packages
Hi, Few weeks back we discussed using test layers for zope.* packages. I tried to do it in my checkout. Here is the patch for trunk: http://zissue.berlios.de/z3/zope-testbrowser-diff.txt When running the tests the output will be like this : http://zope3.pastebin.com/851855 Jim wants to do it in this way (see http://zope3.pov.lt/irclogs/%23zope3-dev.2007-01-05.log.html) Anyone want to do this for other packages? P.S: My employer is changed, so I have to send a new contributor agreement for making further commits. (I joined ZeOmega on 2nd January 2007) 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] Builbot mail not working ?
Hi, Can anyone verify that buildbot [1] send test failure error mails to list? There is one test failure in Zope 3 trunk now [2]. But it's not in Zope3-dev list archive [3]. [1] http://buildbot.zope.org [2] http://buildbot.zope.org/Zope3%20trunk%202.4%20Linux%20zc-buildbot/builds/832/test_2/0 [3] http://mail.zope.org/pipermail/zope3-dev/ 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] Experimental implementation of Loading Configuration from the zope.app Egg
On 12/22/06, Jim Fulton [EMAIL PROTECTED] wrote: snip svn://svn.zope.org/repos/main/Zope3/branches/baijum-zope-app-zcmlfiles snip I suggest you merge this to the trunk. My review was not very thorough but if I missed anything, we can sort it out later. Ok, will merge it after fixing two warnings. I guess that we can make a collected zope.app egg now and break it up later as people have time to make individual eggs. This egg could include just zope.app.zcmlfiles the packages from zope.app needed to make zope.app.zcmlfiles' configure.zcml work. A collected zope.app egg is good idea. 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] Experimental implementation of Loading Configuration from the zope.app Egg
Hi Jim, I tried to implement your Loading Configuration from the zope.app Egg proposal [1] in one svn branch (baijum-zope-app-zcmlfiles) [2]. If you are not yet started it's implementation can you review this branch? [1] http://wiki.zope.org/zope3/LoadingConfigurationFromTheZopeAppEgg [2] svn://svn.zope.org/repos/main/Zope3/branches/baijum-zope-app-zcmlfiles 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: [SpringCleaning07]
On 12/19/06, Roger Ineichen [EMAIL PROTECTED] wrote: Hi Baiju Subject: [SpringCleaning07] Here is a list of candidates for removal (please verify!): zope.dependencytool zope.fssync zope.importtool zope.modulealias zope.sequencesort zope.wfmc zope.xmlpickle zope.app.dtmlpage zope.app.file zope.app.fssync zope.app.zptpage -- What does removal mean? IMO, the proposal (http://wiki.zope.org/zope3/SpringCleaning07) can elaborate on that. Anyway, a package selected for spring cleanup can be changed it's location in svn. For example, zope.fssync is now in the toplevel of subversion. But 'src/zope/fssync' is an svn:externals to svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/fssync. Now fssync source can be moved to this location, after removing svn:externals. But some packages are not yet added to toplevel of svn, it can be added as part of eggification. 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] On the road to Zope 3.4
On 12/19/06, Christian Theune [EMAIL PROTECTED] wrote: I'd like to get some feedback on the eggification, as the proposal IMHO needs some work on the goals that should be achieved within the scope and how it relates to zc.buildout. (Is turning each package into a buildout within the scope or not?) zc.buildout support for individual packages are a goal of EggificationOfZopePackages proposal. For complete eggification (including zope.app.* packages) LoadingConfigurationFromTheZopeAppEgg proposal (http://wiki.zope.org/zope3/LoadingConfigurationFromTheZopeAppEgg) should be implemented. But it's not yet implemented ? 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: Tracking eggification of zope.* packages
On 11/5/06, Jim Fulton [EMAIL PROTECTED] wrote: I meant to note that the efforts to eggify many packages is a crucial and much appreciated first step in the effort to get an agg-based Zope 3 (and someday Zope 2) checkout and distribution. Now most of the zope.* packages are eggified, but some packages should be considered broken because it's functional testing are not working. We have to use test layers for functional testing with at least one layer per package based on ZCMLLayer ? Then there will be TestBroserLayer, PublisherLayer etc. or should we create a ZopeAppServerLayer derived from ZCMLLayer and use it for the packages where application server is required to run tests? To eggify zope.app.* packages we should implement this proposal ? : http://wiki.zope.org/zope3/LoadingConfigurationFromTheZopeAppEgg I have implemented this in my checkout with an ugly hack and tried to eggify one package, can anyone review this ? ftp://ftp.berlios.de/pub/zissue/z3/zope.app.container.tar.bz2 Where do we place zope.app.* individual packages in subversion? If we are placing it in toplevel (under main) there will be about 90+ packages. What about creating a 'zope.app' directory in toplevel and put all zope.app.* packages there ? Regards, Baiju M P.S: My marriage in on next Sunday, so I won't be doing anymore eggification in coming days. ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: [Checkins] SVN: zope.fssync/trunk/ Initial commit of zope.fssync for eggification.
On 10/29/06, Benji York [EMAIL PROTECTED] wrote: Baiju M wrote: Log message for revision 70964: Initial commit of zope.fssync for eggification. I'm really glad to see so much work being done on eggification, but am a little concerned as to the mechanics. I'm worried that if dozens of packages are separated out before they are actually knit into Zope proper, we'll get drift between the two. It would seem to make more sense to eggify one or a few packages and get them properly working in the core, and then go from there. zope.fssync and some other packages are not distributed with Zope 3. In fact I am preparing another proposal to move these packages to another location in subversion [1]. So, if I do the eggification of those packages now itself, it will be easier for implementing that proposal. Remember, spring cleanup is another release goal of Zope 3.4. [1] http://kpug.zwiki.org/RemovalOfNonDistributedPackages 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: Tracking eggification of zope.* packages
On 10/26/06, Jim Fulton [EMAIL PROTECTED] wrote: Baiju M wrote: But I am not sure zc.buildout support is a release goal of Zope 3.4? My plan is to base 3.4 on buildout. Theune, What about adding this to prospective feature list of Zope 3.4 here: http://wiki.zope.org/zope3/RoadMap 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] Individual packages and functional testing
Hi, As part of eggification [1], I was creating an egg of zope.testbrowser There are some functional tests in that package. So, I have to copy few ZCML files to top directory from an instance to run the functional tests. How do we handle the functional tests for individual packages? Should I add all ZCML files to each packages which required functional testing? I think I am missing something here, because Zope 3 main test.py works without these ZCML files? I have committed zope.testbrowser [2], to enable functional tests, change test-pattern in test.py to '^f?tests$'. [1] http://wiki.zope.org/zope3/EggificationOfZopePackages [2] svn co svn://svn.zope.org/repos/main/zope.testbrowser/trunk zope.testbrowser 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] Tracking eggification of zope.* packages
Hi all, I have created a proposal to _tack eggification_ of zope.* packages, which is already started. http://zope3.zwiki.org/EggificationOfZopePackages May be I should change the status as IsInformational ? Buildout support for individual packages are not included in this proposal. I think it can be another proposal. Any suggestions/comments? 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
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
[Zope3-dev] Path used in test.py for Zope 3 and individual packages.
Hi,
I was experimenting with creating some eggs [1] .
When I tried to run tests of zope.configuration (Individual package)
I got some test failures, this is due to a path problem:
Failure in test checkDuplicate (zope.configuration.config.ConfigurationContext)
Failed doctest test for
zope.configuration.config.ConfigurationContext.checkDuplicate
File src/zope/configuration/config.py, line 256, in checkDuplicate
--
File src/zope/configuration/config.py, line 278, in
zope.configuration.config.ConfigurationContext.checkDuplicate
Failed example:
try:
c.checkDuplicate(d + os.path.normpath('/bar.zcml'))
except ConfigurationError, e:
str(e).endswith(bar.zcml' included more than once)
Expected:
True
Got nothing
Failure in test path (zope.configuration.config.ConfigurationContext)
Failed doctest test for zope.configuration.config.ConfigurationContext.path
File src/zope/configuration/config.py, line 212, in path
--
File src/zope/configuration/config.py, line 227, in
zope.configuration.config.ConfigurationContext.path
Failed example:
c.path(y/z) == d + os.path.normpath(/y/z)
Expected:
1
Got:
False
--
File src/zope/configuration/config.py, line 229, in
zope.configuration.config.ConfigurationContext.path
Failed example:
c.path(y/./z) == d + os.path.normpath(/y/z)
Expected:
1
Got:
False
--
File src/zope/configuration/config.py, line 231, in
zope.configuration.config.ConfigurationContext.path
Failed example:
c.path(y/../z) == d + os.path.normpath(/z)
Expected:
1
Got:
False
In test.py of Zope3 we insert abosolute path at the beginning of path.
But for individual packages we use relative path.
Here is relevant code from test.py of Zope 3:
here = os.path.abspath(os.path.dirname(sys.argv[0]))
src = os.path.join(here, 'src')
sys.path.insert(0, src)
And from test.py of an individual package:
src = os.path.join(os.path.split(sys.argv[0])[0], 'src')
sys.path.insert(0, src)
So, can I change the all the invidual pacakge's test.py to insert absolute path?
or only the test.py file of zope.configuration (test.py is not yet added)
Regards,
Baiju M
[1] ftp://ftp.berlios.de/pub/zissue/z3/
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Path used in test.py for Zope 3 and individual packages.
On 10/21/06, Baiju M [EMAIL PROTECTED] wrote: [1] ftp://ftp.berlios.de/pub/zissue/z3/ Sorry, this is a temporary location, will be removed soon. 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
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 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. Faassen, it is difficult to manually synchronise two wikis, so please announce the new wiki, so that other developers can add new content there. 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
On 10/21/06, Jim Fulton [EMAIL PROTECTED] wrote: At: http://dev.zope.org/Zope3/ZopeConfigurationProcessingAndSideEffects I've written an informational proposal 'IsInformational' is a new wiki badge? I have added this to: http://zope3.zwiki.org/IsInformational under http://zope3.zwiki.org/WikiBadge 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.i18n dependency in zope.configuration
On 10/22/06, Fred Drake [EMAIL PROTECTED] wrote: On 10/21/06, Baiju M [EMAIL PROTECTED] wrote: I was looking at zope.configuration source, zope.i18n is given as a dependency in DEPENDENCIES.cfg, but it is not imported anywhere in that package. So, can I remove 'zope.i18n' line from DEPENDENCIES.cfg file? It looks like zope.i18n can go, but the simpler zope.i18nmessageid needs to be added (done on the trunk). Maintenance branches should be checked for similar updates. So any module imported should be added as a dependency. Then, what about modules imported in test files (*.txt or test*.py files) ? 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] Re: [Zope3-checkins] SVN: Zope3/trunk/ Fixed encoding of newlines, carriage returns, and tabs when
[Changed To address to zope3-dev] On 10/20/06, Baiju M [EMAIL PROTECTED] wrote: On 10/20/06, Fred L. Drake, Jr. [EMAIL PROTECTED] wrote: Log message for revision 70828: Fixed encoding of newlines, carriage returns, and tabs when encoding attributes for widgets so we're consistent under all Python 2.4.x versions (including 2.4.4, which failed tests before). So, we have to merge this to 3.2 and 3.3 branches? I just done this in my check out and test with Python 2.4.4 and 2.4.3 versions, all tests passed. Can I commit it? I ported this to 3.2 and 3.3 branches. Untill the next point releases, some tests will be failed when using Python 2.4.4 . So, we have to make new point releases now? 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] Set 'svn:keywords Id' to *.py files
Hi all, Few weeks back when I added a new file I forgot to set 'svn:keywords Id', but I added '$Id$' in that file. I thought there will be few more files like that, so I tried this command: $ find . -name *.py|xargs grep \$Id[\:|\s*\$] | cut -f 1 -d :|xargs svn ps svn:keywords Id then: $ svn diff | grep svn:keywords |wc -l 233 I run the tests, all passed. So, can I commit this? Here is the diff: http://zissue.berlios.de/z3/keywords.diff 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] Zope3Faq is moved from KPUG wiki
Hi all, Now Zope3Faq is disconnected from Kerala :) Thanks for contributing to http://kpug.zwiki.org/Zope3Faq (This was Kerala Python User Group Wiki) Now I have merged the questions from this page to http://zope3.zwiki.org/FAQ This is the official FAQ (will be available from wiki.zope.org later) So, please continue your contributions. Now there is sections, so we have to re-organise it a bit. I will move other pages from here to new wiki. 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.interface category in pypi
Hi Fred, Can you add add 'Framework :: Zope3' to category here: http://cheeseshop.python.org/pypi/zope.interface Now it's not listed here: http://cheeseshop.python.org/pypi?:action=browseamp;c=515 May be we have to update that release? 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] Add zope.deferredimport to svn toplevel
On 10/7/06, Jim Fulton [EMAIL PROTECTED] wrote: Baiju M wrote: Hi, Can I commit zope.deferredimport to the toplevel of svn, like zope.interface,zope.proxy etc. That would be great. Commited. Will you also release an egg to pypi? :) Done. Also added 'J1m' as owner. http://cheeseshop.python.org/pypi/zope.deferredimport I have added README.txt, setup.py, test.py etc. see this: http://zissue.berlios.de/z3/zope.deferredimport.tar.bz2 Please confirm these steps: $ svn mkdir svn+ssh://[EMAIL PROTECTED]/repos/main/zope.deferredimport $ svn co svn+ssh://[EMAIL PROTECTED]/repos/main/zope.deferredimport $ cd zope.deferredimport $ mkdir trunk $ mkdir branches $ mkdir tags $ svn add trunk branches tags Minor note: I typically set up the full tree in the original transaction that sets up the project. You can give multiple directories on the mkdir line. I have a script named z that echos the repo url, so I'd do: svn mkdir `z`/zope.deferredimport `z`/zope.deferredimport/trunk `z`/zope.deferredimport/branches `z`/zope.deferredimport/tags Thanks, I used this trick :) $ cd trunk (Now add package here, then set svn:external to (in src/zope) deferredimport svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/deferredimport Also set svn:ignore in / and src/) It would be nice to also turn it into a buildout so that you could run it's tests in a project checkout. See for example: http://www.python.org/pypi/zc.buildout#work-on-a-package First I will learn zc.buildout, then I will try. 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] Buildbot for individual packages
Hi all, Since we are going for eggification, it is necessary to add buildbot support for indiviaul packages. Can we make sure 'python setup.py build' also works? For example zope.component build was not working, because in trunk we removed zope.component.bbb.tests. But we didn't removed this from setup.py of zope.component 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] Add zope.deferredimport to svn toplevel
Hi, Can I commit zope.deferredimport to the toplevel of svn, like zope.interface,zope.proxy etc. I have added README.txt, setup.py, test.py etc. see this: http://zissue.berlios.de/z3/zope.deferredimport.tar.bz2 Please confirm these steps: $ svn mkdir svn+ssh://[EMAIL PROTECTED]/repos/main/zope.deferredimport $ svn co svn+ssh://[EMAIL PROTECTED]/repos/main/zope.deferredimport $ cd zope.deferredimport $ mkdir trunk $ mkdir branches $ mkdir tags $ svn add trunk branches tags $ cd trunk (Now add package here, then set svn:external to (in src/zope) deferredimport svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/deferredimport Also set svn:ignore in / and src/) Then commit. 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[2]: help, Z3.2.2 build fails on win32 with ZConfig
On 10/6/06, Adam Groszer [EMAIL PROTECTED] wrote: http://dev.zope.org/Zope3/MakingARelease says you should be making a tarball with ../../zpkgtools/bin/zpkg -r Zope-3.3.0b1 -C Zope.cfg Zope but of course you need to replace Zope-3.3.0b1 with the current tag (which is 3.2.2). My suspicion is that Adam forgot to do that and so he built a tarball of 3.2.2, but with zopeskel from 3.3.x. I'm sorry, but I did it. But the required command is not exactly the same. http://www.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/ZopeWindowsRelease says that I should run python ..\zpkg\bin\zpkg -C releases\Zope.cfg -v 3.1.0c1 -t Zope-win Can you try this: python ..\zpkg\bin\zpkg -C releases\Zope.cfg -r Zope-3.2.2 -v 3.2.2 -t Zope-win The ` -r Zope-3.2.2` option is important, so it will get zopeskel from here: svn://svn.zope.org/repos/main/Zope3/tags/Zope-3.2.2/zopeskel/ 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] Re: Re[2]: help, Z3.2.2 build fails on win32 with ZConfig
On 10/6/06, Adam Groszer [EMAIL PROTECTED] wrote: It looks like the instructions aren't complete here. You should be specifying -r 3.2.2 here so that it looks at the tag. Lot better :-) now it works. Now I start the upload. Can you update ZopeWindowsRelease wiki page also? 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] help, Z3.2.2 build fails on win32 with ZConfig
On 10/5/06, Adam Groszer [EMAIL PROTECTED] wrote: Hello, I built Z3.2.2 on win32, but after installing the result and creating an instance it fails. I don't have a clou where and what to look for. C:\zopeinstbin\runzope Error: 'formatter' is not a known key name (line 103 in file:/C|/zopeinst/etc/zope.conf) For help, use c:\zopeinst\bin\runzope -h I am not sure about the reason, but another mail suggest to comment `formatter` line: http://mail.zope.org/pipermail/zope3-users/2006-September/004415.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] Python version for Zope 3.4 ?
On 9/29/06, Martijn Faassen [EMAIL PROTECTED] wrote: It's going to be a significant investment of work to make sure everything works with Python 2.5. Either someone credible steps up, convinces us, and does the work, and we all move over to Python 2.5. If they don't, we do it the next cycle. Initially I asked this question just out of curiosity, because some other Python web frameworks already started some efforts [1]. [1] http://code.djangoproject.com/ticket/2771 http://trac.turbogears.org/turbogears/wiki/python2.5 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] Python version for Zope 3.4 ?
On 9/29/06, Baiju M [EMAIL PROTECTED] wrote: On 9/29/06, Martijn Faassen [EMAIL PROTECTED] wrote: It's going to be a significant investment of work to make sure everything works with Python 2.5. Either someone credible steps up, convinces us, and does the work, and we all move over to Python 2.5. If they don't, we do it the next cycle. Initially I asked this question just out of curiosity, because some other Python web frameworks already started some efforts [1]. Let me fix some simple warings in trunk like this: Warning: 'with' will become a reserved keyword in Python 2.6 I know that this not going to help us to support Python 2.5, though just a beginning. 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 3.3.1 and 3.4
On 9/28/06, Christian Theune [EMAIL PROTECTED] wrote: Please provide fixes and tests on the trunk and the 3.3 branch. What about 3.2, dropped ? Regards, Baiju M ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
