Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #49774
| From | Grant Edwards <invalid@invalid.invalid> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: Bug reports [was Re: Python list code of conduct] |
| Date | 2013-07-03 21:52 +0000 |
| Organization | PANIX Public Access Internet and UNIX, NYC |
| Message-ID | <kr26eg$fou$1@reader2.panix.com> (permalink) |
| 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> <kr20h3$omo$1@reader2.panix.com> <roy-336F1A.16311303072013@70-1-84-166.pools.spcsdns.net> |
On 2013-07-03, Roy Smith <roy@panix.com> wrote:
> In article <kr20h3$omo$1@reader2.panix.com>,
> Grant Edwards <invalid@invalid.invalid> wrote:
>
>> On 2013-07-03, 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.
>>
>> I've recently added IPv6 support to some embedded firmware. We had to
>> add it because various purchasing people (mostly government) have
>> non-negotiable feature checklists and "IPv6 support" is starting to
>> show up on the checklists.
>
> Yup. I did one of those. Hmmm, just found the powerpoint deck dated
> March 2006, so we probably started the project around September 2005.
> Same deal, we couldn't sell into government accounts unless we had IPv6.
> Have they actually used it? I doubt it.
>
> The really annoying thing about the project was I never got around to
> implementing rfc1924.
Thankfully, the network library for our RTOS had support functions to
handle rfc1924. Otherwise I would have had to do it myself because
there's no way I could have made it through the project having to read
and type full-length IPv6 addresses the whole time.
>> However, so far, none of the people requiring IPv6 support actually
>> have any plans to use IPv6 -- ever.
>
> What's known in the industry as "shelfware".
Yep. 99.9% of the time, our products are used on small, isolated
industrial networks that have little or no internet connectivity. The
product line started out when a lot of customers weren't even using
IPv4 yet. We still have customers who use our products with all IP
support disabled (though these days it's always on networks that
have other IP traffic).
--
Grant Edwards grant.b.edwards Yow! On the road, ZIPPY
at is a pinhead without a
gmail.com purpose, but never without
a POINT.
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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