Message 73370 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	jcea
Recipients	barry, benjamin.peterson, gregory.p.smith, jcea, mhammond, trent
Date	2008-09-18.11:22:41
SpamBayes Score	0.0018072
Marked as misclassified	No
Message-id	<1221736971.46.0.318564376983.issue3892@psf.upfronthosting.co.za>
In-reply-to

Content
Adding Nelson to the nosy list, since I'm unable to debug any Windows issue by myself. I'm very interested in the report saying that MS Windows Berkeley DB correctly sends the db.DB_EVENT_REP_STARTUPDONE event in his setup. That could indicate some issue in the buildbot. Barry, I don't consider this a "release blocker" for 2.6.0. This is a very advanced feature (database replication). This must be solved, but 2.6 doesn't need to be delayed for it.

Adding Nelson to the nosy list, since I'm unable to debug any Windows
issue by myself.

I'm very interested in the report saying that MS Windows Berkeley DB
correctly sends the db.DB_EVENT_REP_STARTUPDONE event in his setup. That
could indicate some issue in the buildbot.

Barry, I don't consider this a "release blocker" for 2.6.0. This is a
very advanced feature (database replication). This must be solved, but
2.6 doesn't need to be delayed for it.

History
Date	User	Action	Args
2008-09-18 11:22:51	jcea	set	recipients: + jcea, mhammond, barry, gregory.p.smith, benjamin.peterson, trent
2008-09-18 11:22:51	jcea	set	messageid: <1221736971.46.0.318564376983.issue3892@psf.upfronthosting.co.za>
2008-09-18 11:22:42	jcea	link	issue3892 messages
2008-09-18 11:22:41	jcea	create