Thanks, Ned. Do you think it would be worth it to use our contacts at Apple to raise the priority of this embarrassment?
On Saturday, October 6, 2012, Ned Deily wrote:
In article
<CAP7+vJKeXqYyvfwipOR+7yTdtUs2eDhvybV3tyZb3ZkX6hta5g@mail.gmail.com>,
Guido van Rossum <guido@python.org> wrote:
> On Fri, Oct 5, 2012 at 4:45 PM, Ned Deily <nad@acm.org> wrote:
> > In article <nad-B4E67A.00475902102012@news.gmane.org>,
> > Update: the bug I filed has been closed as a duplicate of #11932488
> > which apparently at the moment is still open. No other information is
> > available.
>
> Thanks Ned! Is there any way that I could see that bug myself and
> attach myself to updates? Otherwise, can you keep us here appraised of
> developments (even if Apple decides not to fix it)?
I don't think there's any way to see any bug other than ones you have
submitted yourself. All I can see is that the bug I submitted is closed
as a duplicate and now has a Related Problem section that only gives the
other incident number and its status (Open). I can't view anything else
about that other incident. I don't know if I'll get an email update if
its status changes. I'll keep an eye on mine and perhaps ask for a
status update if nothing changes in a few weeks.
--
Ned Deily,
nad@acm.org
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/guido%40python.org