Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed4.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <roy-D94466.10233503072013@70-1-84-166.pools.spcsdns.net>
References: <kqtq4f$skq$1@news.grnet.gr> <mailman.4107.1372749724.3114.python-list@python.org> <kqu77d$s0f$1@news.grnet.gr> <CAMw+j7LvoFbzx-5MLrEiNjDXPutoGinm+abZXHsgn5Vi-p_Kgw@mail.gmail.com> <mailman.4116.1372766435.3114.python-list@python.org> <kquhld$lt5$1@news.grnet.gr> <CAMw+j7JSW7JSXuZuuAHNNswMRc0NVtPbCiaS=QibpvsRUEhAxg@mail.gmail.com> <kqum9j$bsu$1@ger.gmane.org> <a3704f85-2ef1-41e7-8fd1-8d7191f3fddb@email.android.com> <mailman.4125.1372798337.3114.python-list@python.org> <roy-D8C68F.19461302072013@70-1-84-166.pools.spcsdns.net> <51d375de$0$29999$c3e8da3$5496439d@news.astraweb.com> <mailman.4153.1372838561.3114.python-list@python.org> <roy-AD597D.10032403072013@70-1-84-166.pools.spcsdns.net> <mailman.4170.1372860945.3114.python-list@python.org> <roy-D94466.10233503072013@70-1-84-166.pools.spcsdns.net>
Date: Thu, 4 Jul 2013 00:52:16 +1000
Subject: Re: Bug reports [was Re: Python list code of conduct]
From: Chris Angelico <rosuav@gmail.com>
To: python-list@python.org
Content-Type: text/plain; charset=ISO-8859-1
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.4174.1372863145.3114.python-list@python.org>
Lines: 42
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:49746

On Thu, Jul 4, 2013 at 12:23 AM, Roy Smith <roy@panix.com> wrote:
> In article <mailman.4170.1372860945.3114.python-list@python.org>,
>  Chris Angelico <rosuav@gmail.com> wrote:
>
>> On Thu, Jul 4, 2013 at 12:03 AM, Roy Smith <roy@panix.com> wrote:
>> > In article <mailman.4153.1372838561.3114.python-list@python.org>,
>> >  Chris Angelico <rosuav@gmail.com> wrote:
>> >
>> >> Of course, it's possible for there to be dark corners. But if you're
>> >> working with those, you know it full well. The dark corners of Python
>> >> might be in some of its more obscure modules, or maybe in IPv6
>> >> handling,
>> >
>> > The sad thing about this statement is that IPv6 has been around for
>> > about as long as Python.
>>
>> Yeah, and yet so many ISPs simply don't support it (only one of the
>> Australian ISPs I've worked with does - Internode).
>
> My comment was not meant as a flame against Python, but as a flame
> against the whole frigging Internet industry for dragging their feet(*)
> on IPv6 rollout.
>
> (*) It is difficult to walk with any gait other than foot-dragging when
> you are suffering from a severe case of cranio-rectal inversion.

Right. My examples of dark corners were non-specific too; I haven't
actually found any such corners in Python as I don't use it enough.
It's high time the world moved to IPv6 wholesale. Start leaning on
your ISPs to offer /64s (or /56s as Internode give) to all their
customers. Sooner or later they'll have to make it a priority. IPv4
depletion was back in early 2011 - that's two years since IANA gave
out the last blocks to the RIRs. Surely that means something?

At work, we took a stand on this, for what it's worth. We rent
dedicated servers from a number of hosting companies (giving us
geographically and topologically separate servers), and will not work
with anyone who doesn't give IPv6 as well as IPv4 addressing. But
since we currently put less than $100/month into servers, that's not
much of a stand :)

ChrisA