Re: [Zope3-dev] faulty releases and pypi access [update]
WinZip has the habit of ignoring files it deems empty and paths it deems too long. Best to avoid. Stefan On 26. Sep 2007, at 10:49, Christian Theune wrote: The issue is that the eggs were released as ZIP files and for some reason those don't work correctly with the data files. -- It doesn't necessarily do it in chronological order, though. --Douglas Adams ___ 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: z3c.widget not on pypi?
I fully agree that such eggs should not have been released into the wild. It is just that, down here in real-life, these eggs *have* been released, and their versions *have* been nailed (not nailing the versions of *all* eggs means saying goodbye to the idea of reproducible buildouts). By deleting a released egg (as opposed to superseding it with a good version) one potentially creates a lot of pain for a lot of people. Stefan On 19. Sep 2007, at 16:21, Tres Seaver wrote: - -1. Another implication: eggs which have '-r[0-9]+' in them should *never* be released to any location where they might be found by anyone not explicitly requesting them. Specifically, this means the cheeseshop as well as any public 'find-links' or 'index-url' location. Nobody should ever nail a dependency to such an egg without taking responsibility for hosting it themselves. Frankly, anybody who *wants* such an egg should instead be using a checkput + 'setup.py develop', instead; anything else is an invitation to disaster. -- Anything that happens, happens. --Douglas Adams ___ 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: z3c.widget not on pypi?
On 19. Sep 2007, at 00:46, Jodok Batlogg wrote: i'm wondering why i couldn't fine zope.app.wsgi = 3.4.0b1dev_r75415 after 3.4.0 was released a few days ago. probably someone in [philikon, ctheune, J1m, baijum] removed the egg? we nailed the version to 3.4.0b1dev_r75415 (and i have still this egg in my cache), but it disappeared from the rest of the world. this should never happen for released eggs, they should be considered read-only imho. +1 Eggs must not disappear, ever. Now that we have decided on eggs we have to live with the implications. This is one of them. Stefan -- Anything that happens, happens. --Douglas Adams ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] doctest prb again
Doesn't NORMALIZE_WHITESPACE help here? Stefan On 20. Jul 2007, at 10:09, Adam Groszer wrote: How to solve the \r\n and \n mismatch between win32 and *nix in the doctests? -- Anything that happens, happens. --Douglas Adams ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] two small bugs in zc.relationship
As a general rule you should avoid taking the boolean value of objects. You never know what the result will be and how expensive the underlying operations are (e.g. computing the length of a BTree can be *very* expensive). Stefan On 2. Jul 2007, at 14:24, Markus Kemmerling wrote: But I wouldn't have expected a non built-in type, that *also* supports the mapping API, to be considered as `False` as long as the mapping is empty ... -- Anything that happens, happens. --Douglas Adams ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] layers can't be new style classes?
IIRC you need @classmethod def setUp(cls): pass @classmethod def tearDown(cls): pass On 17. Okt 2006, at 12:30, Chris Withers wrote: It would appear that Philipp's article is somewhat misleading in that layers can't be new style classes... class MyLayer(object): def setUp(self): pass def tearDown(self): pass ..results in the following when used as a layer: AttributeError: type object 'object' has no attribute 'setUp' Is this a bug in Philipp's article or in the testrunner? -- Anything that, in happening, causes something else to happen, causes something else to happen. --Douglas Adams ___ 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] Should PageTemplate._text be a unicode or an encoded string in Zope 2.9.3?
zope.pagetemplate.pagetemplatefile.PageTemplateFile reads an eventual meta http-equiv=Content-Type ... header, or defaults to UTF-8. Stefan On 21. Jul 2006, at 16:53, Chris Withers wrote: I wonder how Zope 3's filesystem-based ZPT's deal with this? -- Anything that, in happening, causes something else to happen, causes something else to happen. --Douglas Adams ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Visionaire! (All your problems, solved)
I like this a whole lot. This is *much* better than diluting the Zope brand (Zed is dead, baby). If people really say things like Oh, I can't use zope.testbrowser because I'm not using Zope it's time to school them, not to ruin our brand: You only need the Zope CA for that, dude, so stop whining. Zope already worked when people like the RoR creators attended primary school. The term Zope having a bad rap in some circles is not Zope's fault, and can not be fixed by calling it Zed (to the contrary, I'd think). IMO, Stefan On 2. Mär 2006, at 01:42, Jeff Shell wrote: - Zope 3 CA: The Zope Component Architecture. Core services. Would include zope.publisher and most other current top level zope.* things. Usable as a library, as a publisher for other environments, perhaps as a simple standalone server. Easy to deploy against WSGI, Paste.deploy, whatever. - Zope 3 AS: The Zope 3 Application Server. A Zope 3 CA stack using the ZODB, ILocation, and most of the zope.app services but without any content objects. Perhaps only an application server configuration skin (process management) but no ZMI. Maybe have the current configuration installable as an option. - Zope Suite (or Zope Web or Zope DE): This is the full application server perhaps Jim is envisioning. A comprehensive web based user interface, based on features (and implementations) of both Zope 2 and Zope 3 application servers and offerings. -- Anything that happens, happens. --Douglas Adams ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] simpleTraverse raises NameError?
Thanks for the reply Stephan, So there are basically 2 options a) Add NameError to Undefs b) Make simpleTraverse raise AttributeError instead I am all for b) because an AttributeError it is, IMO Stefan On Sat, 12 Nov 2005, Stephan Richter wrote: On Sunday 23 October 2005 03:12, Stefan H. Holek wrote: So, is there or would this qualify as a bug? There is a test that seems to point to some use with regard to namespaces, but I don't see how this wouldn't work just as well with AttributeError. I definitely think this is a bug. I guess the | operator should simply also know how to deal with NameError. Stefan, it would be great if you could fix this or at least file a bug report. Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
