➜

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 flox, jcea
Date 2010-08-25.01:21:49
SpamBayes Score 3.5910352e-06
Marked as misclassified No
Message-id <1282699311.49.0.794641887675.issue9675@psf.upfronthosting.co.za>
In-reply-to
Content 
The problem is that the "-We" is converting the CObject use to ERRORs, when this API is perfectly legal in Python 2.7.

bsddb 4.8.4 DOES *legally* uses CObjects in Python 2.7.

In pybsddb 5.0.0 I migrated to Capsule, since 5.0 doesn't support python 3.0 anymore (python 3.0 didn't support capsule).

I can commit a "4.8.4.1" version with Capsule support, for I think this crash is overzealot. 

According to http://bugs.python.org/issue7992#msg104140 , CObject is not actually deprecated in Python 2.7, so it should not cause CObjects use with "-We" to be an error. Read the mail thread. In particular: http://mail.python.org/pipermail/python-committers/2010-April/000882.html .

I would suggest to drop DeprecationWarnings for CObjects in 2.7.1.

Comments?.
History
Date User Action Args
2010-08-25 01:21:51jceasetrecipients: + jcea, flox
2010-08-25 01:21:51jceasetmessageid: <1282699311.49.0.794641887675.issue9675@psf.upfronthosting.co.za>
2010-08-25 01:21:50jcealinkissue9675 messages
2010-08-25 01:21:49jceacreate