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 rhettinger
Recipients alexandre.vassalotti, amaury.forgeotdarc, christian.heimes, gvanrossum, mark.dickinson, nascheme, noam, preston, rhettinger, skip.montanaro, tim.peters
Date 2009-02-25.23:09:34
SpamBayes Score 4.498692e-07
Marked as misclassified No
Message-id <>
Gay's code is 3800+ lines and includes many ifdef paths that we need to
get right.  Mark points out that the code itself needs additional work.
 The discussions so far also get into setting compiler flags on
different systems and I would imagine that that would need to be
maintained as those compilers change and as hardware gets updated.  The
main challenge for a maintainer is to be sure that any change doesn't
break something.  AFAICT, this code is very difficult to validate.

The comments is the first 180 lines of code give a good survey of the
issues a maintainer would face when given a bug report in the form of:
eval(repr(f)) != f for myhardware x compiled with mycompiler c with
myflags f and running on operating system z.  There reports would be
even more challenging for cross-platform comparisons.
Date User Action Args
2009-02-25 23:09:36rhettingersetrecipients: + rhettinger, gvanrossum, tim.peters, skip.montanaro, nascheme, amaury.forgeotdarc, mark.dickinson, christian.heimes, alexandre.vassalotti, noam, preston
2009-02-25 23:09:36rhettingersetmessageid: <>
2009-02-25 23:09:35rhettingerlinkissue1580 messages
2009-02-25 23:09:34rhettingercreate