[Zope-dev] Re: zope.app.authentication and zope.app.container broken doctests
Wichert Akkerman wrote: I've re-tagged and reuploaded new versions zope.app.container 3.5.6 and zope.app.authentication 3.4.3. This should be ok. Re-uploading is very problematic: if anyone has the previous version in their buildout download cache they will never get the new version. I prefer a minor version number bump instead of re-uploading. That's what Christophe did. His choice of words is just a bit confusing. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.authentication and zope.app.container broken doctests
Previously Christophe Combelles wrote: > Marius Gedminas a écrit : > >Something seems to be wrong with zope.app.authentication 3.4.2 and > >zope.app.container 3.5.5 eggs: > > > >Test-module import failures: > > > >Module: zope.app.authentication.tests > > > >ValueError: line 13 of the docstring for principalfolder.txt has > >inconsistent leading whitespace: '\r' > > > > > >Module: zope.app.authentication.browser.tests > > > >ValueError: line 18 of the docstring for principalfolder.txt has > >inconsistent leading whitespace: '\r' > > > > > >Module: zope.app.container.browser.tests.test_contents_functional > > > >ValueError: line 12 of the docstring for index.txt has inconsistent > >leading whitespace: '\r' > > > > > >Module: zope.app.container.tests.test_constraints > > > >ValueError: line 11 of the docstring for constraints.txt has > >inconsistent leading whitespace: '\r' > > > >Ideas? Eggs built on Windows? Missing svn:eol-style=native properties? > >Mixed > >\n and \r\n line endings? > > > >Marius Gedminas > > I've re-tagged and reuploaded new versions zope.app.container 3.5.6 and > zope.app.authentication 3.4.3. This should be ok. Re-uploading is very problematic: if anyone has the previous version in their buildout download cache they will never get the new version. I prefer a minor version number bump instead of re-uploading. Wichert. -- Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.authentication and zope.app.container broken doctests
Marius Gedminas a écrit : Something seems to be wrong with zope.app.authentication 3.4.2 and zope.app.container 3.5.5 eggs: Test-module import failures: Module: zope.app.authentication.tests ValueError: line 13 of the docstring for principalfolder.txt has inconsistent leading whitespace: '\r' Module: zope.app.authentication.browser.tests ValueError: line 18 of the docstring for principalfolder.txt has inconsistent leading whitespace: '\r' Module: zope.app.container.browser.tests.test_contents_functional ValueError: line 12 of the docstring for index.txt has inconsistent leading whitespace: '\r' Module: zope.app.container.tests.test_constraints ValueError: line 11 of the docstring for constraints.txt has inconsistent leading whitespace: '\r' Ideas? Eggs built on Windows? Missing svn:eol-style=native properties? Mixed \n and \r\n line endings? Marius Gedminas I've re-tagged and reuploaded new versions zope.app.container 3.5.6 and zope.app.authentication 3.4.3. This should be ok. Christophe ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Please no version numbers in setup.py [was: SVN: Zope2.buildout/tags/2.11.1/setup.py Pin / fix up dependencies based on comparison with monolith.]
On Wednesday 06 August 2008, Tres Seaver wrote: > I am uninterested in making the Z2 eggs depend on a KGS / index which is > not managed specifically for the benefit of the corresponding Zope2 > version: there is zero chance that such a KGS will be truly "known > good" for a configuration which its managers don't test or run. This is no 1. We do run the tests. 2. You can always create Zope 2 KGS that extends a specific Zope 3 version. > Users who wanted to deploy exactly 2.11.1 would use the first index; > those who wanted to do updates would use the second. Buildout users > would need to write recipes which were able to use different indexes for > different eggs, if they needed eggs not in the "Z2 KGS" index. So don't use the index. For our commercial stuff I use the released versions.cfg file and then overwrite the versions as needed. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter" ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: zcml filtering
Philipp von Weitershausen wrote: But yes, that sounds like a great idea. Feel free to do it ;). I probably won't have time to worry about this any time soon. I'm just trying to fix an issue at hand. Thanks a lot for doing that, by the way. :) Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Please no version numbers in setup.py [was: SVN: Zope2.buildout/tags/2.11.1/setup.py Pin / fix up dependencies based on comparison with monolith.]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Philipp von Weitershausen wrote: > Tres Seaver wrote: >> Log message for revision 89399: >> Pin / fix up dependencies based on comparison with monolith. >> > > Thanks for picking this up! > > I do, however, strongly object to pinning versions of dependencies in > setup.py like this. What's the point of eggifying Zope 2 in the first > place then if not for the ability to upgrade individual libraries to > newer versions with bugfixes or features? > > Instead of pinning versions in setup.py, we should rather include a list > of known-good versions, or even better, add the Zope 2 eggs to the Zope > KGS. That way, by default, you'd get the known good set but you could > deviate from it as necessary. More importantly, by having one good set > (instead of a setup.py here, a versions.cfg there and another list > somewhere else), the KGS becomes much easier to maintain. I am uninterested in making the Z2 eggs depend on a KGS / index which is not managed specifically for the benefit of the corresponding Zope2 version: there is zero chance that such a KGS will be truly "known good" for a configuration which its managers don't test or run. This is no A better fix would be to run a set of indexes for the Z2 eggs, e.g.: http://download.zope.org/distribution/Zope-2.11.1/index/simple would contain *only* the egg versions which shipped with Zope 2.11.1 (the versions currently pinneed in setup.py). Note that I have already put this index up, with the "pinned" version of the Zope-2.11.1 sdist. Another index, e.g.:: http://download.zope.org/distribution/Zope-2.11/index/simple would contain the same eggs, plus updated versions known to work with Zope 2.11.x. Users who wanted to deploy exactly 2.11.1 would use the first index; those who wanted to do updates would use the second. Buildout users would need to write recipes which were able to use different indexes for different eggs, if they needed eggs not in the "Z2 KGS" index. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIme/i+gerLs4ltQ4RAk2HAKC4tGZr8EwNlopQcK6l88jcyHvO7wCgpkY5 7k1Wn1P0HfZbEiCl6r3+x2M= =MX2E -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: zcml filtering
El 6 Aug 2008, a las 17:17 , Roger Ineichen escribió: I'm +1 on zc.configuration. z3c.unconfigure, however, will contain zope.component specific code to "unconfigure" subscribers (which currently have no useful discriminator). So it's a hack to make it work with existing Zope code out there. If zope.component.zcml were changed to emit useful actions for (and , too!), we could solely rely on shooting down actions and the code could find its way into zope.configuration. That will only help us with future Zope code, not with existing code out there (which this is for). Feel free to undertake this :) That's a good argument but valid for any development or improvment on existing code/packages. It's about being pragmatic. We need to this to work on existing code (Zope 3.3 to be exact). We can't just upgrade zope.configuration. The bad thing is that we now have 3 packages for one thing doing right. It's unfortunate, but things could be worse. I'm +1 too for a simple zope.configuration package which offers the API for doing configuration how it should. What do you think about to release z3c.unconfigure and merge it to zope.configuration after the release. So we have both options and a simple setup for the future. Not forgetting to give and decent discriminators. But yes, that sounds like a great idea. Feel free to do it ;). I probably won't have time to worry about this any time soon. I'm just trying to fix an issue at hand. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
AW: [Zope-dev] Re: zcml filtering
Hi Philipp > Betreff: Re: [Zope-dev] Re: zcml filtering [...] > I'm +1 on zc.configuration. > > z3c.unconfigure, however, will contain zope.component > specific code to "unconfigure" subscribers (which currently > have no useful discriminator). So it's a hack to make it work > with existing Zope code out there. If zope.component.zcml > were changed to emit useful actions for (and > , too!), we could solely rely on shooting down > actions and the code could find its way into > zope.configuration. That will only help us with future Zope > code, not with existing code out there (which this is for). > > Feel free to undertake this :) That's a good argument but valid for any development or improvment on existing code/packages. The bad thing is that we now have 3 packages for one thing doing right. I'm +1 too for a simple zope.configuration package which offers the API for doing configuration how it should. What do you think about to release z3c.unconfigure and merge it to zope.configuration after the release. So we have both options and a simple setup for the future. Regards Roger Ineichen ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: zcml filtering
El 6 Aug 2008, a las 16:47 , Stephan Richter escribió: On Wednesday 06 August 2008, Philipp von Weitershausen wrote: I'm working on a package for this functionality in z3c.unconfigure right now. Name inspired by Martin's suggestion above; my original prototype used had a different name but this is much better :). Couldn't we just merge zc.configuration and z3c.unconfigure into zope.configuration? Everyone who wants to use our configuration system certainly wants this functionality as well. I'm +1 on zc.configuration. z3c.unconfigure, however, will contain zope.component specific code to "unconfigure" subscribers (which currently have no useful discriminator). So it's a hack to make it work with existing Zope code out there. If zope.component.zcml were changed to emit useful actions for (and , too!), we could solely rely on shooting down actions and the code could find its way into zope.configuration. That will only help us with future Zope code, not with existing code out there (which this is for). Feel free to undertake this :) ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: zcml filtering
On Wednesday 06 August 2008, Philipp von Weitershausen wrote: > I'm working on a package for this functionality in z3c.unconfigure right > now. Name inspired by Martin's suggestion above; my original prototype > used had a different name but this is much better :). Couldn't we just merge zc.configuration and z3c.unconfigure into zope.configuration? Everyone who wants to use our configuration system certainly wants this functionality as well. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter" ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: zcml filtering
Marius Gedminas wrote: On Tue, Aug 05, 2008 at 10:36:30PM +0100, Martin Aspeli wrote: Subscribers and subscription adapters are particularly bad in this way, since they are unnamed and thus can't be "overridden", only amended to. We've talked about an "off" switch for ZCML before. Given that we have a configuration machine that's capable of doing overrides based on discriminators, why couldn't we have support for negatives, e.g. This could use a special _context that would record callables and discriminators, and then look for the corresponding callables/discriminators in the real context and remove them before that context was configured. Subscribers don't have discriminators, unfortunately. Indeed they don't. That just makes them harder to track down, though. I'm working on a package for this functionality in z3c.unconfigure right now. Name inspired by Martin's suggestion above; my original prototype used had a different name but this is much better :). ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: zcml filtering
On Tue, Aug 05, 2008 at 10:36:30PM +0100, Martin Aspeli wrote: > Subscribers and subscription adapters are particularly bad in this way, > since they are unnamed and thus can't be "overridden", only amended to. > > We've talked about an "off" switch for ZCML before. Given that we have a > configuration machine that's capable of doing overrides based on > discriminators, why couldn't we have support for negatives, e.g. > > > > > > This could use a special _context that would record callables and > discriminators, and then look for the corresponding > callables/discriminators in the real context and remove them before that > context was configured. Subscribers don't have discriminators, unfortunately. Marius Gedminas -- Be cheerful. Strive to be happy Oh, and we just set fire to your desktop. signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 5 OK
Summary of messages to the zope-tests list. Period Tue Aug 5 11:00:00 2008 UTC to Wed Aug 6 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Tue Aug 5 20:50:31 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/009965.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Tue Aug 5 20:52:04 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/009966.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Tue Aug 5 20:53:34 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/009967.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Tue Aug 5 20:55:04 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/009968.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Tue Aug 5 20:56:34 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/009969.html ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] failures in zope.testing trunk r89432 on windows
Hi All,
Is anyone else seeing these:
C:\LocalSVN\zope.testing>bin\test.exe
Running zope.testing.testrunner.layer.UnitTests tests:
Set up zope.testing.testrunner.layer.UnitTests in 0.000 seconds.
Failure in test
c:\localsvn\zope.testing\src\zope\testing\testrunner\testrunner-
debugging-layer-setup.test
Failed doctest test for testrunner-debugging-layer-setup.test
File
"c:\localsvn\zope.testing\src\zope\testing\testrunner\testrunner-debuggin
g-layer-setup.test", line 0
--
File
"c:\localsvn\zope.testing\src\zope\testing\testrunner\testrunner-debugging-
layer-setup.test", line 45, in testrunner-debugging-layer-setup.test
Failed example:
try:
zope.testing.testrunner.run(['--path', dir, '-D'])
finally: sys.stdin = real_stdin
# doctest: +ELLIPSIS
Exception raised:
Traceback (most recent call last):
File "c:\localsvn\zope.testing\src\zope\testing\doctest.py", line
1356, in
__run
compileflags, 1) in test.globs
File "", line
2, in ?
File
"c:\localsvn\zope.testing\src\zope\testing\testrunner\__init__.py", l
ine 33, in run
runner.run()
File
"c:\localsvn\zope.testing\src\zope\testing\testrunner\runner.py", lin
e 129, in run
feature.global_setup()
File
"c:\localsvn\zope.testing\src\zope\testing\testrunner\find.py", line
343, in global_setup
tests = find_tests(self.runner.options, self.runner.found_suites)
File
"c:\localsvn\zope.testing\src\zope\testing\testrunner\find.py", line
53, in find_tests
for suite in found_suites:
File
"c:\localsvn\zope.testing\src\zope\testing\testrunner\find.py", line
103, in find_suites
suite = StartUpFailure(
File
"c:\localsvn\zope.testing\src\zope\testing\testrunner\find.py", line
36, in __init__
post_mortem(exc_info)
File
"c:\localsvn\zope.testing\src\zope\testing\testrunner\runner.py", lin
e 717, in post_mortem
pdb.post_mortem(exc_info[2])
File "C:\Python24\lib\pdb.py", line 1016, in post_mortem
while t.tb_next is not None:
AttributeError: 'NoneType' object has no attribute 'tb_next'
A message on stderr. Please ignore (expected in test output).
Failure in test
c:\localsvn\zope.testing\src\zope\testing\testrunner\testrunner-
coverage-win32.txt
Failed doctest test for testrunner-coverage-win32.txt
File
"c:\localsvn\zope.testing\src\zope\testing\testrunner\testrunner-coverage
-win32.txt", line 0
--
File
"c:\localsvn\zope.testing\src\zope\testing\testrunner\testrunner-coverage-w
in32.txt", line 14, in testrunner-coverage-win32.txt
Failed example:
ignore = testrunner.TestIgnore(WinOptions())
Exception raised:
Traceback (most recent call last):
File "c:\localsvn\zope.testing\src\zope\testing\doctest.py", line
1356, in
__run
compileflags, 1) in test.globs
File "", line 1, in ?
AttributeError: 'module' object has no attribute 'TestIgnore'
--
File
"c:\localsvn\zope.testing\src\zope\testing\testrunner\testrunner-coverage-w
in32.txt", line 15, in testrunner-coverage-win32.txt
Failed example:
ignore._test_dirs
Exception raised:
Traceback (most recent call last):
File "c:\localsvn\zope.testing\src\zope\testing\doctest.py", line
1356, in
__run
compileflags, 1) in test.globs
File "", line 1, in ?
NameError: name 'ignore' is not defined
--
File
"c:\localsvn\zope.testing\src\zope\testing\testrunner\testrunner-coverage-w
in32.txt", line 20, in testrunner-coverage-win32.txt
Failed example:
ignore.names('r:\\winproject\\src\\blah\\foo\\baz.py', 'baz')
Exception raised:
Traceback (most recent call last):
File "c:\localsvn\zope.testing\src\zope\testing\doctest.py", line
1356, in
__run
compileflags, 1) in test.globs
File "", line 1, in ?
NameError: name 'ignore' is not defined
--
File
"c:\localsvn\zope.testing\src\zope\testing\testrunner\testrunner-coverage-w
in32.txt", line 22, in testrunner-coverage-win32.txt
Failed example:
ignore.names('R:\\winproject\\src\\blah\\foo\\baz.py', 'baz')
Exception raised:
Traceback (most recent call last):
File "c:\localsvn\zope.testing\src\zope\testing\doctest.py", line
1356, in
__run
compileflags, 1) in test.globs
File "", line 1, in ?
NameError: name 'ignore' is not defined
--
File
"c:\localsvn\zope.testing\src\zope\testing\testrunner\testrunner-coverage-w
in32.txt", line 24, in testrunner-coverage-win32.txt
Failed example:
ignore.names('r:\\winproject\\src\\blah\\bar\\zab.py', 'zab')
Exception raised:
Traceback (most
