Hi Ondrej,
On Aug 08, 2016, at 11:46 AM, Ondrej Novy wrote:
>what do you think about this:
>https://anonscm.debian.org/cgit/python-modules/packages/pep8.git/commit/?id=655e6f631fc854c51f48f142e58bdb6b4af8494f
>
>With this change we can make slow transition pep8 -> pycodestyle without
>breaking cu
Hi,
what do you think about this:
https://anonscm.debian.org/cgit/python-modules/packages/pep8.git/commit/?id=655e6f631fc854c51f48f142e58bdb6b4af8494f
With this change we can make slow transition pep8 -> pycodestyle without
breaking current pep8 users.
BTW: pycodestyle is still in NEW, so don't
On Aug 08, 2016, at 12:52 AM, Ondrej Novy wrote:
>created (https://bugs.debian.org/833683) and uploaded :)
\o/
Thanks,
-Barry
pgpl8ZGPKewXt.pgp
Description: OpenPGP digital signature
Hi,
2016-06-21 13:43 GMT+02:00 Barry Warsaw :
> >I'd simply create new source package with new binary packages and remove
> >src:pep8 even from Stretch (once all rev. dependencies use new package).
>
created (https://bugs.debian.org/833683) and uploaded :)
--
Best regards
Ondřej Nový
On 06/21/2016 03:35 AM, Ben Finney wrote:
> My understanding is that renaming a source package is rather more
> disruptive than renaming a binary package, is that right?
To my experience, renaming a source package is painless. The pain used
to be for FTP masters, but now even that is automated now
On Jun 21, 2016, at 10:18 AM, Piotr Ożarowski wrote:
>I'd simply create new source package with new binary packages and remove
>src:pep8 even from Stretch (once all rev. dependencies use new package).
Yep, I'm leaning toward this, or at least creating a new source package for
pycodestyle. I thin
[Barry Warsaw, 2016-06-20]
> I think we eventually want to rename Source:pep8 to Source:pycodestyle, as
> well as Package:pep8, Package:python-pep8, and Package:python3-pep8. I
> suppose we could at least keep the source package name unchanged and
> transition to the new binary package names.
I'd
Barry Warsaw writes:
> You might be aware that the upstream pep8 package has been renamed to
> pycodestyle. Both the command line and imports have changed, although
> not in a backward compatible way unfortunately[1].
Ah, Python. We love you, but please grow a proper API versioning system :-/
>
You might be aware that the upstream pep8 package has been renamed to
pycodestyle. Both the command line and imports have changed, although not in
a backward compatible way unfortunately[1].
There's a new upstream flake8 which I'm preparing in git-dpm, but it will be
blocked until we decide what
9 matches
Mail list logo
