Skip to content
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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Markers cannot be registered in setup.cfg #705

Closed
pytestbot opened this issue Mar 27, 2015 · 3 comments
Closed

Markers cannot be registered in setup.cfg #705

pytestbot opened this issue Mar 27, 2015 · 3 comments
Labels
type: bug problem that needs to be addressed

Comments

@pytestbot
Copy link
Contributor

Originally reported by: Daniel Hahler (BitBucket: blueyed, GitHub: blueyed)


I've tried registering a mark in setup.cfg, but it appears to be ignored.

Adding it to pytest.ini works, but I was under the impression, that setup.cfg should work in the same way - given a [pytest] section.

The following comment from Holger mentions this: #567/use-of-pytest-in-setupcfg-collides-with#comment-12111803


@pytestbot pytestbot added the type: bug problem that needs to be addressed label Jun 15, 2015
@flub
Copy link
Member

flub commented Jul 24, 2015

Hi, could you actually give a concrete example? Only one of setup.cfg, tox.ini, pytest.ini should have a [pytest] setting otherwise some will be ignored. Might this be happening here?

@RonnyPfannschmidt
Copy link
Member

@blueyed ping? since we didn't use the @ references you probably didn't notice here

@blueyed
Copy link
Contributor

blueyed commented Jul 25, 2015

The pytest.ini was / should have been empty (I like to use setup.cfg for everything), and there is no [pytest] section in tox.ini.

But I cannot reproduce it now on the 2.7 branch nor master.

Therefore I am closing this issue for now.

@blueyed blueyed closed this as completed Jul 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug problem that needs to be addressed
Projects
None yet
Development

No branches or pull requests

4 participants