Re: [Zope-dev] Zope Tests: 10 OK, 4 Failed, 2 Unknown
On Tue, May 4, 2010 at 00:41, Christophe Combelles cc...@free.fr wrote: Unless I missed something, the ZTK was globally compatible with Python2.4 recently, wasn't it? Do we want the latest changes and Lennart's work to be part of the ZTK 1.0? I think it's OK if they are not. Of course it would be cool if 1.0 does include the latest and greatest, but my changes are mostly aimed at Python 3 compatibility, and ZTK 1.0 will not have that as a whole anyway. -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 10 OK, 4 Failed, 2 Unknown
On Mon, May 3, 2010 at 20:02, Tres Seaver tsea...@palladion.com wrote:
- - zope.browserpage
- - zope.viewlet
- - zope.contentprovider
- - zope.deferredimport
These tests all fail because as Tres pointed out, Python 2.4 doesn't
set __file__ to the doctest filename in the globals. Zope.browserpage
in turn uses those globals to determine the filename of the
pagetemplate. So, you get an error if you create a browserpage in a
DocTestFile, like so:
ErrorPage = SimpleViewClass(errorFileName, name='error.html')
Passing in file explicitly solves the problem:
ErrorPage = SimpleViewClass(errorFileName, name='error.html',
offering={'__file__': 'README.txt'})
The same thing goes for ViewPagetemplateFile, but there it's called
_prefix instead of offering. Yeah, none of those variable names make
sense.
It can also typically be fixed by passing in __file__ explicitly to the doctest:
def test_suite():
import doctest
filename = os.path.join(os.pardir, 'namedtemplate.txt')
return doctest.DocFileSuite(
filename,
setUp=pageSetUp, tearDown=zope.component.testing.tearDown,
globs={'__file__':
os.path.abspath(os.path.join(os.path.dirname(__file__), filename))}
)
Other options is to make the usage of __file__ lazy, so that it's only
looked up in the globals when accessed. Because I suspect it's not
actually used except when you get errors, but I'm not 100% sure.
So for the time being, I went for passing in __file__ explicitly in
globs. The tests run under Python 2.4 again.
--
Lennart Regebro: Python, Zope, Plone, Grok
http://regebro.wordpress.com/
+33 661 58 14 64
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 10 OK, 4 Failed, 2 Unknown
Hanno Schlichting wrote: Dropping Python 2.4 supports makes most sense to me at this stage. Zope2/Plone only support Python 2.6 for any modern version. I don't know what BlueBream and Grok want to support, but would guess they aim for Python 2.5 + 2.6 support. 2.4 is really old by now. Grok 1.1 aims for 2.5 and 2.6. Grok 1.0 goes for 2.4 and 2.5, but Grok 1.0's stable so we don't have problems when the ZTK is updated. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 10 OK, 4 Failed, 2 Unknown
On Tue, May 4, 2010 at 12:07, Martijn Faassen faas...@startifact.com wrote: For a while already people have been making changes that at least break tests on 2.4. For instance, zope.testing has some facility to pretty print a dictionary that sorts the keys, because Python 2.4's built-in pretty print module apparently doesn't do that yet, meaning random test failures can happen. But people have been updating code to use Python's built-in pretty print facility and this will only be reliable on Python 2.5 and higher. Although that zope.testing facility has been deprecated, as far as I'm aware it's still there... If not maybe it should be reintroduced, we're suppose dto deprecate, not break in this case. In my opinion it's time to drop Python 2.4 support anyway, but it's been going a bit haphazardly by way of bit rot.. Yeah, officially dropping is better than bitrot dropping it, that's for sure. And as mentioned, except for the Bicycle toolkit or whatever the name is, 2.4 is not needed any more. -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SVN: Zope/trunk/versions.cfg Group versions by the 'sets' to which they correspond.
On Tue, May 4, 2010 at 4:25 AM, Tres Seaver tsea...@palladion.com wrote: Should the triumvirs so decide, attached is the patch for zopetoolkit which adopts the versions from Zope2. The normal buildout (using eggs rather than checkouts) passes all test-ztk and test-zopeapp tests with this patch applied. As far as I understand the current process, you can just go ahead and update the ztk.cfg file, as long as all tests pass. Please do that. I will change the Zope 2 versions file once we started clarifying a few things on the release team. Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 11 OK, 5 Failed
Summary of messages to the zope-tests list. Period Mon May 3 12:00:00 2010 UTC to Tue May 4 12:00:00 2010 UTC. There were 16 messages: 6 from Zope Tests, 9 from ccomb at free.fr, 1 from ct at gocept.com. Test failures - Subject: FAILED: Repository policy check found errors in 670 projects From: ct at gocept.com Date: Mon May 3 21:19:27 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014248.html Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 32bit From: ccomb at free.fr Date: Tue May 4 00:07:36 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014259.html Subject: FAILED : ZTK 1.0dev / Python2.5.2 Linux 32bit From: ccomb at free.fr Date: Tue May 4 00:08:31 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014260.html Subject: FAILED : Zope 3.4.1 KGS / Python2.4.6 32bit linux From: ccomb at free.fr Date: Tue May 4 00:30:16 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014262.html Subject: FAILED : Zope 3.4.1 KGS / Python2.5.2 32bit linux From: ccomb at free.fr Date: Tue May 4 00:54:09 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014263.html Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Mon May 3 21:29:11 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014249.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon May 3 21:31:11 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014250.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Mon May 3 21:33:11 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014251.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Mon May 3 21:35:11 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014252.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Mon May 3 21:37:11 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014253.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Mon May 3 21:39:11 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014254.html Subject: OK : BlueBream template / Python2.4.6 32bit linux From: ccomb at free.fr Date: Mon May 3 22:01:04 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014255.html Subject: OK : BlueBream template / Python2.6.4 32bit linux From: ccomb at free.fr Date: Mon May 3 22:01:06 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014256.html Subject: OK : BlueBream template / Python2.7b1 32bit linux From: ccomb at free.fr Date: Mon May 3 22:01:08 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014258.html Subject: OK : BlueBream template / Python2.5.2 32bit linux From: ccomb at free.fr Date: Mon May 3 22:01:09 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014257.html Subject: OK : ZTK 1.0dev / Python2.6.4 Linux 32bit From: ccomb at free.fr Date: Tue May 4 00:09:10 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014261.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] IRC Meeting Today at 15:00 UTC
Hi, can't see Theuni anywhere so I thought I'd do the honours - the meeting will be on #zope in just over two-and-a-half hours. Not sure about the Agenda but I think there is some KGS to be carried over from last week and possibly some of the very recent ZTK discussions need formalising so the following is just a suggestion, Agenda -- - KGS status - Windows builds - ZTK status - Python 3 status - Deprecating Python 2.5 Ongoing issues -- Those issues are currently ongoing. We don't have to discuss them. We just need to follow up on them eventually. - Bug tracking - Monitoring tracker status (Charlie Clark, ctheune) - Towards a ZTK release - Establishing ZTK release engineering team (Z2, grok, BB) - Documentation - Release scope - Test runners / nightly builds - Windows machines - Meta - How to organize open issues in the long run (Blueprints? Other tool? Continue text files?) - Find second person to run the weekly meetings Horizon --- These items are currently tracked on the horizon. We won't discuss them at this meeting, but we'll get to them at some point: - Pondering *some* (re-)structuring of the ZTK to allow for better maintenance/release management/communication/marketing. (Chris McDonough) -- Charlie Clark Managing Director Clark Consulting Research German Office Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 10 OK, 4 Failed, 2 Unknown
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lennart Regebro wrote:
On Mon, May 3, 2010 at 20:02, Tres Seaver tsea...@palladion.com wrote:
- - zope.browserpage
- - zope.viewlet
- - zope.contentprovider
- - zope.deferredimport
These tests all fail because as Tres pointed out, Python 2.4 doesn't
set __file__ to the doctest filename in the globals. Zope.browserpage
in turn uses those globals to determine the filename of the
pagetemplate. So, you get an error if you create a browserpage in a
DocTestFile, like so:
ErrorPage = SimpleViewClass(errorFileName, name='error.html')
Passing in file explicitly solves the problem:
ErrorPage = SimpleViewClass(errorFileName, name='error.html',
offering={'__file__': 'README.txt'})
The same thing goes for ViewPagetemplateFile, but there it's called
_prefix instead of offering. Yeah, none of those variable names make
sense.
It can also typically be fixed by passing in __file__ explicitly to the
doctest:
def test_suite():
import doctest
filename = os.path.join(os.pardir, 'namedtemplate.txt')
return doctest.DocFileSuite(
filename,
setUp=pageSetUp, tearDown=zope.component.testing.tearDown,
globs={'__file__':
os.path.abspath(os.path.join(os.path.dirname(__file__), filename))}
)
Other options is to make the usage of __file__ lazy, so that it's only
looked up in the globals when accessed. Because I suspect it's not
actually used except when you get errors, but I'm not 100% sure.
So for the time being, I went for passing in __file__ explicitly in
globs. The tests run under Python 2.4 again.
Cool. I was afraid we were looking at something more insidious than that.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkvgFckACgkQ+gerLs4ltQ7mtwCfSlKCCD/dyzxDjT1SQTWokT5F
qaAAoNYBsgA/PqKHdhnLXtRE9iJFy0Im
=P4PS
-END PGP SIGNATURE-
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Last week's meeting summary
Hi, sorry for the lag (and thanks for Charlie to pick up the reminder today). Here's last weeks summary. Biggeste note: next bug day is on 2010-05-19 which is a rainy Wednesday - a perfect day for sitting inside and smashing bugs. Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development = Weekly Zope developer meeting = This is the summary of the weekly Zope developer meeting which happened on Tuesday, 2010-04-27 on #z...@irc.freenode.org from 3pm to 3:30pm (UTC). The agenda for this meeting is available in the mailing list archives: https://mail.zope.org/pipermail/zope-dev/2010-April/040350.html The IRC logs are located here: http://zope3.pov.lt/irclogs-zope/%23zope.2010-04-27.log.html#t2010-04-27T18:00:43 Review bug day outcome == Quite a few people showed up (Christophe Combelles, Tres Seaver, Christian Theune, Charlie Clark, Roman Joost, during bug day and a substantial number of bugs were handled. Christophe Combelles reported having worked on zope.container and zope.app.container. He backported his fixes to 3.5 and 3.6 awaiting for minor releases (binaries needed). Charlie Clark reported enjoyment about committing patches that were sitting around for quite a while. He had a good experience asking questions as he knew others were working on bugs as well. He points out that we still have a lot of work to do and coding style and test coverage have to improve. Christian Theune reported that he was around during 9am and 3pm CEST as a guide and handled all the Zope 3 bugs that had patches attached. He started working on a test browser bug about referrer handling which is the hottest bug as indicated by launchpad. He'd like to see and attend monthly bug days although weekends are hard. We do have some fixes that are sitting in the repository, waiting for a release now. A task that would be helpful is going through the fix comitted bugs and releasing the packages as appropriate. Adam Groszer worked on the KGS 3.4.1 and made some progress, but he'll need more small steps to conclude the release. Many people agreed that regular bug days will help a lot and we definitely need to do them monthly. A quick discussion about having them on weekdays or weekends turned towards having the next bug day during the week. Charlie suggested Wednesday 2010-05-19 which was supported by other participants and thus agreed as the next bug day. (Already announced on the list and with a wiki page: http://wiki.zope.org/ztk/BugDays) State of bug tracking/LP usage == Christian Theune created the zopeapp project group in anticipation of the bug day and gathered as many zope.app.* packages he could find on Launchpad in them. He also created new projects based on bugs he found/worked on. If any are missing, please tell and more projects can be created quickly. The Zope 3 project which we want to empty out from bug reports (by setting them to 'wontfix' and assigning the bugs to individual projects) still has bugs assigned. Although many people contributed, we need to continue work on this. For the next bug day, we should also plan to clean up the bug trackers further. Christian Theune pointed out that the 'zope.org' project group on Launchpad (https://edge.launchpad.net/zope) is messy and not defined clearly. Although the project group and name is a good entry point for marketing/advertisement the way it's used does more harm than good. The recommendation is to get rid of the project group but there has been no clear decision for this. Windows machines status update == Tres wasn't around but Christian Theune reported that there was progress on the topic of getting people access to the MSDN compiler suite. We'll wait for a report of Tres. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] IRC Meeting Today at 15:00 UTC
Hi, thanks, Charlie for doing this. Would you consider being the second person to handle the meetings (reminders, presence, and summaries) together with me? I'd like to adjust your agenda a little bit: On 05/04/2010 02:24 PM, Charlie Clark wrote: Hi, can't see Theuni anywhere so I thought I'd do the honours - the meeting will be on #zope in just over two-and-a-half hours. Not sure about the Agenda but I think there is some KGS to be carried over from last week and possibly some of the very recent ZTK discussions need formalising so the following is just a suggestion, Agenda -- - KGS status - Windows builds - ZTK status - Python 3 status - Deprecating Python 2.5 We noticed having more than 3 items will make us rush or not get throught them thoroughly. I picked from your list. ;) - KGS 3.4.1 release status - Test runners/nightly builds - Windows machines - Deprecating Python 2.4 and earlier Ongoing issues -- Those issues are currently ongoing. We don't have to discuss them. We just need to follow up on them eventually. New items appears here from the last log: - Making regular releases - Watch packages which have bugs marked as fix committed - Preparing bug day 2010-05-19 - upfront bug triage - Bug tracking - Monitoring tracker status (Charlie Clark, ctheune) - Towards a ZTK release - Establishing ZTK release engineering team (Z2, grok, BB) - Documentation - Release scope - Test runners / nightly builds - Windows machines - Meta - How to organize open issues in the long run (Blueprints? Other tool? Continue text files?) - Find second person to run the weekly meetings Horizon --- These items are currently tracked on the horizon. We won't discuss them at this meeting, but we'll get to them at some point: - Pondering *some* (re-)structuring of the ZTK to allow for better maintenance/release management/communication/marketing. (Chris McDonough) -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Nightly tests for Grok?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martijn Faassen wrote: Hanno Schlichting wrote: Dropping Python 2.4 supports makes most sense to me at this stage. Zope2/Plone only support Python 2.6 for any modern version. I don't know what BlueBream and Grok want to support, but would guess they aim for Python 2.5 + 2.6 support. 2.4 is really old by now. Grok 1.1 aims for 2.5 and 2.6. Grok 1.0 goes for 2.4 and 2.5, but Grok 1.0's stable so we don't have problems when the ZTK is updated. Is there anybody running buildbots for those Grok releases? It would be good if the reports from such tests would make it to the zope-tests list, so that those of us not actively developing with Grok have a shot at knowing if something we did in the ZTK might have triggered breakage. Hmmm, the ZTK buildbots page[1] says that The Health Agency and Securactive are running Grok tests. The Health Agency page shows a fair number of tests for Grok sub-projects, but no one overall test which would be a sensible smoke test for exposing to non-Grok developers. The Securactive stuff seems to be offline (503s or non-resolvable hostnames). [1] http://docs.zope.org/zopetoolkit/process/buildbots.html Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvgIbYACgkQ+gerLs4ltQ6LoQCfYMeAHfQCC6x8VRJsfVlb+q6X MuUAoJRUDTh2vXvEvwH0ZVNuMe7QukRn =7ck1 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Nightly tests for Grok?
On Tue, May 4, 2010 at 15:31, Tres Seaver tsea...@palladion.com wrote: The Securactive stuff seems to be offline (503s or non-resolvable hostnames). Hi Tres, Sorry for that, I've stopped accidentally the builbots this morning. -- Sebastien Douche sdou...@gmail.com Twitter: http://bit.ly/afkrK (agile, lean, python, open source) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 10 OK, 4 Failed, 2 Unknown
On May 4, 2010, at 6:07 AM, Martijn Faassen wrote: For a while already people have been making changes that at least break tests on 2.4. For instance, zope.testing has some facility to pretty print a dictionary that sorts the keys, because Python 2.4's built-in pretty print module apparently doesn't do that yet, The pprint version in Python 2.4 sorts dictionaries too, but only if they don't fit on a single line of output. meaning random test failures can happen. But people have been updating code to use Python's built-in pretty print facility and this will only be reliable on Python 2.5 and higher. I already corrected one such checkin with a simple workaround. pprint(somedict, width=1) This causes Python 2.4 to pretty print somedict one item per line, and thus forces it to sort it. So the tests using pprint can be made reliable on Python 2.4 to 2.6. Zvezdan ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope-Dev Weekly Meeting Summary
Hi, quite a crowd today. Must be have been drawn by my star status! ;-) Charlie -- Charlie Clark Managing Director Clark Consulting Research German Office Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226= Weekly Zope developer meeting = This is the summary of the weekly Zope developer meeting which happened on Tuesday, 2010-05-04 on #z...@irc.freenode.org from15:00 to 15:45 UTC. The agenda for this meeting is available in the mailing list archives: https://mail.zope.org/pipermail/zope-dev/2010-May/040493.html The IRC log is here: http://zope3.pov.lt/irclogs-zope/%23zope.2010-05-04.log.html#t2010-05-04T18:00:13 Present === Charlie Clark (convenor in Theuni's absence), Tres Seaver, Hanno Schlichting, Christophe Combelles, Lennart Regebro, Adam Groszer, Baiju Muthukadan, Marius Gediminas, Leonardo Almeida, Chris Warner, Fred Drake #1 KGS Status = 3.4.1 is nearly ready for release - all tests pass. Some housekeeping still required for a beta release. = Adam to check with Jens Vagelpohl on getting access to dowloads.zope.org #2 Test runners/nightly builds - Windows machines = * 2 test failures on Python 2.4 2.5 from a total of 9404 tests * Still waiting to hear from Microsoft regarding the licences = Tres will follow this up * Amazon image still required from Sidnei * Grok smoketest required = To be taken up by the ZTK release team due to meet on Thursday #3 Deprecating older Python versions 4:1 votes in favour of officially dropping support for Python 2.4. However, after an impassioned plea by Fred Drake it was agreed that providing legacy support for Python 2.4 in ZTK 1.0.x would cost little. Problems are currently restricted to doctests and workarounds are known. No one should start new ZTK-based work with Python 2.4 Support will be dropped completely from ZTK 1.1 on and in any case by 2010-12-31 ZTK 1.1 will allow features that are not compatible with Python 2.4 and possibly also with 2.5 #4 Bug day reminder === The next bug day is 2010-05-19. Launchpad gardening and triaging will be required before then. You've been a wonderful audience! Next meeting will be 2010-05-11 17:00 UTC___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] IRC Meeting Today at 15:00 UTC
Am 04.05.2010, 15:12 Uhr, schrieb Christian Theune c...@gocept.com: Hi, thanks, Charlie for doing this. Would you consider being the second person to handle the meetings (reminders, presence, and summaries) together with me? I don't mind - not hard for me to play the clueless guy asking the dumb questions. But we should probably all have a go at it every now and then for practice. Charlie -- Charlie Clark Managing Director Clark Consulting Research German Office Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] adding the weekly irc meetings record to the ZTK docs?
Hi there, Wouldn't it be useful to add the reports of the weekly IRC meetings to the ZTK docs? This way we have an archive that includes some decisions and such that's easier to go through than the mailing list archive. It also provides a source of information that could then later be integrated into the documentation proper. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] adding the weekly irc meetings record to the ZTK docs?
Am 04.05.2010, 22:43 Uhr, schrieb Martijn Faassen faas...@startifact.com: Hi there, Wouldn't it be useful to add the reports of the weekly IRC meetings to the ZTK docs? This way we have an archive that includes some decisions and such that's easier to go through than the mailing list archive. It also provides a source of information that could then later be integrated into the documentation proper. Hiya, I think some kind of paper trail is definitely a good idea. Not sure if docs is the right place but Christian is planning to put the reports into the svn repository. And both location and form are less important than having an archive*. We'll have something sorted by next week. Probably. Charlie *Of course I want Wag the Dog style access to the archive for when I need to change history! ;-) -- Charlie Clark Managing Director Clark Consulting Research German Office Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] adding the weekly irc meetings record to the ZTK docs?
Charlie Clark wrote: I think some kind of paper trail is definitely a good idea. Not sure if docs is the right place but Christian is planning to put the reports into the svn repository. And both location and form are less important than having an archive*. We'll have something sorted by next week. Probably. Cool! I think since Sphinx + SVN has been working pretty well for us, it makes sense to do more of that. Creates easy access through a website. But separating it from the ZTK procedural docs might make sense, I don't know exactly how the scopes relate. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] adding the weekly irc meetings record to the ZTK docs?
On Tue, May 4, 2010 at 10:54 PM, Charlie Clark charlie.cl...@clark-consulting.eu wrote: I think some kind of paper trail is definitely a good idea. Not sure if docs is the right place but Christian is planning to put the reports into the svn repository. And both location and form are less important than having an archive*. We'll have something sorted by next week. Probably. Cool. Feel free to put them into a new folder inside svn+ssh://svn.zope.org/repos/main/zopetoolkit/doc/source if that is easiest. But do whatever works best for you and Christian. Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
