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 | christian.heimes |
|---|---|
| Recipients | christian.heimes, eric.smith, nnorwitz |
| Date | 2008年03月25日.10:30:02 |
| SpamBayes Score | 0.047205742 |
| Marked as misclassified | No |
| Message-id | <1206441004.8.0.283185927897.issue2477@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I've carefully examined both version. I agree that update_flags_from_node is too fragile. I haven't verified my theory but I *think* the current code does neither support from __future__ import egg, spam nor from __future__ import egg from __future__ import spam The PyParser_ParseFileFlagsEx() is easier and more stable. I'll go with it. By the way I also like your name "unicode_strings". Should we stay with it or use my idea "unicode_literals"? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年03月25日 10:30:05 | christian.heimes | set | spambayes_score: 0.0472057 -> 0.047205742 recipients: + christian.heimes, nnorwitz, eric.smith |
| 2008年03月25日 10:30:04 | christian.heimes | set | spambayes_score: 0.0472057 -> 0.0472057 messageid: <1206441004.8.0.283185927897.issue2477@psf.upfronthosting.co.za> |
| 2008年03月25日 10:30:03 | christian.heimes | link | issue2477 messages |
| 2008年03月25日 10:30:03 | christian.heimes | create | |