Re: [Zope-dev] misterious btree issue

2008-11-06 Thread Tim Peters
[Jim Fulton] In particular, it might have a reference to the key in an internal BTree node. (I don't know this to be true, but I wouldn't be surprised if it was true.) It was true when I was working on BTrees ... here, from

Re: [Zope-dev] difference between OOSet and OOTreeSet?

2007-03-01 Thread Tim Peters
[Chris Withers] Wondering if someone could tell me the difference between an OOSet and an OOTreeSet? OOSet is to OOTreeSet as OOBucket is to OOBTree. An OOTreeSet is built out of leaf-level OOSets in exactly the same way an OOBTree is built out of leaf-level OOBuckets. More at:

Re: [Zope-dev] Maintainer of Zope 2 Windows builds?

2006-10-09 Thread Tim Peters
[Andreas Jung] Who is currently in charge or who feels responsible for the Windows builds? [Sidnei da Silva] Tim Peters. [Chris Withers] Er, no. Tim isn't even at Zope Corp anymore, as far as I know... [Sidnei] That shouldn't be related, should it? Don't know about should

Re: [Zope] ZODB install time error

2006-08-16 Thread Tim Peters
[P. Nagaraj] [ZODB3-3.4.0]# python test.py Running tests from build/lib.linux-i686-2.3 Running unit tests: Error in test testUmask (zdaemon.tests.testzdrun.ZDaemonTests) Traceback (most recent call last): File build/lib.linux-i686-2.3/zdaemon/tests/testzdrun.py, line 75, in tearDown

[Zope-Checkins] SVN: Zope/tags/2-8-8/inst/WinBuilders/mk/ Checking into a tag is evil, but the tag was made with

2006-07-31 Thread Tim Peters
Log message for revision 69323: Checking into a tag is evil, but the tag was made with incorrect version numbers in two of the makefiles needed to build the Windows installer for 2.8.8. Changed: U Zope/tags/2-8-8/inst/WinBuilders/mk/python.mk U

[Zope-Checkins] SVN: Zope/tags/2.9.4/inst/WinBuilders/mk/common.mk Checking in on a tag is evil, but the code for finding

2006-07-31 Thread Tim Peters
Log message for revision 69324: Checking in on a tag is evil, but the code for finding Inno Setup was completely broken. Changed: U Zope/tags/2.9.4/inst/WinBuilders/mk/common.mk -=- Modified: Zope/tags/2.9.4/inst/WinBuilders/mk/common.mk

Re: [Zope-dev] Windows Installers

2006-07-31 Thread Tim Peters
[Sidnei da Silva] Seems like we are seeing a shortage of volunteers for building the Zope Installers for Windows. IOW, nothing has changed :-) I haven't seen Tim Peters around for a while, and Chris Withers seems to have stepped down now. I'm around, but don't pay particular attention

Re: [Zope-dev] Windows Installers

2006-07-31 Thread Tim Peters
[Sidnei da Silva[ So we need a 2.8.8 and 2.9.4 installers. OK, I uploaded a Windows installer for 2.8.8. There were two -all test failures: ERROR: test_OFS_ObjectManager__importObjectFromFile_xml (OFS.tests.test_XMLExportImport.XMLExportImportTests)

Re: [Zope-dev] Re: Zope 2.9.4

2006-07-15 Thread Tim Peters
[Andreas Jung] ... I think we should make another internal ZODB release. The current svn:externals for the ZODB (and other modules) use a revision number instead of a tag. This reminds me of some former discussion whether to use revision numbers or tags...what was the result of this discussion.

Re: [Zope-dev] Re: Zope 2.9.4

2006-07-15 Thread Tim Peters
[Tim] I used tags for ZODB until I gave in to complaints about that, and switched to using revision numbers. The real complaint about using a tagged external is that when the tag changes, SVN isn't smart enough to do an incremental update. Instead, when you update after an external tag

[Zope-Checkins] SVN: Zope/tags/2-8-6/inst/WinBuilders/mk/python.mk Move to build 207 of pywin32 (this should have been

2006-06-21 Thread Tim Peters
Log message for revision 65842: Move to build 207 of pywin32 (this should have been done before Zope 2.8.6 was tagged). Changed: U Zope/tags/2-8-6/inst/WinBuilders/mk/python.mk -=- Modified: Zope/tags/2-8-6/inst/WinBuilders/mk/python.mk

[Zope-Checkins] SVN: Zope/tags/2-8-6/inst/WinBuilders/README.txt Move to build 207 of pywin32 (this should have been

2006-06-21 Thread Tim Peters
Log message for revision 65843: Move to build 207 of pywin32 (this should have been done before Zope 2.8.6 was tagged). Changed: U Zope/tags/2-8-6/inst/WinBuilders/README.txt -=- Modified: Zope/tags/2-8-6/inst/WinBuilders/README.txt

[Zope-Checkins] SVN: Zope/tags/2-8-6/inst/WinBuilders/etc/zope.iss.in More installer bitmap repair.

2006-06-21 Thread Tim Peters
Log message for revision 65845: More installer bitmap repair. Changed: U Zope/tags/2-8-6/inst/WinBuilders/etc/zope.iss.in -=- Modified: Zope/tags/2-8-6/inst/WinBuilders/etc/zope.iss.in === ---

[Zope-Checkins] SVN: Zope/tags/2-8-6/inst/WinBuilders/etc/zeo.iss.in Repair distorted installer bitmaps.

2006-06-21 Thread Tim Peters
Log message for revision 65844: Repair distorted installer bitmaps. Changed: U Zope/tags/2-8-6/inst/WinBuilders/etc/zeo.iss.in -=- Modified: Zope/tags/2-8-6/inst/WinBuilders/etc/zeo.iss.in === ---

[Zope-Checkins] SVN: Zope/branches/Zope-2_8-branch/inst/WinBuilders/ Merge revs 65842 65843 65844 65845 from Zope/tags/2-8-6/.

2006-06-21 Thread Tim Peters
Log message for revision 65846: Merge revs 65842 65843 65844 65845 from Zope/tags/2-8-6/. Move to pywin32 build 207, and repair mangling of installer bitmaps. These should have been done before the 2.8.6 tag was made. Changed: U

Re: [Zope3-dev] Re: [Zope-dev] Re: 64-bit BTrees

2006-04-13 Thread Tim Peters
[Tres Seaver] ... I would guess that if you could do a census of all the OIDs in all the Datas.fs in the world, a significant majority of them would be instances of classes declared in IOBTree / IIBTree (certainly the bulk of *transaction* records are going to be tied up with them). Provided

Re: [Zope] repozo.py

2006-03-08 Thread Tim Peters
[Dennis Allison] We are (finally) moving to repozo for our backups. We are running a mixed collection of Zopes -- mostly Zope 2.7.6, Zope 2.8.X and Zope 2.9.0. For the near term we cannot move to a single release. There are differences between the versions of repozo distributed with the

Re: [Zope-dev] Windows Binary for 2.8.6?

2006-03-06 Thread Tim Peters
[Chris Withers] I notice 2.8.6 doesn't have a Windows binary either. What's the build process for that? Try to detect the pattern between this and previous answers ;-): http://svn.zope.org/Zope/branches/Zope-2_8-branch/inst/WinBuilders/README.txt I have a feeling I won't be able to help

Re: [Zope-dev] Zope 2.9 releases for Windows?

2006-03-03 Thread Tim Peters
[Chris Withers] ... How should I run all the Zope tests once I have a candidate build? Section Testing Zope in http://svn.zope.org/Zope/trunk/inst/WinBuilders/README.txt ___ Zope-Dev maillist - Zope-Dev@zope.org

Re: [Zope-dev] Zope 2.9 releases for Windows?

2006-02-26 Thread Tim Peters
[Chris Withers] I see there are no Zope 2.9 releases for Windows. There probably should be ;-) There's a Windows installer for Zope 2.9.0 on its download page: http://www.zope.org/Products/Zope/2.9.0 Or do you mean 2.9.1? What can I do to help with that? Provoke Sidnei into responding

Re: [Zope-dev] Python warnings behavior and stacklevel=2

2006-02-10 Thread Tim Peters
[Julien Anguenot] I'm having some problems with the warnings module behavior. (Python-2.4.2 and Zope-2.9 trunk) [... traceback ... ] - Line 71 Module zLOG, line 140, in LOG Module warnings, line 61, in warn Module warnings, line 67, in warn_explicit TypeError: unsubscriptable

RE: [Zope-Checkins] SVN: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/ Repair invocation of Inno compiler -- it doesn't ( can't) work to

2006-01-26 Thread Tim Peters
[Tim Peters] Log message for revision 41456: Repair invocation of Inno compiler -- it doesn't ( can't) work to stick the path and /cc in the same quoted string. Unsure why that change was made (it worked fine before -- and now). [Sidnei da Silva] That change was so I can run

[Zope-Checkins] SVN: Zope/tags/2.9.0/inst/WinBuilders/ Merge tim-2.9-windows-installer branch.

2006-01-26 Thread Tim Peters
Log message for revision 41458: Merge tim-2.9-windows-installer branch. This is the code used to build the Zope 2.9.0 Windows installer. It bundles Python 2.4.2, lives in peace with zpkgtools, moves to InnoSetup 5, and simplifies most parts of the build-the- installer process.

[Zope-Checkins] SVN: Zope/branches/2.9/inst/WinBuilders/ Merge tim-2.9-windows-installer branch.

2006-01-26 Thread Tim Peters
Log message for revision 41460: Merge tim-2.9-windows-installer branch. This is the code used to build the Zope 2.9.0 Windows installer. It bundles Python 2.4.2, lives in peace with zpkgtools, moves to InnoSetup 5, and simplifies most parts of the build-the- installer process.

RE: [Zope-Checkins] SVN: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/ Repair invocation of Inno compiler -- it doesn't ( can't) work to

2006-01-26 Thread Tim Peters
[Sidnei da Silva] I can surely say that it doesn't work with the buildbot. Maybe because it's running as a Windows Service. Well, that's a goofy idea -- nothing runs right as a service ;-) ___ Zope-Checkins maillist - Zope-Checkins@zope.org

[Zope-Checkins] SVN: Zope/trunk/inst/WinBuilders/ Merge tim-2.9-windows-installer branch.

2006-01-26 Thread Tim Peters
Log message for revision 41462: Merge tim-2.9-windows-installer branch. This is the code used to build the Zope 2.9.0 Windows installer. It bundles Python 2.4.2, lives in peace with zpkgtools, moves to InnoSetup 5, and simplifies most parts of the build-the- installer process.

[Zope-Checkins] SVN: Zope/branches/tim-2.9-windows-installer/ This branch is no longer interesting -- it's been merged

2006-01-26 Thread Tim Peters
Log message for revision 41463: This branch is no longer interesting -- it's been merged to Zope trunk, 2.9 branch, and 2.9.0 tag. Changed: D Zope/branches/tim-2.9-windows-installer/ -=- ___ Zope-Checkins maillist - Zope-Checkins@zope.org

Re: [Zope] unpickle error on Data.fs pack

2006-01-25 Thread Tim Peters
[Gerhard Schmidt] since three days we have problems when packing the Data.fs. 2006-01-25T03:40:42 ERROR(200) zrpc:7266 Error raised in delayed method Traceback (most recent call last): File /usr/local/www/Zope/lib/python/ZEO/StorageServer.py, line 991, in run result =

Re: [Zope-Checkins] SVN: Zope/branches/tim-2.9-windows-installer/ - Collector #2002: fixed broken 'ls -R' functionality (didn't

2006-01-21 Thread Tim Peters
[Sidnei da Silva] Log message for revision 41394: - Collector #2002: fixed broken 'ls -R' functionality (didn't recurse properly subclasses of OFS.Folder) Changed: U Zope/branches/tim-2.9-windows-installer/doc/CHANGES.txt U

Re: [Zope-Checkins] SVN: Zope/branches/tim-2.9-windows-installer/ - Collector #2002: fixed broken 'ls -R' functionality (didn't

2006-01-21 Thread Tim Peters
[Sidnei da Silva] Log message for revision 41394: - Collector #2002: fixed broken 'ls -R' functionality (didn't recurse properly subclasses of OFS.Folder) [Tim Peters] This certainly doesn't belong on the Windows installer branch. Nothing outside of inst/WinBuilders

[Zope-dev] Re: [Zope3-dev] December release post-mortem

2006-01-19 Thread Tim Peters
... [Stephan Ricther] I have seen you take a similar approach to zope.testing and I found that painful just by watching the checkins. [Jim Fulton] I don't understand what you mean. Having a separate zope.testing project has been extremely useful. For example, in our comercial apps, we

Re: [Zope] zeopack: No handlers could be found for logger ZEO.zrpc

2006-01-19 Thread Tim Peters
[Cameron Beattie] When I run the following: python /usr/lib/zope/bin/zeopack.py -d 20 -h localhost -p 8100 I get an error: No handlers could be found for logger ZEO.zrpc As Dieter said, that's not an error in and of itself, it's just Python's logging module whining at you. ZEO.zrpc is

[Zope-dev] Re: [Zope3-dev] December release post-mortem

2006-01-18 Thread Tim Peters
We should distinguish between authoring the Windows build-the-installer code, and running that code. Making a Zope 2 Windows release consists of _running_ the build-the-installer code, and is easy. It's actually easier than building a Zope 3 Windows release: once the Python tarball, Zope 2

[Zope-dev] Re: Removing 'inst'

2006-01-15 Thread Tim Peters
[Philipp von Weitershausen] ... Therefore, just to reduce confusion, I would move Makefile.in and configure.py to the root (and remove the decoys). I'd also suggest we rename 'inst' to 'installer' so that it won't be confused with instance. Then again, this is just me and my weird sense of

Re: [Zope] Where oh where is Repozo

2006-01-15 Thread Tim Peters
[Jonathan Cyr] Where is the latest version of Repozo, the backup tool, kept? Is there a reason, that it's not included with the Zope install/utilities (at least the 2.7.x I'm using). [... time passes ...] Thanks for the quick response, I noticed that the my WinXP Zope (sandbox) doesn't

[Zope-Checkins] SVN: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/zope.mk Removed long-broken `test_zope` target.

2006-01-14 Thread Tim Peters
Log message for revision 41312: Removed long-broken `test_zope` target. Changed: U Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/zope.mk -=- Modified: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/zope.mk

Re: [Zope-dev] Re: Seeking brave souls to try Zope 2.9 Windows installer

2006-01-14 Thread Tim Peters
[Lennart Regebro] Only one real bug: No user is created (even though you type in name and password). Sorry, I'm not following this. The installer never offers to create a user (although it does ask you to supply a password for the fixed admin user). So you must be talking about something

[Zope-Checkins] SVN: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/README.txt Partially-working new instructions for running the tests.

2006-01-13 Thread Tim Peters
Log message for revision 41300: Partially-working new instructions for running the tests. The functional tests don't even try to run, but at least this exercises 6724 of the unit tests. Someone who understands how Zope3 testing was changed to work from a zpkgtools-based install

[Zope-Checkins] SVN: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/zope.mk Stop hiding the line that builds version.txt.

2006-01-13 Thread Tim Peters
Log message for revision 41301: Stop hiding the line that builds version.txt. Don't know why it was hidden before, but can't think of a reason, and the lack of makefile output showing its creation just confused the heck out of me for 10 minutes ;-). Changed: U

[Zope-Checkins] SVN: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/bin/makezope.bat Remove unused file.

2006-01-13 Thread Tim Peters
Log message for revision 41307: Remove unused file. The build-the-Windows-installer dance used to use it. Changed: D Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/bin/makezope.bat -=- Deleted: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/bin/makezope.bat

[Zope-dev] Re: Seeking brave souls to try Zope 2.9 Windows installer

2006-01-13 Thread Tim Peters
[Sidnei da Silva] Way to go Tim! You beat me to it. I was supposed to look at this soon but got back from vacation just this tuesday. I will make sure your installer gets testing and try to fix any eventual issues. Excellent! This may actually work ;-) While I'll be on vacation the next two

Re: [Zope-dev] Removing 'inst'

2006-01-13 Thread Tim Peters
[Philipp von Weitershausen] It seems that 'inst' holds nothing of value anymore except 'Makefile.in' and 'WinBuilders'. WRT Windows, that's certainly true on my Windows-installer branch. I don't know whether any of it is still useful on Linux. You seem to think Makefile.in is still useful,

Re: [Zope-dev] Removing 'inst'

2006-01-13 Thread Tim Peters
[Sidnei da Silva] I think there's a Makefile.win too, that is used by inst/configure.py on Windows. (I know because use it). There is a Makefile.win.in, but the build-the-Windows-installer process no longer uses it on my branch -- the branch doesn't use anything in the root of inst/ anymore,

[Zope-Checkins] SVN: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/ Pain, pain, and more pain.

2006-01-12 Thread Tim Peters
Log message for revision 41291: Pain, pain, and more pain. The build-the-installer process now completes, and running the installer creates something that may or may not be a working Zope. It starts fine as a Windows Service, and at least looks like a Zope ;-) Nothing in the

[Zope-dev] Seeking brave souls to try Zope 2.9 Windows installer

2006-01-12 Thread Tim Peters
Most of the last two days I've been whacking on Zope 2.9 to build a Zope 2 style Windows installer that bundles Python 2.4.2, and cooperates with the new zpkgtools-created tarball layout. The build-the-Windows-installer code got simpler as a result, but ... This work is being done on branch:

[Zope-Checkins] SVN: Zope/branches/tim-2.9-windows-installer/ Zope 2.9 went out without working code to build a Windows installer.

2006-01-11 Thread Tim Peters
Log message for revision 41263: Zope 2.9 went out without working code to build a Windows installer. This is a branch from the 2.9 tag to try to repair that. Changes here will be limited to the WinBuilder stuff. Changed: A Zope/branches/tim-2.9-windows-installer/ -=- Copied:

[Zope-Checkins] SVN: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/zope.mk For whatever reason, the tarball for 2.9.0 dropped -final from its name.

2006-01-11 Thread Tim Peters
Log message for revision 41268: For whatever reason, the tarball for 2.9.0 dropped -final from its name. The makefile has to know the actual name. Changed: U Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/zope.mk -=- Modified:

[Zope-Checkins] SVN: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/python.mk Python 2.4.2 is needed now.

2006-01-11 Thread Tim Peters
Log message for revision 41277: Python 2.4.2 is needed now. Changed: U Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/python.mk -=- Modified: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/python.mk

[Zope-Checkins] SVN: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/python.mk Untested first stab at moving to Python 2.4.2.

2006-01-11 Thread Tim Peters
Log message for revision 41278: Untested first stab at moving to Python 2.4.2. Changed: U Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/python.mk -=- Modified: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/python.mk

[Zope-Checkins] SVN: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/README.txt More words about the process, and corrections to specifics.

2006-01-11 Thread Tim Peters
Log message for revision 41280: More words about the process, and corrections to specifics. Changed: U Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/README.txt -=- Modified: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/README.txt

[Zope-Checkins] SVN: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/README.txt Fixed typo in new notes.

2006-01-11 Thread Tim Peters
Log message for revision 41281: Fixed typo in new notes. Removed ancient info about wrestling with Win98SE. Changed: U Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/README.txt -=- Modified: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/README.txt

[Zope-Checkins] SVN: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/common.mk Use immediate assignment to (greatly) speed the

2006-01-11 Thread Tim Peters
Log message for revision 41282: Use immediate assignment to (greatly) speed the heavily used utility variables that call out to a shell. Changed: U Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/common.mk -=- Modified:

[Zope-Checkins] SVN: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/zope.mk Remove compiled Python files from the tree before packaging.

2006-01-11 Thread Tim Peters
Log message for revision 41283: Remove compiled Python files from the tree before packaging. Convert line ends on more kinds of files. Changed: U Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/zope.mk -=- Modified:

[Zope-Checkins] SVN: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/zope.mk Moved version number to top of file.

2006-01-11 Thread Tim Peters
Log message for revision 41284: Moved version number to top of file. Changed: U Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/zope.mk -=- Modified: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/zope.mk

[Zope-Checkins] SVN: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/zope.mk install_zope: List one dependence per line.

2006-01-11 Thread Tim Peters
Log message for revision 41285: install_zope: List one dependence per line. Changed: U Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/zope.mk -=- Modified: Zope/branches/tim-2.9-windows-installer/inst/WinBuilders/mk/zope.mk

Re: [ZODB-Dev] Re: [Zope-dev] Re: zLOG module deprecated

2006-01-10 Thread Tim Peters
[Andreas Jung] ... Obviously ZEO (using TRACE) runs on Zope 3 without zLOG so specific extension can be handled locally. ZEO also runs on Zopes 2.8 and 2.9 without zLOG -- zLOG hasn't been used in ZODB since 3.2 (ZODBs 3.3, 3.4, 3.5, 3.6, and current trunk contain no references to zLOG). If

Re: [Zope-dev] Twice-annual releases and bugfixes?

2006-01-09 Thread Tim Peters
[Jeff Kowalczyk] What does the twice-annual release policy say about bugs and/or packaging errors that are identified and fixed within a very short time of the official release announcement? I think the answer you're looking for is that the policy says nothing about that. Every-6-months

[Zope-dev] RE: [ZODB-Dev] Re: zLOG module deprecated

2006-01-09 Thread Tim Peters
[Andreas Jung] ZODB defines these levels but I can not see any code in the ZODB package that actually uses these levels. Nevertheless, grep'ing the ZODB source for TRACE and BLATHER will find them. TRACE is used only in modules under ZEO/zrpc/, and gives extremely verbose output about

Re: [Zope-dev] Re: zLOG module deprecated

2006-01-09 Thread Tim Peters
[Fred Drake] Nobody should be using the zLOG levels with the logging package, but rather use the logging package levels. So in the end, there's no need for Zope to be defining levels at all, only conventions for how the levels are used. The logging package supports defining as many

Re: [Zope] Zope 2.8.5 install

2006-01-09 Thread Tim Peters
[Robert Conner] Thanks for compiling that and setting up the windows installer. However, I don't believe it works. Sorry it took me so long to get back to you. I wanted to try installing this on a second computer before I wrote back. On both of them it What is it? Please spell out exactly

Re: [Zope] Zope 2.8.5 install

2006-01-09 Thread Tim Peters
[Robert Conner] Well color me purple, it does work. Good! How could anything on Windows fail to work ;-)? I was just so used to seeing the Zope Ready to handle Requests message that when it never appeared I just assumed it was not working at all. I've broken Zope on my computer 100 times

Re: [Zope-dev] Re: SVN: Zope/branches/2.9/ Move to ZODB 3.6 final.

2006-01-06 Thread Tim Peters
[Florent Guillaume] Why not use the tag you just made? ZODB svn://svn.zope.org/repos/main/ZODB/tags/3.6.0/src/ZODB etc. Ask Jim ;-) (Hi have a vague feeling this may have been discussed before but I'm not sure ;)). I'm not sure it's been coherently discussed on a mailing list: - While

Re: [Zope-dev] Re: SVN: Zope/branches/2.9/ Move to ZODB 3.6 final.

2006-01-06 Thread Tim Peters
[Andreas Jung] I _like_ tags in externals because they are self-documenting. Dealing with externals where you have several different revision numbers is a PIA since you never know what version of a module is behind the revision. You always have look through the log for the referenced

[Zope-Checkins] SVN: Zope/branches/2.9/ Move to ZODB 3.6.0b6.

2006-01-01 Thread Tim Peters
Log message for revision 41069: Move to ZODB 3.6.0b6. Changed: _U Zope/branches/2.9/doc/ _U Zope/branches/2.9/lib/python/ _U Zope/branches/2.9/utilities/ -=- Property changes on: Zope/branches/2.9/doc ___ Name:

[Zope-Checkins] SVN: Zope/trunk/ Move to ZODB 3.6.0b6.

2006-01-01 Thread Tim Peters
Log message for revision 41070: Move to ZODB 3.6.0b6. Changed: _U Zope/trunk/doc/ _U Zope/trunk/lib/python/ _U Zope/trunk/utilities/ -=- Property changes on: Zope/trunk/doc ___ Name: svn:externals - ZEO

[Zope-dev] RE: [ZODB-Dev] Re: Connection pool makes no sense

2005-12-29 Thread Tim Peters
[EMAIL PROTECTED] Not agree. Can you answer the question? Does self.all.remove(c) mean that we WANT to destroy connection instance? [Tim Peters] It means that _ConnectionPool no longer has a reason to remember anything about that Connection.  Application code can continue keeping it alive

Re: [Zope-dev] RE: [ZODB-Dev] Re: Connection pool makes no sense

2005-12-29 Thread Tim Peters
Oops! I sent this to zope-dev instead of zodb-dev by mistake. Nevertheless, if you can help Denis Markov, don't let my mistake inhibit you ;-) ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts

Re: [Zope-dev] Re: buildbot failure in Zope branches 2.9 2.4 Windows 2000 zc-bbwin

2005-12-21 Thread Tim Peters
[Florent Guillaume] FYI test output is: ... 'zope[.]app[.])' is not recognized as an internal or external command, operable program or batch file. program finished with exit code 255 That was due to an ill-formed command line, which Jim repaired this morning. Zope trunk and Zope 2.9 branch

Re: [Zope-dev] Re: buildbot failure in Zope branches 2.9 2.4 Windows 2000 zc-bbwin

2005-12-21 Thread Tim Peters
[Tim Peters] ... Failure in test test_checkPermission_proxy_roles_limit_access (AccessControl.tests.testZopeSecurityPolicy.C_ZSPTests) Traceback (most recent call last): File c:\python24\lib\unittest.py, line 260, in run testMethod() File C:\buildbot\.org\zc-bbwin--Windows2000

Re: [Zope-dev] Re: buildbot failure in Zope branches 2.9 2.4 Windows 2000 zc-bbwin

2005-12-21 Thread Tim Peters
[Tim Peters] ... That was the problem. Turns out `bbwin` does have a compiler, but the buildbot recipe didn't use it. After Jim fixed that, we have another Windows-specific failure, in new code from ChrisM (this is on Zope trunk, of course): Failure in test test_get_env

Re: [Zope-dev] Re: Unit Test Failures

2005-12-19 Thread Tim Peters
[Benji York] The Zope2 unit tests have been failing for some time on buildbot.zope.com. Looks like a Five-related problem: http://buildbot.zope.org/Zope%20trunk%202.4%20Linux%20zc-buildbot/builds/109/test/0 [Tres Seaver] The failing test is a functional test, not a unit test; I don't run

Re: [Zope-dev] Re: Unit Test Failures

2005-12-19 Thread Tim Peters
[Tim] I opened a Collector issue on this about a month ago (I always run with `--all`, so these failures are old news to me): http://www.zope.org/Collectors/Zope/1947 [Philipp] Rereading that issue again, it's totally surprising to see that there's no failure on Windows, which makes

Re: [Zope-dev] Re: Unit Test Failures

2005-12-19 Thread Tim Peters
... [Philipp] Well, if you look closer you find that it uses pprint.pformat which always outputs the same on all machines (because it provides output sorted by the dictionary key). [Tres Seaver] I see that in the implementation; it isn't documented as part of pprint's contract, however.

Re: [Zope-dev] Re: Unit Test Failures

2005-12-19 Thread Tim Peters
[Tim] Looks like Jim's suggested from zope.testing.doctestunit import pprint inherits this insecurity. [Jim] No, it doesn't. from zope.testing.doctestunit import pprint pprint({z: 1, m: 2}) {'m': 2, 'z': 1} Note both the sorting and the wrapping. See below. Cool! I

Re: [Zope-dev] Re: Unit Test Failures

2005-12-19 Thread Tim Peters
... [Tim] Well, I understand why that works, but it's not part of pprint's contract either. [Jim] What contract. :) pprint's docs. Aren't you always telling me to read the source? Indeed, if you hadn't, you wouldn't have known that forcing width=1 forces dict sorting ;-) It's common as

Re: [Zope-dev] Re: svn.zope.org borked

2005-12-19 Thread Tim Peters
[Jim] ... The whole repository is only about 800 megs. There are over 8 gigs free. Are the dump file or the file-based repo much larger in size the the Berkeley database? FYI, if you don't want to read the code ;-), the book says an FSFS repository is slightly smaller than the same thing

[Zope-Checkins] SVN: Zope/branches/2.9/ Move to ZODB 3.6.0b5.

2005-12-18 Thread Tim Peters
Log message for revision 40874: Move to ZODB 3.6.0b5. Changed: _U Zope/branches/2.9/doc/ _U Zope/branches/2.9/lib/python/ _U Zope/branches/2.9/utilities/ -=- Property changes on: Zope/branches/2.9/doc ___ Name:

Re: [Zope-dev] zope-2.9 r40780 make install doesn't finish, files missing from bin

2005-12-18 Thread Tim Peters
[Stefan H. Holek] make install does currently not work on 2.9 branch and trunk. I am told that this is because zpkg cannot do it. I am also told that the tarball would support make install, just not the checkout. I never use tarballs, so I don't know for sure. There's no longer any necessary

[Zope-Checkins] SVN: Zope/trunk/lib/python/ New zdaemon.

2005-12-16 Thread Tim Peters
Log message for revision 40813: New zdaemon. This fixes an intermittent test-killing race in testRunIgnoresParentSignals, which was introduced the last time a new zdaemon got stitched in. Changed: _U Zope/trunk/lib/python/ -=- Property changes on: Zope/trunk/lib/python

[Zope-dev] RE: [ZODB-Dev] Test Failures

2005-12-16 Thread Tim Peters
[Sidnei da Silva] I've seen the following tests fail today, after updating Zope 2.8 branch for all variants of BTrees: == ERROR: testUpdateFromPersistentMapping (BTrees.tests.testBTrees.IIBucketTest)

[Zope-dev] RE: [ZODB-Dev] Test Failures

2005-12-16 Thread Tim Peters
[Sidnei] I've seen the following tests fail today, after updating Zope 2.8 branch ... Python 2.4.2 (#2, Nov 20 2005, 17:20:59) ... BTW, I think the Official Story is that Python 2.4+ is still not supported for Zope 2.8. I ran all the stuff in my reply with 2.4.2 too. Doesn't matter, though

[Zope-dev] RE: [ZODB-Dev] Test Failures

2005-12-16 Thread Tim Peters
[Sidnei da Silva] But, why only the 2.8 tests would fail then? Hey, it's your machine, you figure it out ;-) Note that test.py in 2.8 has little in common with the test.py in 2.9 or Zope trunk, and they may very well react in different ways to quirks in your environment. I'll try a 'make

Retiring ZODB 3.2 (was: Re: [Zope-dev] FTP Upload killing Zope)

2005-12-16 Thread Tim Peters
[Andreas Jung, on zope-dev; Tim added zodb-dev to this msg] I would like to consider the 2.7 branch closed for any kind of fixes except security related fixes. I don't plan any further 2.7 releases. In that case (which is fine by me), I'll stop porting fixes to the ZODB 3.2 line too. No

[Zope-Checkins] SVN: zdaemon/trunk/src/zdaemon/tests/testzdrun.py testRunIgnoresParentSignals(): Try to fix an

2005-12-15 Thread Tim Peters
Log message for revision 40791: testRunIgnoresParentSignals(): Try to fix an intermittent test-killing race between this test and zdrun.py fighting over who deletes the test socket first. Changed: U zdaemon/trunk/src/zdaemon/tests/testzdrun.py -=- Modified:

[Zope-Checkins] SVN: Zope/branches/2.9/lib/python/ New zdaemon.

2005-12-15 Thread Tim Peters
Log message for revision 40794: New zdaemon. Should repair the latest intermittent failures in testRunIgnoresParentSignals. Changed: _U Zope/branches/2.9/lib/python/ -=- Property changes on: Zope/branches/2.9/lib/python

RE: [ZODB-Dev] Re: [Zope-dev] Re: sessions in the presence of conflicts

2005-12-15 Thread Tim Peters
[Chris McDonough] Note that changing the transientobject conflict resolution algorithm won't get rid of all write conflict errors, because the BTree-based indexes in the transient object container will still conflict during a bucket split and other situations that I can't exactly recall

Re: [Zope-Checkins] SVN: Zope/branches/2.9/ Collector #1965: 'get_transaction' missing from builtins without sufficient deprecation notice

2005-12-12 Thread Tim Peters
[Tres Seaver] Log message for revision 40728: Collector #1965: 'get_transaction' missing from builtins without sufficient deprecation notice o ZODB 3.6 properly removed it, but Zope needs to keep it for another release because ZODB released *twice* during the Zope 2.9 release cycle.

Re: [Zope-dev] New ways of getting transactions?

2005-12-11 Thread Tim Peters
A number of ZODB gimmicks were officially deprecated in ZODB 3.4, and removed in ZODB 3.6. Zope 2.9 uses the latter. From the ZODB NEWS file for 3.6: Removal of Features Deprecated in ZODB 3.4 -- (3.6b2) ZODB 3.6 no longer contains features officially

Re: [Zope-dev] New ways of getting transactions?

2005-12-11 Thread Tim Peters
[Jim Fulton] ... BTW, This is a good example for why I want to start using time-based deprecation. In a world with time-based releases, is there a difference? ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev

Re: [Zope-dev] Windows Installer for Zope 2.9+

2005-12-09 Thread Tim Peters
... [Sidnei da Silva] Simplifying a lot what the existing Zope 2 installer does, it basically creates a 'software home', a default 'instance home' and registers the services. All but the first part is done manually for Zope 3, so I can see the lack of glow there. There's also that Zope2

Re: [Zope-dev] Logging changes in ZEO break zeoup.py

2005-12-08 Thread Tim Peters
[Jens Vagelpohl] In Zope 2.7 I'm using zeoup.py to check on a ZEO server. This script can be run from anywhere as long as the PYTHONPATH is set correctly. For Zope 2.8.4, the ZEO logging has been switched to use the logging module. This leads to an error when running zeoup.py now:

Re: [Zope] Zope refusing to serve ... i am an idiot

2005-12-08 Thread Tim Peters
[Chris Wilton] Whoops. Sorry. Error log tells me it's a 'no space left on device' error: 2005-12-08T19:33:30 ERROR(200) SiteError http://ekhidna.biocenter.helsinki.fi/dali/downloads/180M.tar/index_html Traceback (most recent call last): File

Re: [Zope-dev] Re: zLOG deprecation?

2005-12-06 Thread Tim Peters
[Tim Peters] Also note that the code Florent pointed at is part of ZODB, not part of Zope. Zope shouldn't use it directly. Growing its own copy would be OK, or refactoring so that ZODB and Zope both get it from a shared new mini-project. [Chris Withers] Sorry, which code are we talking

Re: [Zope-dev] Windows Installer for Zope 2.9+

2005-12-06 Thread Tim Peters
[Sidnei da Silva] Just noticed a checkin talking about the Windows Installer builder. I hope to find some time soon to take a look at that, since we now require Python 2.4 and Python 2.4 uses the 'Microsoft Installer'. I recall talking with Mark about it and he said it would take some time to

Re: [Zope-dev] Windows Installer for Zope 2.9+

2005-12-06 Thread Tim Peters
... [Tim] | Possible headache: Python 2.4.2 requires msvcr71.dll, which is a | Microsoft DLL (it's akin to msvcrt.dll for Visual Studio 6 -- it's the | C runtime for VC 7.1), and one for which the redistribution conditions | are unclear (at least to me). You can't assume that all Windows boxes

Re: [Zope-dev] Re: zLOG deprecation?

2005-12-05 Thread Tim Peters
[Dennis Allison] We probably want an ALL level as well which would map to the NOTSET of the Python logging code and log everything. Why not call it NOTSET? Then you already have it ;-) Or forget it -- TRACE gets everything anyway. Florent, I don't see a TRACE level in this list. Did you

[Zope-Checkins] SVN: Zope/branches/2.9/ Move to ZODB 3.6.0b4.

2005-12-04 Thread Tim Peters
Log message for revision 40533: Move to ZODB 3.6.0b4. Changed: _U Zope/branches/2.9/doc/ _U Zope/branches/2.9/lib/python/ _U Zope/branches/2.9/utilities/ -=- Property changes on: Zope/branches/2.9/doc ___ Name:

Re: [Zope] Re: Zope 2.8.4 strange behavior

2005-11-30 Thread Tim Peters
[Dieter Maurer] ... I think, Tim wanted to implement such a keep alive mechanism inside ClientStorage (to reliably detect disconnects) but in ZODB 3.4 it seems not yet available. Right on all counts: I would like to add that, because it's currently possible for ZEO to run forever without

Re: [Zope] Zope 2.8.4 strange behavior

2005-11-29 Thread Tim Peters
[Chris McDonough] The symptom you're describing has happened to me in the past. Zope stops serving requests and my CPU is not pegged (it's not hitting the CPU hard via an infinept loop I've made). I usually end up tracking it down to the fact that my instance is somehow leaking database

Re: [Zope-dev] How bad _are_ ConflictErrors

2005-11-21 Thread Tim Peters
[Dennis Allison] ... Conflict errors are not always errors. At the ZODB level, an unresolved conflict always raises an exception. Whether such an exception is considered to be an error isn't ZODB's decision -- that's up to the app. My understanding (which may be wrong) is that Zope tries up

  1   2   3   4   5   >