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

Groups > comp.lang.python > #87667

Re: Python 2 to 3 conversion - embrace the pain

From John Nagle <nagle@animats.com>
Newsgroups comp.lang.python
Subject Re: Python 2 to 3 conversion - embrace the pain
Date 2015-03-17 23:37 -0700
Organization A noiseless patient Spider
Message-ID <meb6ct$11j$1@dont-email.me> (permalink)
References <550351BF.5020108@animats.com> <87vbi4ovp1.fsf@elektro.pacujo.net> <me4l3v$ghe$1@dont-email.me> <am4cga9sn16m74v1952gnfq5u443mkk9l1@4ax.com> <roy-9FB3DB.19430815032015@news.panix.com>

Show all headers | View raw

On 3/15/2015 4:43 PM, Roy Smith wrote:
> In article <am4cga9sn16m74v1952gnfq5u443mkk9l1@4ax.com>,
>  Mario Figueiredo <marfig@gmail.com> wrote:
> 
>> What makes you think your anecdotal bugs constitute any sort of
>> evidence this programming language isn't ready to be used by the
>> public?
> 
> There's several levels of "ready".
> 
> I'm sure the core language is more than ready for production use for a 
> project starting from scratch which doesn't rely on any third party 
> libraries.
> 
> The next step up on the "ready" ladder would be a new project which will 
> require third-party libraries.  And that pretty much means any 
> non-trivial project.  I'm reasonably confident that most common use 
> cases can now be covered by p3-ready third party modules. 

   If only that were true.  Look what I'm reporting bugs on:

	ssl - a core Python module.
	cPickle - a core Python module.
	pymysql - the pure-Python recommended way to talk to MySQL.
	bs4/html5parser - a popular parser for HTML5

We're not in exotic territory here.  I've done lots of exotic
projects, but this isn't one of them.

There's progress.  The fix to "ssl" has been made and committed.
I have a workaround for the cPickle bug - use pure-Python Pickle.
I have a workaround for the pymysql problem, and a permanent fix
is going into the next release of pymysql. I have a tiny test case
for bs4/html5parser that reproduces the bug on a tiny snippet of
HTML, and that's been uploaded to the BS4 issues tracker.
I don't have a workaround for that.

All this has cost me about two weeks of work so far.

The "everything is just fine" comments are not helpful.
Denial is not a river in Egypt.

				John Nagle

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

Thread

Python 2 to 3 conversion - embrace the pain John Nagle <nagle@animats.com> - 2015-03-13 14:08 -0700
  Re: Python 2 to 3 conversion - embrace the pain INADA Naoki <songofacandy@gmail.com> - 2015-03-14 07:27 +0900
    Re: Python 2 to 3 conversion - embrace the pain John Nagle <nagle@animats.com> - 2015-03-13 16:01 -0700
      Re: Python 2 to 3 conversion - embrace the pain Ned Deily <nad@acm.org> - 2015-03-13 16:14 -0700
      Re: Python 2 to 3 conversion - embrace the pain Chris Angelico <rosuav@gmail.com> - 2015-03-14 12:40 +1100
      Re: Python 2 to 3 conversion - embrace the pain INADA Naoki <songofacandy@gmail.com> - 2015-03-15 16:01 +0900
        Re: Python 2 to 3 conversion - embrace the pain wxjmfauth@gmail.com - 2015-03-15 01:11 -0700
  Re: Python 2 to 3 conversion - embrace the pain Marko Rauhamaa <marko@pacujo.net> - 2015-03-14 10:00 +0200
    Re: Python 2 to 3 conversion - embrace the pain John Nagle <nagle@animats.com> - 2015-03-15 12:05 -0700
      Re: Python 2 to 3 conversion - embrace the pain Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-03-15 19:16 +0000
      Re: Python 2 to 3 conversion - embrace the pain "Fetchinson ." <fetchinson@googlemail.com> - 2015-03-15 21:59 +0100
      Re: Python 2 to 3 conversion - embrace the pain Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-03-15 21:05 +0000
        Re: Python 2 to 3 conversion - embrace the pain Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2015-03-16 11:25 +1100
          Re: Python 2 to 3 conversion - embrace the pain Chris Angelico <rosuav@gmail.com> - 2015-03-16 11:38 +1100
          Re: Python 2 to 3 conversion - embrace the pain Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-03-16 01:07 +0000
      Re: Python 2 to 3 conversion - embrace the pain Mario Figueiredo <marfig@gmail.com> - 2015-03-16 00:23 +0100
        Re: Python 2 to 3 conversion - embrace the pain Roy Smith <roy@panix.com> - 2015-03-15 19:43 -0400
          Re: Python 2 to 3 conversion - embrace the pain Chris Angelico <rosuav@gmail.com> - 2015-03-16 11:00 +1100
          Re: Python 2 to 3 conversion - embrace the pain Mario Figueiredo <marfig@gmail.com> - 2015-03-16 01:19 +0100
          Re: Python 2 to 3 conversion - embrace the pain John Nagle <nagle@animats.com> - 2015-03-17 23:37 -0700
            Re: Python 2 to 3 conversion - embrace the pain Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-03-18 08:41 +0000
            Re: Python 2 to 3 conversion - embrace the pain Ned Deily <nad@acm.org> - 2015-03-18 02:11 -0700
              Re: Python 2 to 3 conversion - embrace the pain Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2015-03-18 21:53 +1100
                Re: Python 2 to 3 conversion - embrace the pain Rustom Mody <rustompmody@gmail.com> - 2015-03-18 06:42 -0700
                Re: Python 2 to 3 conversion - embrace the pain wxjmfauth@gmail.com - 2015-03-18 07:23 -0700
                Re: Python 2 to 3 conversion - embrace the pain Paul Rubin <no.email@nospam.invalid> - 2015-03-18 09:35 -0700
                Re: Python 2 to 3 conversion - embrace the pain Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2015-03-20 09:48 +1100
        Re: Python 2 to 3 conversion - embrace the pain Kishan Thobhani <thobhanikishan@gmail.com> - 2015-03-16 05:05 +0530
        Re: Python 2 to 3 conversion - embrace the pain Kishan Thobhani <thobhanikishan@gmail.com> - 2015-03-16 05:23 +0530
  Re: Python 2 to 3 conversion - embrace the pain Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-03-14 09:05 +0000

csiph-web