On Sun, Sep 12, 2021 at 09:06:54AM +, c.bu...@posteo.jp wrote:
> Am 12.09.2021 10:23 schrieb Geert Stappers:
> > In which package is a pep8 code style checker?
>
> Upstream "pep8" was renamed to "pycodestyle".
> So look at
> https://tracker.debian.org/pkg/pycodestyle
>
Yes, that package has
Am 12.09.2021 10:23 schrieb Geert Stappers:
In which package is a pep8 code style checker?
Upstream "pep8" was renamed to "pycodestyle".
So look at
https://tracker.debian.org/pkg/pycodestyle
Hi Geert,
On 12 September 2021 1:53:25 pm IST, Geert Stappers
wrote:
>Hello Debian-Python,
>
>In which package is a pep8 code style checker?
Is this what you seek?
https://tracker.debian.org/pkg/autopep8
Corresponding binary package is python3-autopep8
Nilesh
--
Sent from my Android d
Hello Debian-Python,
In which package is a pep8 code style checker?
With `apt search pep8` I found among others
|
| python3-pep8/unstable,now 1.7.1-9 all [installed]
| Python PEP 8 code style checker - Python 3
|
| python3-pycodestyle/unstable,now 2.6.0-1 all [installed]
| Python style
[Ben Finney, 2014-01-31]
> How should the Python library style guide recommend we do this using
> “pybuild”?
add python-all-dbg or python3-all-dbg to Build-Depends, is that simple
enough? :)
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarow
w should the Python library style guide recommend we do this using
“pybuild”?
--
\ “Welchen Teil von ‘Gestalt’ verstehen Sie nicht? [What part of |
`\‘gestalt’ don't you understand?]” —Karsten M. Self |
_o__)
[Olivier Berger, 2013-11-29]
> On Tue, 05 Nov 2013, Barry Warsaw wrote:
> >
> > There's one little white lie currently: debian/*.pyremove files aren't yet
> > supported for Python 3 package, but Piotr is going to enable that with the
> > next upload of dh-python.
> >
>
> May I ask whether there's
Hi.
On Tue, 05 Nov 2013, Barry Warsaw wrote:
>
> There's one little white lie currently: debian/*.pyremove files aren't yet
> supported for Python 3 package, but Piotr is going to enable that with the
> next upload of dh-python.
>
May I ask whether there's a quick workaround for this issue, for t
Win!
> Based on that, I've done a pass through the library style guide, which I was
> able to greatly simplify.
> https://wiki.debian.org/Python/LibraryStyleGuide
> Please take a look, edit as necessary or follow up here for more discussion.
> There's one little white lie
On Nov 11, 2013, at 09:34 AM, Piotr Ożarowski wrote:
>it should match module name, not source package name (which doesn't
>match module name in most cases).
Thanks for fixing the wiki!
-Barry
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Tr
[Steve Langasek, 2013-11-11]
> A few questions:
>
> (On PYBUILD_NAME)
> Here, we're telling it that the name is foo. This should match the source
> package name, so for example, in enum34, you'd see: [...]
>
> If it's supposed to match the source package name, why does it need to be
> speci
Hi Barry,
On Tue, Nov 05, 2013 at 06:55:33PM -0500, Barry Warsaw wrote:
> Today I migrated the enum34 package to use pybuild. Win!
> Based on that, I've done a pass through the library style guide, which I was
> able to greatly simplify.
> https://wiki.debian.org/Python/
Barry Warsaw writes:
> On Nov 06, 2013, at 12:52 PM, Ben Finney wrote:
>
> >The following “assumption about the Python package you are working on”
> >survives from the historical version:
>
> Thanks for the review. Yeah, this did read awkwardly from the previous
> version. I took a slightly diffe
On Nov 06, 2013, at 12:52 PM, Ben Finney wrote:
>The following “assumption about the Python package you are working on”
>survives from the historical version:
>
> * Your Debian packaging uses debhelper, dh_python2, and is preferably
>source format 3.0 (quilt).
>
>While that's technically acc
Barry Warsaw writes:
> Based on that, I've done a pass through the library style guide, which
> I was able to greatly simplify.
>
> https://wiki.debian.org/Python/LibraryStyleGuide
Thanks for that, Barry!
> Please take a look, edit as necessary or follow up here for mor
Today I migrated the enum34 package to use pybuild. Win!
Based on that, I've done a pass through the library style guide, which I was
able to greatly simplify.
https://wiki.debian.org/Python/LibraryStyleGuide
Please take a look, edit as necessary or follow up here for more discussion.
Th
Hi Dmitry (2012.02.15_17:13:17_+0200)
> Does it make any sense to run "setup.py install" for all python3
> versions? Actually the every next python3 version will overwrite what
> the previous one writes.
That's assuming it's all pure-python.
SR
--
Stefano Rivera
http://tumbleweed.org.za/
H:
Does it make any sense to run "setup.py install" for all python3
versions? Actually the every next python3 version will overwrite what
the previous one writes.
I think that this will be the optimal way:
override_dh_auto_install:
python3 setup.py install --root=... --install-layout=deb
On Feb 13, 2012, at 01:30 PM, Jakub Wilk wrote:
>* Barry Warsaw , 2012-02-07, 20:53:
>>http://wiki.debian.org/Python/LibraryStyleGuide
>
>* “The package […] should have a working setup.py or setup.cfg file” — err,
>* surely setup.cfg without setup.py is not enough.
It will be for Python 3.3 (i.e.
* Piotr Ożarowski , 2012-02-13, 13:58:
http://wiki.debian.org/Python/LibraryStyleGuide
* “The package […] should have a working setup.py or setup.cfg file” —
err, surely setup.cfg without setup.py is not enough.
it will be enough soon (or was "packaging" released already?)
Well, dh doesn't su
[Jakub Wilk, 2012-02-13]
> * Barry Warsaw , 2012-02-07, 20:53:
> >http://wiki.debian.org/Python/LibraryStyleGuide
>
> * “The package […] should have a working setup.py or setup.cfg file”
> — err, surely setup.cfg without setup.py is not enough.
it will be enough soon (or was "packaging" released
* Barry Warsaw , 2012-02-07, 20:53:
http://wiki.debian.org/Python/LibraryStyleGuide
* “The package […] should have a working setup.py or setup.cfg file” —
err, surely setup.cfg without setup.py is not enough.
* “there appears to be no way to prevent distribute explicitly from
downloading th
On Feb 09, 2012, at 01:02 AM, Ben Finney wrote:
>In other words, I'm not directing that as a request to any particular
>people. I'm expressing only the hope that Barry's initial document is,
>in some future form, acknowledged by policy-shapers to embody best
>packaging practices. It's a thank-you
Jakub Wilk writes:
> * Ben Finney , 2012-02-08, 16:02:
> >>http://wiki.debian.org/Python/LibraryStyleGuide
> > Thank you! This is sorely needed, and I hope it gets the blessing of
> > the core Debian Python packagers.
>
> Who are “core Debian Python packagers”?
A vaguely-defined category that I
* Ben Finney , 2012-02-08, 16:02:
http://wiki.debian.org/Python/LibraryStyleGuide
Thank you! This is sorely needed, and I hope it gets the blessing of
the core Debian Python packagers.
Who are “core Debian Python packagers”?
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-python-requ...@li
Barry Warsaw writes:
> In the interest of making life easier for future packagers of Python
> libraries, I wrote up the following guidelines.
>
> http://wiki.debian.org/Python/LibraryStyleGuide
Thank you! This is sorely needed, and I hope it gets the blessing of the
core Debian Python packagers.
In the interest of making life easier for future packagers of Python
libraries, I wrote up the following guidelines.
http://wiki.debian.org/Python/LibraryStyleGuide
I've based these recommendations on feedback I've received on my own packages,
and a few other packages I've submitted bugs on. Thi
27 matches
Mail list logo
