On 2 Feb 2018, at 10:22, Ronny Pfannschmidt wrote:
for eternal old api's i would like to introduce a warning which is per
default filtered (like a future-warning), simply so plugin authors can
have
a advised way of keeping up with core even if we keep some old things
in
place for users
Hidd
On Fri, Feb 2, 2018 at 7:22 AM Ronny Pfannschmidt
wrote:
> HI,
>
> i also like apply_params, it well in place with my desire of a more
> complete rename instead of just cutting it short.
>
> +1
>
> for eternal old api's i would like to introduce a warning which is per
> default filtered (like a f
HI,
i also like apply_params, it well in place with my desire of a more
complete rename instead of just cutting it short.
+1
for eternal old api's i would like to introduce a warning which is per
default filtered (like a future-warning), simply so plugin authors can have
a advised way of keeping
On Tue, Jan 30, 2018 at 22:22 -0800, Floris Bruynooghe wrote:
> holger krekel writes:
>
> > On Mon, Jan 29, 2018 at 19:08 -0800, Floris Bruynooghe wrote:
> >> Bruno Oliveira writes:
> >> > A PR[1] has been submitted which adds `parameterize` as an alias to
> >> > `parametrize`. Florian Bruhin an
Hello all,
I kinda feel bad that this has turned into kind-of an ordeal.
Or at least it seems like it has.
I'm rather rooting for the "params" version, and agree with Floris that
"parametrize" should be supported for eternity.
This is not something urgent, of course.
One option is to implement t
holger krekel writes:
> On Mon, Jan 29, 2018 at 19:08 -0800, Floris Bruynooghe wrote:
>> Bruno Oliveira writes:
>> > A PR[1] has been submitted which adds `parameterize` as an alias to
>> > `parametrize`. Florian Bruhin and I are not very keen to the idea given
>> > that there is an explicit war
On Mon, Jan 29, 2018 at 19:08 -0800, Floris Bruynooghe wrote:
> Bruno Oliveira writes:
> > A PR[1] has been submitted which adds `parameterize` as an alias to
> > `parametrize`. Florian Bruhin and I are not very keen to the idea given
> > that there is an explicit warning for it already and having
* Ronny Pfannschmidt [180130 08:05 +0100]:
> the alt_spellings is actually a list of wrong spellings that triggers
> errors - the reason being that the word as different spellings in
> british and american English
The whole list is, yes -- in the case of that PR, it's making an alias
for two Amer
the alt_spellings is actually a list of wrong spellings that triggers
errors - the reason being that the word as different spellings in british
and american English
if we actually change the word i would like to see something completely
different, not just some short-cutting
-- Ronny
2018-01-30
* Floris Bruynooghe [180129 19:08 -0800]:
> However the serious note in that plugin is that I think it makes sense
> to use ``params``. My reasoning is that it's easy to spell and
> already used for fixtures: ``@pytest.fixture(params=[0, 1])``. So
> why not everywhere else: ``@pytest.mark.param
Hi,
Bruno Oliveira writes:
> A PR[1] has been submitted which adds `parameterize` as an alias to
> `parametrize`. Florian Bruhin and I are not very keen to the idea given
> that there is an explicit warning for it already and having different names
> to the same thing reduces consistency across t
Hi all,
A PR[1] has been submitted which adds `parameterize` as an alias to
`parametrize`. Florian Bruhin and I are not very keen to the idea given
that there is an explicit warning for it already and having different names
to the same thing reduces consistency across test suites.
I'm sending an
12 matches
Mail list logo
