path.common: handle FileNotFoundError when trying to import pathlib#207
Conversation
|
did this practically happen? |
|
Yes, with py34-xdist on Travis, see the original ref. |
|
Yikes, thanks |
3b86205 to
1a5f9b9
Compare
|
Rebased. |
|
Pushed a fixup. I also wonder if caching the ImportError wouldn't make sense?! |
|
Can you please check the travis failure @blueyed? |
|
I think it is related to pytest itself failing with the test. |
|
IIRC AppVeyor skips the test. |
427c7b6 to
820aa08
Compare
|
Any clues about the failures on Travis? |
|
Still the same as with #207 (comment) I guess. |
|
OK. Another option is to drop support for those old pytest versions. With the "importlib" option getting used in pytest, we will need to require a higher version of |
820aa08 to
74e8a71
Compare
74e8a71 to
d714f41
Compare
Python 3.4 might raise FileNotFoundError due to `os.getcwd()` failing on a non-existing cwd. This is fixed in Python 3.5. Ref: pytest-dev/pytest#4787 (comment)
Might not really be necessary, since py27 triggers the ImportError always already, but better to be safe.
d714f41 to
a64cb3f
Compare
|
Fixed the new test to cd back (using monkeypatch). |
Codecov Report
@@ Coverage Diff @@
## master #207 +/- ##
==========================================
+ Coverage 82.04% 82.07% +0.03%
==========================================
Files 55 55
Lines 10136 10153 +17
Branches 1141 1141
==========================================
+ Hits 8316 8333 +17
Misses 1556 1556
Partials 264 264 |
|
Please add a CHANGELOG then it is good to go I think |
|
Pushed with |
Python 3.4 might raise FileNotFoundError due to
os.getcwd()failing ona non-existing cwd. This is fixed in Python 3.5.
Ref: pytest-dev/pytest#4787 (comment)