Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #49746

Re: Bug reports [was Re: Python list code of conduct]

References (11 earlier) <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 2013-07-04 00:52 +1000
Subject Re: Bug reports [was Re: Python list code of conduct]
From Chris Angelico <rosuav@gmail.com>
Newsgroups comp.lang.python
Message-ID <mailman.4174.1372863145.3114.python-list@python.org> (permalink)

Show all headers | View raw


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

Back to comp.lang.python | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

OSError [Errno 26] ?!?! Νίκος <nikos@superhost.gr> - 2013-07-02 06:37 +0300
  Re: OSError [Errno 26] ?!?! Cameron Simpson <cs@zip.com.au> - 2013-07-02 15:15 +1000
    Re: OSError [Errno 26] ?!?! Νίκος <nikos@superhost.gr> - 2013-07-02 08:57 +0300
      Re: OSError [Errno 26] ?!?! Cameron Simpson <cs@zip.com.au> - 2013-07-02 17:21 +1000
        Re: OSError [Errno 26] ?!?! Νίκος <nikos@superhost.gr> - 2013-07-02 12:40 +0300
          Re: OSError [Errno 26] ?!?! Chris “Kwpolska” Warrick <kwpolska@gmail.com> - 2013-07-02 12:06 +0200
          Re: OSError [Errno 26] ?!?! Dave Angel <davea@davea.name> - 2013-07-02 08:00 -0400
            Re: OSError [Errno 26] ?!?! Νίκος <nikos@superhost.gr> - 2013-07-02 15:39 +0300
              Re: OSError [Errno 26] ?!?! Chris “Kwpolska” Warrick <kwpolska@gmail.com> - 2013-07-02 15:00 +0200
              Re: OSError [Errno 26] ?!?! Robert Kern <robert.kern@gmail.com> - 2013-07-02 14:58 +0100
                Re: OSError [Errno 26] ?!?! Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-07-03 00:19 +0000
                Re: Persistence of CGI (was: OSError [Errno 26] ?!?!) Tim Chase <python.list@tim.thechases.com> - 2013-07-02 19:57 -0500
              Python list code of conduct Steve Simmons <square.steve@gmail.com> - 2013-07-02 16:51 +0100
                Re: Python list code of conduct Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-07-03 00:42 +0000
              Re: Python list code of conduct Joshua Landau <joshua.landau.ws@gmail.com> - 2013-07-02 20:48 +0100
              Re: Python list code of conduct Skip Montanaro <skip@pobox.com> - 2013-07-02 15:33 -0500
              Re: Python list code of conduct Ned Deily <nad@acm.org> - 2013-07-02 13:52 -0700
                Re: Python list code of conduct Roy Smith <roy@panix.com> - 2013-07-02 19:46 -0400
                Re: Python list code of conduct Ned Deily <nad@acm.org> - 2013-07-02 17:07 -0700
                Re: Python list code of conduct Cameron Simpson <cs@zip.com.au> - 2013-07-03 10:10 +1000
                Bug reports [was Re: Python list code of conduct] Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-07-03 00:52 +0000
                Re: Bug reports [was Re: Python list code of conduct] Joshua Landau <joshua.landau.ws@gmail.com> - 2013-07-03 02:12 +0100
                Re: Bug reports [was Re: Python list code of conduct] Chris Angelico <rosuav@gmail.com> - 2013-07-03 18:02 +1000
                Re: Bug reports [was Re: Python list code of conduct] Roy Smith <roy@panix.com> - 2013-07-03 10:03 -0400
                Re: Bug reports [was Re: Python list code of conduct] Chris Angelico <rosuav@gmail.com> - 2013-07-04 00:15 +1000
                Re: Bug reports [was Re: Python list code of conduct] Roy Smith <roy@panix.com> - 2013-07-03 10:23 -0400
                Re: Bug reports [was Re: Python list code of conduct] Chris Angelico <rosuav@gmail.com> - 2013-07-04 00:52 +1000
                Re: Bug reports [was Re: Python list code of conduct] Grant Edwards <invalid@invalid.invalid> - 2013-07-03 20:11 +0000
                Re: Bug reports [was Re: Python list code of conduct] Roy Smith <roy@panix.com> - 2013-07-03 16:31 -0400
                Re: Bug reports [was Re: Python list code of conduct] Grant Edwards <invalid@invalid.invalid> - 2013-07-03 21:52 +0000
                IPv6 deployment by ISPs (was: Bug reports) Ben Finney <ben+python@benfinney.id.au> - 2013-07-04 11:15 +1000
                Re: Python list code of conduct Terry Reedy <tjreedy@udel.edu> - 2013-07-03 02:18 -0400
                Re: Python list code of conduct Roy Smith <roy@panix.com> - 2013-07-03 10:10 -0400
                Re: Python list code of conduct Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-07-03 17:24 +0000
              Re: Python list code of conduct Ben Finney <ben+python@benfinney.id.au> - 2013-07-03 08:39 +1000
                Re: Python list code of conduct Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-07-03 06:18 +0000
              Re: Python list code of conduct Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2013-07-02 19:15 -0400
                Re: Python list code of conduct Neil Hodgson <nhodgson@iinet.net.au> - 2013-07-03 19:50 +1000
              Re: Python list code of conduct Ben Finney <ben+python@benfinney.id.au> - 2013-07-03 10:39 +1000
                Re: Python list code of conduct rusi <rustompmody@gmail.com> - 2013-07-03 04:50 -0700
                Re: Python list code of conduct Steve Simmons <square.steve@gmail.com> - 2013-07-03 15:18 +0100

csiph-web