Message246807
| Author | steve.dower |
|---|---|
| Recipients | James Salter, paul.moore, steve.dower, tim.golden, vstinner, zach.ware |
| Date | 2015-07-16.15:37:22 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1437061042.84.0.380670214404.issue24643@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
That's probably an option, though it would break extensions that use `timezone` expecting it to work. But it seems like any change is going to cause that. I prefer defining _Py_timezone, since at least we can offer something that is portable for all Python 3.5 platforms (that support timezones), unlike timezone/_timezone (MSVC deprecated `timezone` a few versions ago and has just removed it completely, hence the breakage). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015-07-16 15:37:22 | steve.dower | set | recipients: + steve.dower, paul.moore, vstinner, tim.golden, zach.ware, James Salter |
| 2015-07-16 15:37:22 | steve.dower | set | messageid: <1437061042.84.0.380670214404.issue24643@psf.upfronthosting.co.za> |
| 2015-07-16 15:37:22 | steve.dower | link | issue24643 messages |
| 2015-07-16 15:37:22 | steve.dower | create | |