A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2012-October/122111.html below:

[Python-Dev] Bad python 2.5 build on OSX 10.8 mountain lion

[Python-Dev] Bad python 2.5 build on OSX 10.8 mountain lion [Python-Dev] Bad python 2.5 build on OSX 10.8 mountain lionNed Deily nad at acm.org
Sun Oct 7 00:42:42 CEST 2012
In article 
<CAP7+vJKeXqYyvfwipOR+7yTdtUs2eDhvybV3tyZb3ZkX6hta5g at mail.gmail.com>,
 Guido van Rossum <guido at python.org> wrote:
> On Fri, Oct 5, 2012 at 4:45 PM, Ned Deily <nad at acm.org> wrote:
> > In article <nad-B4E67A.00475902102012 at 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 at acm.org

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4