-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
discover should ignore build/ and dist/ by default #1544
Labels
good first issue
easy issue that is friendly to new contributor
status: help wanted
developers would like help from experts on this topic
type: enhancement
new feature or API change, should be merged into features branch
type: feature-branch
new feature or API change, should be merged into features branch
type: proposal
proposal for a new feature, often to gather opinions or design the API around the new feature
Comments
RonnyPfannschmidt
added
type: enhancement
new feature or API change, should be merged into features branch
status: help wanted
developers would like help from experts on this topic
type: proposal
proposal for a new feature, often to gather opinions or design the API around the new feature
good first issue
easy issue that is friendly to new contributor
type: feature-branch
new feature or API change, should be merged into features branch
labels
May 2, 2016
This was referenced Aug 24, 2016
This was referenced Aug 31, 2016
This was referenced Nov 15, 2017
Merged
This was referenced Nov 22, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
good first issue
easy issue that is friendly to new contributor
status: help wanted
developers would like help from experts on this topic
type: enhancement
new feature or API change, should be merged into features branch
type: feature-branch
new feature or API change, should be merged into features branch
type: proposal
proposal for a new feature, often to gather opinions or design the API around the new feature
If running
py.test
from same folder assetup.py
then test discovery may enterbuild/
causing errors. Removing thebuild/
directory, using--ignore=build
and settingnorecursedirs
for[pytest]
in any.ini
file all solve the issue, but canpy.test
be configured to always ignore this folder? Notenose2
andnosetests
do not have this issue.In the case where dynamic module import occurs and the path is specified relative to the test directory, then
py.test
returns the following stacktrace:minimalist example
my_package -> tests -> test_this.py
OS and Python
py.test --version
This is pytest version 2.9.1, imported from c:\python27\lib\site-packages\pytest.pyc
requirements.txt
Thanks for submitting an issue!
Here's a quick checklist in what to include:
pip list
of the virtual environment you are usingThe text was updated successfully, but these errors were encountered: