Message73124
| Author |
ghaering |
| Recipients |
amaury.forgeotdarc, ghaering, loewis |
| Date |
2008年09月12日.19:21:59 |
| SpamBayes Score |
0.00013259522 |
| Marked as misclassified |
No |
| Message-id |
<1221247320.71.0.666478867637.issue3846@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Interesting. I was smart enough to not document check_same_thread in the
sqlite3 incarnation of the module.
This has nothing to do with releasing/aquiring the GIL around
sqlite3_prepare, though. Adding the macros was just an oversight.
They're there for all other nontrivial SQLite API calls (sqlite3_step,
sqlite3_reset, sqlite3_open, sqlite3_finalize and also already for the
"BEGIN"/"COMMIT" and "ROLLBACK" versions of sqlite3_prepare in connection.c. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2008年09月12日 19:22:00 | ghaering | set | recipients:
+ ghaering, loewis, amaury.forgeotdarc |
| 2008年09月12日 19:22:00 | ghaering | set | messageid: <1221247320.71.0.666478867637.issue3846@psf.upfronthosting.co.za> |
| 2008年09月12日 19:21:59 | ghaering | link | issue3846 messages |
| 2008年09月12日 19:21:59 | ghaering | create |
|