Groups > linux.debian.maint.python > #16213

Re: Python2 idiosyncrasies in Python3 scripts

From	Alexandre Detiste <alexandre.detiste@gmail.com>
Newsgroups	linux.debian.maint.python
Subject	Re: Python2 idiosyncrasies in Python3 scripts
Date	2024-08-15 13:50 +0200
Message-ID	<JbH9n-5aM9-3@gated-at.bofh.it> (permalink)
References	<JbFTY-5a6P-13@gated-at.bofh.it> <JbGmZ-5age-1@gated-at.bofh.it> <JbGQ1-5aFr-11@gated-at.bofh.it> <JbGZI-5aIS-11@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

Hi,

We should patch  modernize in Debian to make --no-six the default.
(otherwise it is a big pitfall)

"It does not guarantee, but it attempts to spit out a codebase compatible
with Python 2.6+ or Python 3. The code that it generates has a runtime
dependency on six, unless the --no-six option is used. Version 1.9.0 or
later of six is recommended. Some of the fixers output code that is not
compatible with Python 2.5 or lower."

Le jeu. 15 août 2024, 13:39, Andrey Rakhmatullin <wrar@debian.org> a écrit :

> On Thu, Aug 15, 2024 at 01:11:23PM +0200, Jerome BENOIT wrote:
> > > > is there a reliable way to isolate Python2 idiosyncrasies in Python3
> scripts ?
> Try modernize or any linter.
>
> --
> WBR, wRAR
>

Back to linux.debian.maint.python | Previous | Next | Find similar

Thread

Re: Python2 idiosyncrasies in Python3 scripts Alexandre Detiste <alexandre.detiste@gmail.com> - 2024-08-15 13:50 +0200

csiph-web