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 loewis
Recipients Eli_B, Stephen.White, brian.curtin, carwyn, cgohlke, dontbugme, eric.araujo, erluk, ghazel, jaraco, jerome.radix, jkloth, loewis, menekali@gmail.com, pje, r.david.murray, santoso.wijaya, srid, ssbarnea, tarek, vr.gamer
Date 2012-01-23.21:55:17
SpamBayes Score 0.000482776
Marked as misclassified No
Message-id <4F1DD744.5070703@v.loewis.de>
In-reply-to <1327251955.78.0.547432775167.issue6792@psf.upfronthosting.co.za>
Content
> If priority escalation is out of the question

It's not out of the question - it's just that setting the priority on
the issue is not a proper way to escalate.

Instead, there are two forms of escalation available:
1. submit a patch that fixes the issue
2. pay somebody to fix the issue if you can't fix it yourself
History
Date User Action Args
2012-01-23 21:55:17loewissetrecipients: + loewis, pje, jaraco, ghazel, tarek, jkloth, eric.araujo, dontbugme, r.david.murray, carwyn, ssbarnea, brian.curtin, srid, cgohlke, erluk, Stephen.White, santoso.wijaya, menekali@gmail.com, jerome.radix, Eli_B, vr.gamer
2012-01-23 21:55:17loewislinkissue6792 messages
2012-01-23 21:55:17loewiscreate