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 ggenellina
Recipients ggenellina, lkcl
Date 2009-01-17.03:25:17
SpamBayes Score 0.0043980796
Marked as misclassified No
Message-id <1232162722.51.0.841743565582.issue4956@psf.upfronthosting.co.za>
In-reply-to
Content
Ok, imagine for a moment that your patch is accepted and applied. 
Python runs in a wide variety of systems. Now imagine that, in a few of 
them, it stops running. What would you say to defend your changes? "I 
have no idea why, but it works for me!". I have no doubt your changes 
would be reverted in two nanoseconds, and your chances of getting a 
second patch accepted would drop near zero.

I understand your project and hope you successfully complete your 
goals, but it seems it's not madure enough yet. At this stage, blogging 
about your progresses and writing some sort of recipe would be more 
adequate, until you get a system that builds cleanly and passes most 
(if not all) test cases. This applies to your other pending patches too.

PS: I don't know the English term, but here in Argentina (Spanish) the 
way you "fix" bugs would be called "chapuza". No offense intended.
History
Date User Action Args
2009-01-17 03:25:22ggenellinasetrecipients: + ggenellina, lkcl
2009-01-17 03:25:22ggenellinasetmessageid: <1232162722.51.0.841743565582.issue4956@psf.upfronthosting.co.za>
2009-01-17 03:25:19ggenellinalinkissue4956 messages
2009-01-17 03:25:17ggenellinacreate