Re: [Python-Dev] Python 2.x and 3.x use survey, 2014 edition
Also keep in mind that not all Python libraries are on PyPI. For non-Python projects with Python bindings (think video players, OpenCV, systemd, Samba), distribution via PyPI doesn't make much sense. And since the Python bindings are usually second-class citizens, the porting doesn't have a high priority. If anyone is wondering why their favorite Linux distribution is stuck with Python 2 – well, I can only speak for Fedora, but nowadays most of what's left are CPython bindings. No pylint --py3k or 2to3 will help there... On Fri, Dec 12, 2014 at 7:24 PM, Mark Roberts wrote: > So, I'm more than aware of how to write Python 2/3 compatible code. I've > ported 10-20 libraries to Python 3 and write Python 2/3 compatible code at > work. I'm also aware of how much writing 2/3 compatible code makes me hate > Python as a language. It'll be a happy day when one of the two languages > dies so that I never have to write code like that again. However, my point > was that just because the core libraries by usage are *starting* to roll out > Python 3 support doesn't mean that things are "easy" or "convenient" yet. > There are too many libraries in the long tail which fulfill semi-common > purposes and haven't been moved over yet. Yeah, sure, they haven't been > updated in years... but neither has the language they're built on. > > I suppose what I'm saying is that the long tail of libraries is far more > valuable than it seems the Python3 zealots are giving it credit for. Please > don't claim it's "easy" to move over just because merely most of the top 20 > libraries have been moved over. :-/ > > -Mark > > On Thu, Dec 11, 2014 at 12:14 PM, Dan Stromberg wrote: >> >> On Thu, Dec 11, 2014 at 11:35 AM, Mark Roberts wrote: >> > I disagree. I know there's a huge focus on The Big Libraries (and >> > wholesale >> > migration is all but impossible without them), but the long tail of >> > libraries is still incredibly important. It's like saying that migrating >> > the >> > top 10 Perl libraries to Perl 6 would allow people to completely ignore >> > all >> > of CPAN. It just doesn't make sense. >> >> Things in the Python 2.x vs 3.x world aren't that bad. >> >> See: >> https://python3wos.appspot.com/ and >> https://wiki.python.org/moin/PortingPythonToPy3k >> http://stromberg.dnsalias.org/~strombrg/Intro-to-Python/ (writing code >> to run on 2.x and 3.x) >> >> I believe just about everything I've written over the last few years >> either ran on 2.x and 3.x unmodified, or ran on 3.x alone. If you go >> the former route, you don't need to wait for your libraries to be >> updated. >> >> I usually run pylint twice for my projects (after each change, prior >> to checkin), once with a 2.x interpreter, and once with a 3.x >> interpreter (using >> http://stromberg.dnsalias.org/svn/this-pylint/trunk/this-pylint) , but >> I gather pylint has the option of running on a 2.x interpreter and >> warning about anything that wouldn't work on 3.x. -- https://mail.python.org/mailman/listinfo/python-list
Re: [Python-Dev] Python 2.x and 3.x use survey, 2014 edition
On Sun, Dec 14, 2014 at 1:14 AM, Nick Coghlan wrote: [...] > Barry, Petr, any of the other folks working on distro level C extension > ports, perhaps one of you would be willing to consider an update to the C > extension porting guide to be more in line with Brett's latest version of > the Python level porting guide? I can make it a 20%-time project starting in January, if no-one beats me to it. -- https://mail.python.org/mailman/listinfo/python-list
Re: Linux users: please run gui tests
On Fri, Aug 7, 2015 at 4:07 AM, Terry Reedy wrote:
> Python has an extensive test suite run after each 'batch' of commits on a
> variety of buildbots. However, the Linux buildbots all (AFAIK) run
> 'headless', with gui's disabled. Hence the following
> test_tk test_ttk_guionly test_idle
> (and on 3.5, test_tix, but not important)
> are skipped either in whole or in part.
>
> We are planning on adding the use of tkinter.ttk to Idle after the 3.5.0
> release, but a couple of other core developers have expressed concern about
> the reliability of tkinter.ttk on Linux.
>
> There is also an unresolved issue where test_ttk hung on Ubuntu Unity 3
> years ago. https://bugs.python.org/issue14799
>
> I would appreciate it if some people could run the linux version of
> py -3.4 -m test -ugui test_tk test_ttk_guionly test_idle
> (or 3.5). I guess this means 'python3 for the executable.
>
> and report here python version, linux system, and result.
> Alteration of environment and locale is a known issue, skip that.
On Fedora 21, the tests pass (Python 3.4.1 and latest dev version).
On Fedora 23, I see:
$ python3 -V
Python 3.4.3
$ python3 -m test -ugui test_tk test_ttk_guionly test_idle
[1/3] test_tk
[2/3] test_ttk_guionly
[3/3] test_idle
All 3 tests OK.
$ ./python -V
Python 3.6.0a0
$ ./python -m test -ugui test_tk test_ttk_guionly test_idle
[1/3] test_tk
[2/3] test_ttk_guionly
[3/3] test_idle
test test_idle failed -- Traceback (most recent call last):
File "/home/pviktori/dev/cpython/Lib/idlelib/idle_test/test_configdialog.py",
line 27, in test_dialog
d=ConfigDialog(self.root, 'Test', _utest=True)
File "/home/pviktori/dev/cpython/Lib/idlelib/configDialog.py", line
71, in __init__
self.LoadConfigs()
File "/home/pviktori/dev/cpython/Lib/idlelib/configDialog.py", line
1078, in LoadConfigs
self.LoadFontCfg()
File "/home/pviktori/dev/cpython/Lib/idlelib/configDialog.py", line
980, in LoadFontCfg
self.SetFontSample()
File "/home/pviktori/dev/cpython/Lib/idlelib/configDialog.py", line
858, in SetFontSample
self.labelFontSample.config(font=newFont)
File "/home/pviktori/dev/cpython/Lib/tkinter/__init__.py", line
1330, in configure
return self._configure('configure', cnf, kw)
File "/home/pviktori/dev/cpython/Lib/tkinter/__init__.py", line
1321, in _configure
self.tk.call(_flatten((self._w, cmd)) + self._options(cnf))
_tkinter.TclError: expected integer but got ""
2 tests OK.
1 test failed:
test_idle
Tk version: 8.6.4
--
https://mail.python.org/mailman/listinfo/python-list
