[Zope-dev] Re: [Proposal] RFC2396 compatible traversal parameters
Florent Guillaume wrote at 2005-10-24 16:19 +0200: I really really wouldn't want to see added on top of the current Zope2 publisher. The Zope 2 publisher (and the various traversal mechanisms -- publisher, restrictedTraverse, TALES) should first be refactored to use Zope 3 mechanisms, and only after that is done should we consider adding the kind of feature you propose. The problem (as always with my proposals): I need this within weeks (not months or years). But, as we maintain our own Zope version, this may not be a problem... -- Dieter ___ 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] RFC: product initialization cleanup and improvements
yuppie wrote at 2005-10-27 14:45 +0200: ... 1.) 'action' key: - I'd like to give empty 'action' values a special meaning: The meta_type is not visible in the add drop down in the ZMI. The five:registerClass directive allows to set empty 'action' values. This would resolve http://www.zope.org/Collectors/Zope/1885 . Filtering out meta_types with empty 'action' values is a two line change in main.dtml. I'd like to make that change also on the 2.8 branch to enable that feature for 2.8.5 with Five 1.2. We already have the visibility key. Why do we need another (much obscurer) way to achieve the same thing? ... 4.) related cleanup: Application.install_product has some backwards compatibility code for products that have initialization code outside the 'initialize' method of their __init__.py. This is deprecated at least for 5 years. I'd like to add explicit deprecation warnings on the 2.8 branch and to remove that code for Zope 2.9. I hate that: While you might have the feeling that it were deprecated, 'ZSQLMethods' still use part of the old style initialization (they have an initialize but still use methods, __ac_permissions__ and __module_aliases__). And I occationally recommend these old style facilities. Having a warning period of 5 days (post on Oct 27; code freeze Nov 1) seems very short. What about removing the code for Zope 2.10? -- Dieter ___ 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] RFC: product initialization cleanup and improvements
Hi Dieter! Dieter Maurer wrote: yuppie wrote at 2005-10-27 14:45 +0200: ... 1.) 'action' key: - I'd like to give empty 'action' values a special meaning: The meta_type is not visible in the add drop down in the ZMI. The five:registerClass directive allows to set empty 'action' values. This would resolve http://www.zope.org/Collectors/Zope/1885 . Filtering out meta_types with empty 'action' values is a two line change in main.dtml. I'd like to make that change also on the 2.8 branch to enable that feature for 2.8.5 with Five 1.2. We already have the visibility key. Why do we need another (much obscurer) way to achieve the same thing? Because it doesn't do the same thing. 'visibility' doesn't primarily change the visibility. It controls if the meta_type is globally available (visibility='Global') or only in containers that specify one of its interfaces (visibility=None). ... 4.) related cleanup: Application.install_product has some backwards compatibility code for products that have initialization code outside the 'initialize' method of their __init__.py. This is deprecated at least for 5 years. I'd like to add explicit deprecation warnings on the 2.8 branch and to remove that code for Zope 2.9. I hate that: While you might have the feeling that it were deprecated, 'ZSQLMethods' still use part of the old style initialization (they have an initialize but still use methods, __ac_permissions__ and __module_aliases__). Well. I think the comments in Application.install_product are very clear. 'initialize' was meant to replace the old way, not to provide a second way. I fixed ZGadflyDA and ZSQLMethods. And I occationally recommend these old style facilities. Having a warning period of 5 days (post on Oct 27; code freeze Nov 1) seems very short. What about removing the code for Zope 2.10? If the change breaks too many existing products I'm fine with leaving the code including deprecation warnings in Zope 2.9. Cheers, Yuppie ___ 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] RFC: product initialization cleanup and improvements
Dieter Maurer wrote: yuppie wrote at 2005-10-27 14:45 +0200: 4.) related cleanup: Application.install_product has some backwards compatibility code for products that have initialization code outside the 'initialize' method of their __init__.py. This is deprecated at least for 5 years. I'd like to add explicit deprecation warnings on the 2.8 branch and to remove that code for Zope 2.9. I hate that: While you might have the feeling that it were deprecated, 'ZSQLMethods' still use part of the old style initialization (they have an initialize but still use methods, __ac_permissions__ and __module_aliases__). __module_aliases__ are not affected by that change. They are not initialized by Application.install_product. Cheers, Yuppie ___ 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[2]: differences in PropertyManager._setPropValue
Hello Florent Guillaume, Monday, October 31, 2005, 6:25:20 PM, you wrote: FG This was changed because have mutable objects stored as properties can lead FG to unexpected behavior. Do you mean you have a custom proprty type called FG list? yes, my own property of type 'list'. I don`t find any restriction on type of the property, only in comment of the PropertyManager class: The 'type' string must be one of the values: 'float', 'int', 'long', 'string', 'lines', 'text', 'date', 'tokens', 'selection', or 'multiple section'. But PropertyManager support any custom types not only types descriped above. For example Publisher supports ':list' and ':tuple' converters (but only in HTTPRequest.processInputs method, it is impossible to manage 'list', 'tuple', 'records' types through converters.py module, pitifully ) FG What's your use case for it, and why can't tuple fit the bill ? My code use the 'sort' method of the python list type. Of course this is ugly to trust the getProperty result, and my code should be manually convert the getProperty result to list. of course i repaire my code, but how chould i escape from incompatible behavior of the zope versions in future? may be write more tests to PropertyManager class? or how? -- Best regards, Victor Safronovich NauMen.NauDoc.SoftwareDeveloper http://www.naumen.ru ___ 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] Default excluded tests?
I have configured the test runner to exclude tests for ZConfig, BTrees, persistent, ThreadedAsync, transaction, ZEO, ZODB, ZopeUndo, zdaemon, and zope.testing. My reasoning for excluding these by default was that these packages are all included via externals. They aren't being modified as part of the Zope 2 development process, so why run their tests? I then realized that this applies to all of the zope package. Perhaps I should exclude the zope package as well. Or perhaps we shouldn't exclude anything by default. Thoughts? Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ 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] moment when zope was started.
Hello zope-dev! How could i find the moment when zope was started in Zope 2.8? in Zope 2.7 was the variable 'Zope.Startup.started', which setted to True when zope was started. But in Zope 2.8 the variable 'Zope2.Startup.started' not changed its value to True, because Zope2.Startup.start_zope was never called, instead of that called Zope2.Startup.run.run function. -- Best regards, Victor Safronovich NauMen.NauDoc.SoftwareDeveloper http://www.naumen.ru ___ 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] Maintenance cycles for Zope 2.X branches
On 10/31/05, Andreas Jung [EMAIL PROTECTED] wrote: What do you think? Sounds great. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ 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] buildbot failure in Zope trunk 2.4 Linux zc-buildbot
The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 1295 Blamelist: chrism,efge,fdrake,jim,philikon,srichter BUILD FAILED: failed compile sincerely, -The Buildbot ___ 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] PAS tests failures
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I got tests failing with the following configuration : FC4 Zope-2.8.4 Python 2.3.5 / 2.4.2 PAS trunk as below : == FAIL: Doctest: ChallengeProtocolChooser.txt - -- Traceback (most recent call last): File /opt/Zope-2.8.4/lib/python/zope/testing/doctest.py, line 2102, in runTest raise self.failureException(self.format_failure(new.getvalue())) AssertionError: Failed doctest test for ChallengeProtocolChooser.txt File /home/zopes/zope2.8.4/Products/PluggableAuthService/plugins/tests/ChallengeProtocolChooser.txt, line 0 and all the failures within this doctest look like this one : - -- File /home/zopes/zope2.8.4/Products/PluggableAuthService/plugins/tests/ChallengeProtocolChooser.txt, line 260, in ChallengeProtocolChooser.txt Failed example: print http(r POST /%s HTTP/1.1 Content-Type: text/xml; charset=utf-8 ?xml version=1.0? methodCall methodNametest_script/methodName /methodCall % (folder_name), handle_errors=False) Exception raised: Traceback (most recent call last): File /opt/Zope-2.8.4/lib/python/zope/testing/doctest.py, line 1315, in __run compileflags, 1) in test.globs File doctest ChallengeProtocolChooser.txt[62], line 1, in ? print http(r File /opt/Zope-2.8.4/lib/python/Testing/ZopeTestCase/zopedoctest/functional.py, line 180, in http debug=not handle_errors, File /opt/Zope-2.8.4/lib/python/ZPublisher/Test.py, line 193, in publish_module response = publish(request, module_name, after_list, debug=debug) File /opt/Zope-2.8.4/lib/python/ZPublisher/Publish.py, line 144, in publish sys.exc_info()[2], File /opt/Zope-2.8.4/lib/python/ZPublisher/Publish.py, line 104, in publish object=request.traverse(path, validated_hook=validated_hook) File /opt/Zope-2.8.4/lib/python/ZPublisher/BaseRequest.py, line 461, in traverse response.unauthorized() File /opt/Zope-2.8.4/lib/python/ZPublisher/HTTPResponse.py, line 684, in unauthorized raise Unauthorized, m Unauthorized: strongYou are not authorized to access this resource./strong With Zope-2.7.8 the tests pass just fine. Any idea about the problem ? J. - -- Julien Anguenot | Nuxeo RD (Paris, France) CPS Platform : http://www.cps-project.org Zope3 / ECM : http://www.z3lab.org mail: anguenot at nuxeo.com; tel: +33 (0) 6 72 57 57 66 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFDaXQHGhoG8MxZ/pIRAkYLAJ4upanns7PRDyYHNgSxHXkJk476IACdFfMy U6mOq7W8VdrXr0EEcCENIoU= =JMU+ -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 )
[Zope-dev] ZSQL method and LIMIT clause
Hello, My problem is I don't know to prevent Zope from adding LIMIT 1000 to the end of each of my ZSQL method (*.zsql). I am developing a filesystem-based product so I can not disable itby settingMaximum Rows to Retrieve to zero in the ZMI interface. I got stuck with this problem for acouple of weeks (google search and read documentation didn't help). Any help is greatly appreciated. ___ 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] ZSQL method and LIMIT clause
Am Donnerstag, den 03.11.2005, 09:37 +0700 schrieb Thanh Hải, Hà: Hello, My problem is I don't know to prevent Zope from adding LIMIT 1000 to the end of each of my ZSQL method (*.zsql). I am developing a filesystem-based product so I can not disable it by setting Maximum Rows to Retrieve to zero in the ZMI interface. I got stuck with this problem for a couple of weeks (google search and read documentation didn't help). Any help is greatly appreciated. Go to the advanced tab of your ZSQL method and set the max rows there to 0. IIRC, just adding the LIMIT clause to the query is database adaptor specific. (Others may fetch only max rows from dataset) ___ 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] buildbot failure in Zope trunk 2.4 Linux zc-buildbot
The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 1305 Blamelist: yuppie BUILD FAILED: failed compile sincerely, -The Buildbot ___ 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] ZSQL method and LIMIT clause
*Everything* you can do in the ZMI can be done from code. The ZMI is not a magic entity, it uses the same APIs as everybody else. With FSZSQLMethods you can stick max_rows: 0 into the lead-in comment, BTW. Stefan On 3. Nov 2005, at 03:37, Thanh Hải, Hà wrote: My problem is I don't know to prevent Zope from adding LIMIT 1000 to the end of each of my ZSQL method (*.zsql). I am developing a filesystem-based product so I can not disable it by setting Maximum Rows to Retrieve to zero in the ZMI interface. -- Anything that happens, happens. --Douglas Adams ___ 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 )
