Config._checkversion checks installed pytest version

[pytestbot]

Originally reported by: Matt Davis (BitBucket: jiffyclub, GitHub: jiffyclub)

---

When setting minversion = X.X in a setup.cfg or similar the version checking does an absolute import of pytest and checks the version of that module.

With this being the case I can bundle py.test 2.2 with my package (using the --genscript file) and explicitly use that for running my tests, but if I have py.test 2.1 installed elsewhere on my system so that import pytest imports py.test 2.1, it will still fail the minversion test.

It would be preferable for Config._checkversion to check the version of py.test that is actually running, and not the version returned by import pytest.

---

• Bitbucket: https://bitbucket.org/pytest-dev/pytest/issue/98

[pytestbot]

Original comment by Ronny Pfannschmidt (BitBucket: RonnyPfannschmidt, GitHub: RonnyPfannschmidt):

---

sounds like a different kind of bug, after a genscript-based pytest is loaded,
there shouldn’t be a way to import a system one the normal way,
figuring the exact semantic issue with pythons import system will be a bit troublesome

[pytestbot]

Original comment by Ronny Pfannschmidt (BitBucket: RonnyPfannschmidt, GitHub: RonnyPfannschmidt):

---

ok, after a bit of code-skimming, i think there is need to do a deeper review of pylib/pytest wrt use of apipkg and the genscript entrypoint,

[pytestbot]

Original comment by Matt Davis (BitBucket: jiffyclub, GitHub: jiffyclub):

---

I've been playing around with this a bit more and the problem actually appears to be caused by our usage. When I isolate the genscript the minversion check does work as it should. Sorry for the false alarm.