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 cjwelborn
Recipients cjwelborn, r.david.murray, tim.peters
Date 2014-01-31.03:03:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1391137382.79.0.472682971905.issue18916@psf.upfronthosting.co.za>
In-reply-to
Content
Yep, I missed the PyThread_allocate_lock reference. As far as the Argument Clinic Derby, I've been following the python-dev list and reading about Argument Clinic, but I don't know enough about it to do the conversion. It's a really good tool from what I can tell. I'll have to study it some more so in the future I can possibly help with the conversions.

I see the threading module listed in <a href="http://bugs.python.org/issue20185">Issue #20185</a> (Derby #17), but no patch for it yet.

Forgive my newbness, but I omitted putting a reference to PyThread_allocate_lock in the comments because I was confused about what kind of reference you were talking about. Something about making sure Python users see "threading.Lock" instead of "PyThread_allocate_lock", or moving a statement like "to create a lock in C, call the PyThread_allocate_lock function" into the comments. If it's important for it to be there, could you let me know so I can make the edit?

Hopefully I have been of some help, instead of just wasting your time.
History
Date User Action Args
2014-01-31 03:03:02cjwelbornsetrecipients: + cjwelborn, tim.peters, r.david.murray
2014-01-31 03:03:02cjwelbornsetmessageid: <1391137382.79.0.472682971905.issue18916@psf.upfronthosting.co.za>
2014-01-31 03:03:02cjwelbornlinkissue18916 messages
2014-01-31 03:03:02cjwelborncreate