Message167687
| Author |
skrah |
| Recipients |
Arfrever, christian.heimes, georg.brandl, mark.dickinson, meador.inge, ncoghlan, pitrou, python-dev, skrah, vstinner |
| Date |
2012年08月08日.11:31:54 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1344425520.44.0.534562747139.issue15573@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Right, byte order specifiers are always at the beginning of the string.
That is at least something. I wonder if we should tighten PEP-3118 to
demand a canonical form of format strings, such as (probably incomplete):
- Whitespace is disallowed.
- Except for 's', no zero count may be given.
- A count of 1 (redundant) is disallowed.
- Repeats must be specified in terms of count + single char.
That still leaves the '=I' != '=L' problem. Why are there two
specifiers describing uint32_t?
Anyway, as Meador says, this can get tricky and I don't think this
can be resolved before beta-2. I'm attaching a patch that should
behave well for the restricted canonical form at least. |
|