New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch `for_parameterize` to `for_parametrize` #3166

Merged
merged 3 commits into from Jan 30, 2018

Conversation

Projects
None yet
3 participants
@alanbato
Member

alanbato commented Jan 30, 2018

From the authors that brought you the controversial #3159...

Change the naming of for_parameterize to for_parametrize in order to comply with the current convention on naming. This should make the whole codebase as of now have the parametrize spelling.
馃悕

Now in theaters close to your location

alanbato added some commits Jan 30, 2018

@coveralls

This comment has been minimized.

coveralls commented Jan 30, 2018

Coverage Status

Coverage remained the same at 92.628% when pulling ef7df8f on alanbato:typo_for_parametrize into f2fb841 on pytest-dev:master.

@nicoddemus

This comment has been minimized.

Member

nicoddemus commented Jan 30, 2018

Thanks! 馃榿

@nicoddemus nicoddemus merged commit 89a55d8 into pytest-dev:master Jan 30, 2018

0 of 2 checks passed

continuous-integration/appveyor/pr Waiting for AppVeyor build to complete
Details
continuous-integration/travis-ci/pr The Travis CI build is in progress
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment