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

Avoid installing tests as a package #60

wants to merge 1 commit into
base: master


None yet
2 participants

Kwpolska commented Jul 16, 2018

What the title says. Without this, any Hatch-maintained package (including Hatch itself) would, in addition to installing the package code, litter the site-packages directory with a tests package, which could potentially conflict with other packages.


This comment has been minimized.

winni2k commented Jul 16, 2018

This I think is great. However, as a hatch user, what would the workflow be for testing a package on a CI service? Would I need to clone a git repo for that? What if I wanted to test the package "in isolation", that is without the git repo around. I suppose I would have to create a separate tests package and install it together with my main package in the testing environment?


This comment has been minimized.

Kwpolska commented Jul 16, 2018

  1. You can git clone and delete the main package after installing/move the tests away.
  2. Some people install the test suite as hatch.tests (although IMO that’s a waste of disk space, as no end user will actually bother to run it).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment