Hi!
I'd like to propose moving pytest-pep8 from pytest-dev on Bitbucket to
GitHub and my pytest-flakes from my GitHub repository to pytest-dev.
Since I use both myself all the time, I would continue maintaining them.
Thoughts? Process?
Regards,
Florian Schulze
___
Sounds reasonable,
i would like to note that by now i believe integrating linting into
normal testing is a step back since the reporting needs are so different
its one of the reasons why i dropped my work on pytest-codecheckers
(which is more like flake8)
-- Ronny
Am 14.03.2018 um 09:35 schrieb
On 14 Mar 2018, at 10:00, RonnyPfannschmidt wrote:
Sounds reasonable,
Ok
i would like to note that by now i believe integrating linting into
normal testing is a step back since the reporting needs are so
different
its one of the reasons why i dropped my work on pytest-codecheckers
(which i
i like to use a tox env with flake8 set up,
additionally my editor always complains about all violations
(imho if linting should happen as early as typing, but at least as early
as when you save a file)
on top of that linting issues trigger ci failure
im currently also looking at tools like sideci
Hi all,
Nice initiative Floris and Ronny!
I definitely like the idea of having a set of talks and introductions so
more people are encouraged to give talks and teach pytest, from local group
meetings to bigger conferences.
Cheers,
Bruno
On Wed, Mar 14, 2018 at 2:33 AM RonnyPfannschmidt <
openso
On 14 Mar 2018, at 10:50, RonnyPfannschmidt wrote:
i like to use a tox env with flake8 set up,
This is what devpi does and in my day to day use I miss issues
sometimes, because it's a separate env and running all envs takes too
long to do before push, so I only see it in CI.
additionally
Hi Florian,
On Wed, Mar 14, 2018 at 5:40 AM Florian Schulze
wrote:
> I'd like to propose moving pytest-pep8 from pytest-dev on Bitbucket to
> GitHub and my pytest-flakes from my GitHub repository to pytest-dev.
> Since I use both myself all the time, I would continue maintaining them.
>
Sounds
On Wed, Mar 14, 2018 at 5:07 AM, Florian Schulze
wrote:
> [...]
> How do you tackle that then? I like things which work on the commit level,
> so one can improve things incrementally. But most solutions I saw work as
> pre-commit hooks, which makes them harder to enforce especially for Open
> Sou