Author meador.inge
Recipients Arfrever, christian.heimes, georg.brandl, mark.dickinson, meador.inge, ncoghlan, pitrou, python-dev, skrah, vstinner
Date 2012-08-08.02:52:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I agree that the general case is complicated.  It will get even more complicated if the full of PEP 3118 gets implemented since it turns into a tree comparison.  In general, I think you will probably have to compute some canonical form and then compare the canonical forms.

Here are a few more cases that don't work out in the attached algorithm:

  1. Repeat characters - '2c' == 'cc'
  2. Whitespace - 'h   h' == 'hh' 

Also, currently the byte order specifiers are always at the beginning of the string.  We discussed in issue3132 scoping them per the nested structures, but decided to drop that unless somebody barks about it since it is fairly complicated without a clear benefit.  So, I wouldn't worry about them being scattered through the string.

This seems like sort of a slippery slope.  I need to think about it more, but my first impression is that coming up with some way to compare format strings is going to be nasty.
Date User Action Args
2012-08-08 02:52:23meador.ingesetrecipients: + meador.inge, georg.brandl, mark.dickinson, ncoghlan, pitrou, vstinner, christian.heimes, Arfrever, skrah, python-dev
2012-08-08 02:52:23meador.ingesetmessageid: <>
2012-08-08 02:52:22meador.ingelinkissue15573 messages
2012-08-08 02:52:22meador.ingecreate