Re: static analysis and other tools for checking Python code

To: debian-python@lists.debian.org
Subject: Re: static analysis and other tools for checking Python code
From: Jeremy Stanley <fungi@yuggoth.org>
Date: Thu, 3 Mar 2016 00:40:56 +0000
Message-id: <[🔎] 20160303004056.GZ2343@yuggoth.org>
In-reply-to: <[🔎] CAKTje6F4-EcCP44jSFKd3oW+4=msC2-zHyEoVzYRV8aVBijxDQ@mail.gmail.com>
References: <[🔎] CAKTje6Hjp+RA666ey=mi7mwsTnxOor2LS85pSU7krziM0Z6=Yw@mail.gmail.com> <[🔎] 20160302235234.GY2343@yuggoth.org> <[🔎] CAKTje6F4-EcCP44jSFKd3oW+4=msC2-zHyEoVzYRV8aVBijxDQ@mail.gmail.com>

On 2016-03-03 08:38:40 +0800 (+0800), Paul Wise wrote:
[...]
> FYI pep257 is definitely packaged:
> 
> https://packages.debian.org/search?keywords=pep257
[...]

Whoops! Thanks--I almost certainly fat-fingered my package search on
that one.
-- 
Jeremy Stanley

Reply to:

References:
- static analysis and other tools for checking Python code
  - From: Paul Wise <pabs@debian.org>
- Re: static analysis and other tools for checking Python code
  - From: Jeremy Stanley <fungi@yuggoth.org>
- Re: static analysis and other tools for checking Python code
  - From: Paul Wise <pabs@debian.org>

Prev by Date: Re: static analysis and other tools for checking Python code
Next by Date: Re: static analysis and other tools for checking Python code
Previous by thread: Re: static analysis and other tools for checking Python code
Next by thread: Re: static analysis and other tools for checking Python code
Index(es):
- Date
- Thread