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 eric.araujo
Recipients Arfrever, BreamoreBoy, eric.araujo, goertzen, gregory.p.smith, hugo_koopmans, javaJake, jdalambert, jepler, loewis, mattcomms, ngie, nico0438, nico38, robsa, rpetrov, solarx, theller, vapier, xudong888
Date 2011-03-25.19:02:44
SpamBayes Score 3.1335037e-09
Marked as misclassified No
Message-id <1301079764.87.0.566919995558.issue1006238@psf.upfronthosting.co.za>
In-reply-to
Content
> Will a new developer be assigned to this bug?
If someone is willing to take charge, yes.  We’re all volunteers, with varying free time and skill sets.  For example, I’m not an expert about compilation, so I try to learn thanks to those issues.

> why are we wasting comments and grave-digging five-year-old discussions?
Comments are not a scarce resource, it’s okay.  An unclosed bug, even that old, is still something to act upon: declare it superseded, outdated, rejected or fix it.  This happens all the time.
History
Date User Action Args
2011-03-25 19:02:44eric.araujosetrecipients: + eric.araujo, loewis, jepler, theller, gregory.p.smith, goertzen, jdalambert, vapier, solarx, robsa, xudong888, nico38, nico0438, hugo_koopmans, mattcomms, rpetrov, Arfrever, ngie, javaJake, BreamoreBoy
2011-03-25 19:02:44eric.araujosetmessageid: <1301079764.87.0.566919995558.issue1006238@psf.upfronthosting.co.za>
2011-03-25 19:02:44eric.araujolinkissue1006238 messages
2011-03-25 19:02:44eric.araujocreate