Stdlib, what's in, what's out
On 20 September 2017 at 17:16, Dennis Lee Bieber <wlfraed at ix.netcom.com> wrote:
> On Tue, 19 Sep 2017 11:58:47 -0700 (PDT), John Ladasky
> <john_ladasky at sbcglobal.net> declaimed the following:
>>And of course I have found some other third-party packages: scipy, pandas, matplotlib, and PyQt5 are important for my work. I helped a student of mine get selenium running. In the case of PyQt, I found TKinter unsatisfactory many years ago, and went looking for better choices. I used wxPython first, when I was working in Py2. When wxPython was slow to migrate to Py3, I went searching again.
> And if wxPython had been part of the stdlib, it would have meant Python
> 3 would have been delayed years until wxPython had been ported -- or
> wxPython would have been pulled from the stdlib and something else put in
> its place...
> So no help to those migrating.
If wxPython had been part of the stdlib, there would be much more
manpower to port it to 3. Also, the project underwent a complete
rewrite, which dooms many projects to failure. Perhaps they wouldn?t
try the rewrite, or they would port the older codebase to Python 3 so
that it could be shipped. (They?re currently at Beta 2 of the
post-rewrite 4.0.0 version.)
Chris Warrick <https://chriswarrick.com/>