- Zope-Dev - Zope lists

Refresh and dumping the cache
by Dylan Jay 13 May '05

13 May '05

When performing a refresh I've read that the cache gets dumped. I've noticed after a refresh the reference counts to objects don't go down. Basically the entire cache seems to be leaked. Is this by design or is it a bug? -- Dylan Jay --- http://www.meetmemap.com - makes giving directions easy http://www.pretaweb.com - Update-it-yourself, low cost websites http://www.eatmanifesto.com - against all dumbing down of food Y!:dylan_jay ICQ:520341 MSN:djsq@hotmail.com Ph:+61423198306

4 6

DateTime, strftime and TimeError
by Santi Camps 13 May '05

13 May '05

Hi all, I think its known that using strftime method of DateTime module with dates <= 1900 or >= 2038, a TimeError is raised. For instance: >> d = DateTime('2045/30/01') >> d.strftime('%d/%m/%Y') DateTime.DateTime.TimeError: The time 2369343600.000000 is beyond the range of this Python implementation I've read that the reason was a validation to avoid int overflows. I think this could be fixed using datetime module (new in python 2.3) instead of old time.localtime Do you think its a good idea ? Can I provide a patch that way ? Thanks Santi Camps

5 9

copyzopeskel.py patch
by Dale Hirt 12 May '05

12 May '05

Hi all, Wonderful product, more than appreciate all the hard work that has been put into Zope and all the various products that are out there. Came across a small issue, and wrote a quick patch for it. Didn't know who to send it to, so I thought I'd send it here. When creating a new zope instance, using mkzopeinstance.py, and having my files under Subversion, copyzopeskel.py also took across my .svn directories. So I created the small patch below to stop that. Makes it a little more flexible for adding in new types, and since you've switched to Subversion anyways, makes sense to add it in there. Again, thanks for your time, Dale Hirt Index: copyzopeskel.py =================================================================== --- copyzopeskel.py (revision 30342) +++ copyzopeskel.py (working copy) @@ -186,12 +186,12 @@ print >>sys.stderr, msg sys.exit(1) -CVS = os.path.normcase("CVS") +CVS_DIRS = [os.path.normcase("CVS"), os.path.normcase(".svn")] def copydir((targetdir, replacements, uid, gid), sourcedir, names): # Don't recurse into CVS directories: for name in names[:]: - if os.path.normcase(name) == CVS: + if os.path.normcase(name) in CVS_DIRS: names.remove(name) elif os.path.isfile(os.path.join(sourcedir, name)): # Copy the file:

2 1

SMTP socket error
by Shilpa P 11 May '05

11 May '05

Hello I am trying to send mail using python.I tried the command >>> import smtplib >>> s=smtplib.SMTP("localhost") I get the following error socket.error: (10053, 'Software caused connection abort') could someone please help.. Thanks Shilpa _______________________________________________________________________ > Yahoo! India Matrimony: Find your life partner > online > Go to: http://yahoo.shaadi.com/india-matrimony > ________________________________________________________________________ Yahoo! India Matrimony: Find your life partner online Go to: http://yahoo.shaadi.com/india-matrimony

2 1

Online test tool
by Zope User 10 May '05

10 May '05

Is there a zope product that will allow me to create an online test tool? Thanks! RT

2 1

Re: ZConfig change breaks Zope 2 and Zope 3
by yuppie 09 May '05

09 May '05

Derrick Hudson wrote: > On Sun, May 08, 2005 at 02:28:55PM +0200, yuppie wrote: > | Hi! > | > | On Windows, this 15 months old change in ZConfig sets the default > | hostname for inet_address to 'localhost': > | > | http://svn.zope.org/ZConfig/?rev=376&view=rev > | > | I have no idea why this was changed, the checkin message is not very > | helpful: "fix the default hostname for address datatypes for Windows" > > | Any comments? > > Search the list archives for a discussion of why that was changed. > IIRC it is due to quirks in Windows' network libraries -- a test was > failing because the system API to query the identity of the socket > did something funny with 'localhost' vs. '127.0.0.1' and that caused > the comparison in the test to fail even though there was no actual > defect. > > OTOH, after a quick look at the referenced defects and archived emails > I may be remembering something else. > > Anyways, hopefully my memory will help you. If not, well that's all I > can offer. I couldn't find anything in the archives, but Tim's Entry #5 in http://www.zope.org/Collectors/Zope/1728 might explain the change in ZConfig. It seems to work around an issue with connect() on Windows. But I still believe it was wrong to change the 'inet_address' datatype in ZConfig. Cheers, Yuppie

2 1

Zope 2.8 on hold
by Andreas Jung 09 May '05

09 May '05

Hi, in agreement with Jim Fulton and Brian Lloyd we decided to put the Zope 2.8 release on hold for now. There are several open issues related to running Zope on Windows (building, startup problems). Since we need to have a stable source code release and a stable windows release in sync, the next beta 2 will appear as soon as the major issues are fixed. This is maybe a good point for advanced Windows programmer to help out *wink* Andreas

3 4

relocating Zope 2 core interfaces - a proposal
by yuppie 09 May '05

09 May '05

Hi again! As discussed two days ago, I started working on integrating Five interfaces closer into Zope 2.8. I believe I understand the problem better now and like to propose a different way to resolve it: Current State ============= Five (now part of Zope 2.8) ships with one big interfaces.py file that contains z3 interfaces for Zope 2 core classes. (There are also some five specific interfaces in that file, but they are not subject of this proposal.) interfaces.zcml states that Zope 2 implements these interfaces, but there are no tests to verify that and in fact many of these interfaces are broken in Five 1.0. (Yesterday I checked in some fixes to the Five trunk.) So if they are used at all in Five products, they are only used as marker interfaces, not to verify implementations. I grepped through CMFonFive, SilvaDocBook and SilvaFlexibleXML: None of them use these interfaces. Goals ===== Step by step, Zope 2 should move to z3 interfaces. Where z2 interfaces exist, these should be improved and bridged to z3 interfaces. Missing interfaces should be added as z3 interfaces. Instead of maintaining competing interfaces, Five should support that process. Interface locations are identifiers, so first of all I want to get these locations right before Zope 2.8 is released. Z3 interfaces should be located in an 'interfaces' module of the corresponding package. In the Five package they are unmaintainable. So e.g. instead of Products.Five.interfaces.IObjectManager Products.Five.interfaces.IWriteLock we would have OFS.interfaces.IObjectManager webdav.interfaces.IWriteLock Proposed Solution ================= 1.) Adding ZCML that bridges existing z2 interfaces into the 'interfaces' module of their package. [Zope 2.8.0] 2.) Copying z3 interfaces from Five.interfaces to the 'interfaces' module of the corresponding package. Marking those in Five as Zope 2.7 backwards compatibility cruft. [Zope 2.8.0] 3.) Doing the same for Zope 2.7 with monkey patching code. [Five 1.0+] 4.) Making interfaces.zcml point to the new locations. [Five 1.0+] 5.) Adding unit tests that verify interfaces and implementations. [Zope 2.8.0] Risks ===== I can't see a way to provide backwards compatibility for Products.Five.interfaces.*, but as explained above I'm hopeful this doesn't break many Five products. Any comments? Cheers, Yuppie

5 22

Re: [Zope-dev] Re: Zope 2.8 on hold
by Tim Peters 09 May '05

09 May '05

[Andreas Jung] > At least the following are important (besides the problem with the > Winbuilder) What WinBuilders problem? I keep hearing there's "a problem" there, but don't know what it is -- and I had no problem using WinBuilders for Zope 2.8. Note that these two aren't about Zope 2.8, they're about Zope 2.7.6: > http://www.zope.org/Collectors/Zope/1763 > http://www.zope.org/Collectors/Zope/1711 Both appear to be due to that Zope 2.7.6 on Windows shipped with a wrong (too old) version of pywin32, and continued to repackage pywin32 in the old (certifiably insane <0.7 wink>) "flat" way. Mark Hammond submitted patches to install a correct version of pywin32, and in a correct way. Those patches were incorporated into WinBuilders, so it's hard to understand how Zope 2.7.6 on Windows got built the way it did. Can only guess the installer was built using an out-of-date WinBuilders checkout, with an out-of-date pywin32, applied to an up-to-date Zope checkout.

3 2

Re: [Zope-dev] Re: Zope 2.8 on hold
by Tim Peters 08 May '05

08 May '05

[Andreas Jung] >>> At least the following are important (besides the problem with the >>> Winbuilder) [Tim Peters] >> What WinBuilders problem? I keep hearing there's "a problem" there, >> but don't know what it is -- and I had no problem using WinBuilders >> for Zope 2.8. [Andreas] > I know only that Christian had problems (according to his posting some > days ago). I can not comment and can not value these issues. But there > seems to be something. If you're talking about his posts to this list, those were all addressed some time ago, and all the problems in Zope 2.8's setup.py he was hitting have been repaired. If Christian still has problems, I haven't seen anything about them (neither on this list nor anywhere else). >> Note that these two aren't about Zope 2.8, they're about Zope 2.7.6: >> >> > http://www.zope.org/Collectors/Zope/1763 >> > http://www.zope.org/Collectors/Zope/1711 >> >> Both appear to be due to that Zope 2.7.6 on Windows shipped with a >> wrong (too old) version of pywin32, and continued to repackage pywin32 >> in the old (certifiably insane <0.7 wink>) "flat" way. >> >> Mark Hammond submitted patches to install a correct version of >> pywin32, and in a correct way. Those patches were incorporated into >> WinBuilders, so it's hard to understand how Zope 2.7.6 on Windows got >> built the way it did. Can only guess the installer was built using an >> out-of-date WinBuilders checkout, with an out-of-date pywin32, applied >> to an up-to-date Zope checkout. > Christian should know...as I said...I have no idea about how this > windows stuff works and what it does...so I depend on the competence of > you windows guys :-) It would help if Christian said something <wink>. I'm not sure the point of the above got across: the subject of this thread is "Zope 2.8 on hold", but the two issues identified above are not Zope 2.8 issues. They're Zope 2.7.6 issues. Zope 2.8 shouldn't have any problem with those. Zope-2.7.6-final-win32.exe from zope.org has those problems; they're not holding up 2.8.

3 3