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

Groups > comp.lang.python > #87671

Re: Python 2 to 3 conversion - embrace the pain

From Ned Deily <nad@acm.org>
Subject Re: Python 2 to 3 conversion - embrace the pain
Date 2015-03-18 02:11 -0700
References (1 earlier) <87vbi4ovp1.fsf@elektro.pacujo.net> <me4l3v$ghe$1@dont-email.me> <am4cga9sn16m74v1952gnfq5u443mkk9l1@4ax.com> <roy-9FB3DB.19430815032015@news.panix.com> <meb6ct$11j$1@dont-email.me>
Newsgroups comp.lang.python
Message-ID <mailman.519.1426669904.21433.python-list@python.org> (permalink)

Show all headers | View raw

In article <meb6ct$11j$1@dont-email.me>, John Nagle <nagle@animats.com> 
wrote:
>    If only that were true.  Look what I'm reporting bugs on:
> 
> 	ssl - a core Python module.

I assume you're referring to http://bugs.python.org/issue23476.
It seems to me that the issue there was not in Python but due to a 
shortcoming in OpenSSL itself.  When the shortcoming was addressed in 
the most recent major release of OpenSSL (1.0.2), both Python 2 and 3 
were modified to take advantage of the new OpenSSL API option when 
available.  Also you would have seen the same behavior if you upgraded 
to the current version of Python 2 (2.7.9), since 2.7.9 now has most of 
the same TLS/SSL support code and best practice defaults that 3.4.3 
does.  So let's not blame this one on Python 3. 
 
> 	cPickle - a core Python module.

http://bugs.python.org/issue23655

No question that this appears to be a serious problem and, while yet 
unresolved, does appear to be a bug in Python 3 itself.

> 	pymysql - the pure-Python recommended way to talk to MySQL.
> 	bs4/html5parser - a popular parser for HTML5

I'm not in a position to comment on those third-party projects. It's too 
bad that you ran into problems with them.  Any idea if you would have 
seen similar problems if you had used them with Python 2?

In any case, of the two problems noted with Python itself, there is only 
one that appears to be Python 3 related.  That's still not good but I 
think it would be fairer to ascribe a good chunk of the pain you've 
experienced to the more common pain of upgrading any major software 
system that depends on multiple third-party components.

-- 
 Ned Deily,
 nad@acm.org

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