Re: [Zope-CMF] 2.3
On Apr 5, 2012, at 17:08 , Charlie Clark wrote: fuchsia:Products.DCWorkflow charlieclark$ bin/sphinx-build docs tmp Running Sphinx v1.1.3 loading pickled environment... done No builder selected, using default: html building [html]: targets for 0 source files that are out of date updating environment: 0 added, 2 changed, 1 removed Traceback (most recent call last):rkflow File /Users/charlieclark/Sites/CMF/src/Products.DCWorkflow/eggs/Sphinx-1.1.3-py2.6.egg/sphinx/ext/autodoc.py, line 321, in import_object __import__(self.modname) I'm using the CMF-level api-doc to generate the ReST files. - I suspect this may be where I'm going wrong but I couldn't see anything in the conf.py or Makefile that looked liked it would work the proper magic. H Charlie, Before going any further, please stop that usage pattern. The correct way to build those Sphinx docs is: - cd into the docs folder - make sure the sphinx-build script you want to use, which can be either the one inside Products.DCWorkflow or at the toplevel CMF package, is in the path and then run make html: $ cd docs/ $ PATH=../bin:$PATH make html ... I have a feeling with the way you are doing it you put output and Sphinx build state files for different Sphinx buildouts in one and the same place, which will not work. jens ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] 2.3
Hi Jens, Am 05.04.2012, 17:35 Uhr, schrieb Jens Vagelpohl j...@dataflake.org: H Charlie, Before going any further, please stop that usage pattern. The correct way to build those Sphinx docs is: - cd into the docs folder - make sure the sphinx-build script you want to use, which can be either the one inside Products.DCWorkflow or at the toplevel CMF package, is in the path and then run make html: $ cd docs/ $ PATH=../bin:$PATH make html ... Thanks for the clarification and your patience. I have a feeling with the way you are doing it you put output and Sphinx build state files for different Sphinx buildouts in one and the same place, which will not work. It does create the ReST files that make can then run over. I've found the problem: the files I generate have the wrong paths in the automodule directive .. automodule:: DCWorkflow.utils instead of .. automodule:: Products.DCWorkflow.utils Fixed now. Charlie -- Charlie Clark Managing Director Clark Consulting Research German Office Kronenstr. 27a Düsseldorf D- 40217 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] 2.3
On Apr 3, 2012, at 14:55 , Charlie Clark wrote: I had a go at autogenerating the api documentation but failed miserably - lots of empty pages got generated because Sphinx had trouble with import paths. Does anyone know the appropriate incantations for this? I have fixed it by creating a small buildout configuration at the root of the package that will create a working sphinx-build script under bin/ with all the dependencies set up, and by replacing all faulty module references to CMFDefault with Products.CMFDefault. I also cleaned up many Sphinx complaints about bad formatting. jens ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] 2.3
Hi Charlie! Charlie Clark wrote: I suppose we could also migrate the old Zope Help docs to docs for Sphinx generation? I know much of the docs are inaccurate and outdated but this might help expose the worst bits which should then be exorcised or at least pruned. +1 Is CMFDefault/help now obsolete? Could it be deleted? Not sure if this would be for 2.3 but I think that CMFCalendar should be rolled into CMFDefault. The main reason being that the default profile for CMFCalendar uses browser views and explicitly requires the CMFDefault skin layer. You then can't use CMFCalendar if you override the default skin layer. Plus, CMFCalendar's functionality is extremely limited and intimately tied to CMFDefault. -1 CMFCalendar is an example add-on. It should be possible to write add-ons like CMFCalendar. So if there are any issues with keeping it in a separate optional package they should be fixed instead of giving up. Cheers, Yuppie ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] 2.3
Hi Yuppie, Am 03.04.2012, 14:11 Uhr, schrieb yuppie y.2...@wcm-solutions.de: +1 Is CMFDefault/help now obsolete? Could it be deleted? I guess so. I'm still working on tidying up what can loosely be termed as the narrative documentation. Still in the clean-up phase but should get this done this week. @ Jens will we be able to point the release to a docs page on Zope.org? I had a go at autogenerating the api documentation but failed miserably - lots of empty pages got generated because Sphinx had trouble with import paths. Does anyone know the appropriate incantations for this? Not sure if this would be for 2.3 but I think that CMFCalendar should be rolled into CMFDefault. The main reason being that the default profile for CMFCalendar uses browser views and explicitly requires the CMFDefault skin layer. You then can't use CMFCalendar if you override the default skin layer. Plus, CMFCalendar's functionality is extremely limited and intimately tied to CMFDefault. -1 CMFCalendar is an example add-on. It should be possible to write add-ons like CMFCalendar. So if there are any issues with keeping it in a separate optional package they should be fixed instead of giving up. Okay. I guess the key issue is making working with Zope-3 skins easier. I'd like to have a different CMFDefault profile that did without CMF skins (yes, I do appreciate the irony), ie. the ability to jetison PythonScripts et al. CMFCalendar won't work with that because of the explicit dependency upon the CMF skin layer. Certainly a big enough change not to be in 2.3. Charlie -- Charlie Clark Managing Director Clark Consulting Research German Office Kronenstr. 27a Düsseldorf D- 40217 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] 2.3
On Mar 31, 2012, at 17:03 , Charlie Clark wrote: Am 21.03.2012, 22:58 Uhr, schrieb Jens Vagelpohl j...@dataflake.org: The beta eggs are released now. Jens, could we have a patch release to include my fallbacks? I'd like to be able to try the beta with a couple of other sites without adding links to trunk in my buildouts. Products.CMFCore and Products.CMFDefault are now released as version 2.3.0-beta2 jens ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] 2.3
Am 21.03.2012, 22:58 Uhr, schrieb Jens Vagelpohl j...@dataflake.org: The beta eggs are released now. Great, thanks! I'm testing with some existing sites and getting the following error even before I run the upgrades: ComponentLookupError: (InterfaceClass Products.CMFCore.interfaces._tools.IURLTool, '') I'm obviously missing a registration but my site includes Products.CMFCore package. Charlie -- Charlie Clark Managing Director Clark Consulting Research German Office Kronenstr. 27a Düsseldorf D- 40217 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] 2.3
On Mar 22, 2012, at 13:42 , Charlie Clark wrote: PS. I've just run tests on trunk and am getting failures in CMFCore: The tests only fail on Python 2.7, they run through fine on 2.6. As such, they're not functional failures but failures dur to changes in behavior between 2.6 and 2.7. In one place a DeprecationWarning is not written to the log, in another diff output has changed slightly. jens ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] 2.3
Am 22.03.2012, 13:42 Uhr, schrieb Charlie Clark charlie.cl...@clark-consulting.eu: thanks for the quick and informative reply. On both of my test sites I've not been able to look at the site in the ZMI without getting the errors. Even running Site/portal_setup fails. FWIW both sites are using the ursa globals. I can try patching this in the way you suggest and then see how the upgrade works. Fallbacks for ursa.py and DynamicType's getIconURL required but then an upgrade is possible. Charlie -- Charlie Clark Managing Director Clark Consulting Research German Office Kronenstr. 27a Düsseldorf D- 40217 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] 2.3
Am 22.03.2012, 13:46 Uhr, schrieb Jens Vagelpohl j...@dataflake.org: The tests only fail on Python 2.7, they run through fine on 2.6. As such, they're not functional failures but failures dur to changes in behavior between 2.6 and 2.7. In one place a DeprecationWarning is not written to the log, in another diff output has changed slightly. Thanks, Jens. I'd forgotten I'd made Python 2.7 my default. Charlie -- Charlie Clark Managing Director Clark Consulting Research German Office Kronenstr. 27a Düsseldorf D- 40217 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] 2.3
On Mar 21, 2012, at 15:55 , Charlie Clark wrote: Am 21.03.2012, 00:36 Uhr, schrieb Tres Seaver tsea...@palladion.com: Sounds good. We should review the code for any stuff deprecated-and-promised-to-be-remove-in-2.3 before releasing a beta. I suppose we could also migrate the old Zope Help docs to docs for Sphinx generation? I know much of the docs are inaccurate and outdated but this might help expose the worst bits which should then be exorcised or at least pruned. Not sure if this would be for 2.3 but I think that CMFCalendar should be rolled into CMFDefault. The main reason being that the default profile for CMFCalendar uses browser views and explicitly requires the CMFDefault skin layer. You then can't use CMFCalendar if you override the default skin layer. Plus, CMFCalendar's functionality is extremely limited and intimately tied to CMFDefault. If we keep piling up tasks that are too big to be tackled in a small amount of time as part of the release process we'll never get anything released. I would classify both these items as nice to have, but not on the critical path. jens ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] 2.3
Am 21.03.2012, 16:47 Uhr, schrieb Jens Vagelpohl j...@dataflake.org: If we keep piling up tasks that are too big to be tackled in a small amount of time as part of the release process we'll never get anything released. I would classify both these items as nice to have, but not on the critical path. True. I've done a *very* basic port of the docs to ReST so that Sphinx will at least generate stuff. This has been done by copying the exiting STX files and renaming them. Should they be moved instead to preserve the history? Charlie -- Charlie Clark Managing Director Clark Consulting Research German Office Kronenstr. 27a Düsseldorf D- 40217 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] 2.3
On Mar 20, 2012, at 23:25 , Jens Vagelpohl wrote: On Mar 20, 2012, at 16:14 , Charlie Clark wrote: Hi, I finally landed my update step for syndication during the PyCon sprints! I thought I had a few more browser views to update to using the EditSettingsForm but on a quick check of the files it seems that this has already been done. Yuppie, I remember that you have commented out some of my views (portal configuration and membership, I think) because of the encoding problem, did you correct them yourself last year and I was simply looking at old source? If that is the case then I think we're good to go with 2.3. If there are no objections I could run through the packages and create 2.3.0 betas later this week or this coming weekend. The beta eggs are released now. jens ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] 2.3
On Mar 20, 2012, at 16:14 , Charlie Clark wrote: Hi, I finally landed my update step for syndication during the PyCon sprints! I thought I had a few more browser views to update to using the EditSettingsForm but on a quick check of the files it seems that this has already been done. Yuppie, I remember that you have commented out some of my views (portal configuration and membership, I think) because of the encoding problem, did you correct them yourself last year and I was simply looking at old source? If that is the case then I think we're good to go with 2.3. If there are no objections I could run through the packages and create 2.3.0 betas later this week or this coming weekend. jens ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] 2.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/20/2012 06:25 PM, Jens Vagelpohl wrote: On Mar 20, 2012, at 16:14 , Charlie Clark wrote: I finally landed my update step for syndication during the PyCon sprints! I thought I had a few more browser views to update to using the EditSettingsForm but on a quick check of the files it seems that this has already been done. Yuppie, I remember that you have commented out some of my views (portal configuration and membership, I think) because of the encoding problem, did you correct them yourself last year and I was simply looking at old source? If that is the case then I think we're good to go with 2.3. If there are no objections I could run through the packages and create 2.3.0 betas later this week or this coming weekend. Sounds good. We should review the code for any stuff deprecated-and-promised-to-be-remove-in-2.3 before releasing a beta. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9pFIQACgkQ+gerLs4ltQ5/qgCgjqblk/uMP2vW1hYksFNvCFXC 8ocAn0ZQzSfmr1EgI5AbNtl6h1KyoU6R =XfEn -END PGP SIGNATURE- ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
