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 neologix
Recipients bquinlan, dmalcolm, jnoller, kristjan.jonsson, lukasz.langa, neologix, pitrou, sandro.tosi, ysj.ray
Date 2011-04-25.21:24:05
SpamBayes Score 1.8628726e-10
Marked as misclassified No
Message-id <1303766647.3.0.893629842394.issue10517@psf.upfronthosting.co.za>
In-reply-to
Content
> So, if it is possible to fix this and remove this weird special case and cast it into the abyss, then by all means, you have my 10 thumbs up.  Not that it counts for much :)

Me too.
We still have a couple hundred RHEL4/5 boxes at work, and I guess we're not alone in this case. It's a really specific case, but I think it would be nice to fix it, especially since it also makes the code more understandable and less error-prone. Unless of course this special treatment is really necessary, in which case I'll have to think of another solution or just drop it.
I'm adding Antoine to the noisy list, since he's noted as thread expert in the Experts Index.
History
Date User Action Args
2011-04-25 21:24:07neologixsetrecipients: + neologix, bquinlan, pitrou, kristjan.jonsson, jnoller, dmalcolm, sandro.tosi, ysj.ray, lukasz.langa
2011-04-25 21:24:07neologixsetmessageid: <1303766647.3.0.893629842394.issue10517@psf.upfronthosting.co.za>
2011-04-25 21:24:05neologixlinkissue10517 messages
2011-04-25 21:24:05neologixcreate