Message160148
| Author | pitrou |
|---|---|
| Recipients | Arfrever, brett.cannon, eric.araujo, eric.smith, eric.snow, lemburg, ncoghlan, pitrou, python-dev |
| Date | 2012-05-07.15:05:28 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1336403010.3352.5.camel@localhost.localdomain> |
| In-reply-to | <1336402898.09.0.459727646619.issue14657@psf.upfronthosting.co.za> |
| Content | |
|---|---|
> Should we have a separate context manager for this, or just make it a > flag for a unified import_state() decorator? Or do we want to *always* > force the use of the Python code instead of the frozen code? Ideally, we would want to test both versions, so that any oddity in the freezing mechanism gets exercised and diagnosed properly. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012-05-07 15:05:29 | pitrou | set | recipients: + pitrou, lemburg, brett.cannon, ncoghlan, eric.smith, eric.araujo, Arfrever, python-dev, eric.snow |
| 2012-05-07 15:05:28 | pitrou | link | issue14657 messages |
| 2012-05-07 15:05:28 | pitrou | create | |