Bug 202884
| Summary: | devel/py-pytest: py34-pytest-2.7.1 conflicts with py27-pytest-2.7.1 Problematic file: /usr/local/bin/py.test | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Jan Beich <jbeich> | ||||
| Component: | Individual Port(s) | Assignee: | Walter Schwarzenfeld <w.schwarzenfeld> | ||||
| Status: | Closed Overcome By Events | ||||||
| Severity: | Affects Only Me | CC: | w.schwarzenfeld | ||||
| Priority: | --- | Keywords: | easy, patch | ||||
| Version: | Latest | Flags: | bugzilla:
maintainer-feedback?
(python) |
||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
Seems solved, please close this. Tested it. It is no more a problem. Agree. Probably obsoleted by USE_PYTHON=concurrent added in ports r409652. |
Created attachment 160692 [details] v0 Testing a new py- port against both 2.x and 3.x python is common routine. Let's keep it easy for py-test consumers without install/uninstall dance or resource hog like poudriere.