py34-filelock: Error: No such port: py34-pytest

[ryandesign (Ryan Carsten Schmidt)]

​https://build.macports.org/builders/jobs-mirror/builds/331689/steps/mirror/logs/stdio

--->  Fetching distfiles for py34-filelock
Error: No such port: py34-pytest

[chrstphrchvz (Christopher Chavez)]

Almost 2 years ago, py34-pytest (in [248c039e69/macports-ports]) and py34-filelock (in [adbf220f8d/macports-ports]) were removed. A few months later, py34-filelock was restored in [ef26e7a10b/macports-ports] (with a comment requesting it be kept).

[cjones051073 (Chris Jones)]

There cannot exactly be that much interest in the py34 versions if no one has reported it until now...

We really should be looking to remove the older py34 subport versions at this point, not still adding them back.

[ryandesign (Ryan Carsten Schmidt)]

Removing py34 subports is fine, but removing ports that other ports depend on should be avoided.

[reneeotten (Renee Otten)]

Replying to cjones051073:

There cannot exactly be that much interest in the py34 versions if no one has reported it until now...

We really should be looking to remove the older py34 subport versions at this point, not still adding them back.

Agreed in general, but last time I attempted such exercise there was a discussion about this and the conclusion was that we should keep py-virtualenv for all Python versions. So, that's the reason that there are for its dependents still PY27/PY34 subports present with a note to keep them there. We should not change that; the fact that there is no py34-pytest is irrelevant to the functioning of the port unless you'd want to run the test-suite... so just don't do that ;)

Of course we can enable the test phase only for Python subports for which pytest is available; I will do so shortly. Other than that nothing has to be done about this.

[reneeotten (Renee Otten)]

In 6187c134fc4633c3300e6d3f04c8404244824c1a/macports-ports (master):

py-filelock: disable test phase for PY34 subport

Closes: #63975