Pycharm import RuntimeWarning after updating to 2016.2

Question

After updating to new version 2016.2, I am getting

RuntimeWarning: Parent module 'tests' not found while handling absolute import
  import unittest
RuntimeWarning: Parent module 'tests' not found while handling absolute import
  import datetime as dt

'tests' is a package inside my main app package, and I receive these warnings when I try to execute unit tests inside this folder. This issue only came up after updating to 2016.2. Besides the warnings, the remaining code works fine.

Edit: This is a known issue - https://youtrack.jetbrains.com/issue/PY-20171. They are suggesting to replace utrunner.py in PyCharm installation folder.

For now, I just copied the old utrunner.py into 2016.2 - ~/pycharm-2016.1/helpers/pycharm/utrunner.py — Sam Kenny, Jul 26 '16 at 20:39
Ok, I've found it here: http://code.metager.de/source/xref/jetbrains/intellij/community/python/helpers/pycharm/utrunner.py — mircealungu, Jul 30 '16 at 06:09
Can you share the ticket link please? (I'm having the same issue and wish to upvote it) — Guy, Aug 02 '16 at 11:56
Replaced the old file (/Applications/PyCharm.app/Contents/helpers/pycharm/utrunner.py) with the file for download from [youtrack.jetbrains.com](https://youtrack.jetbrains.com/issue/PY-20171) ([download link](https://youtrack.jetbrains.com/_persistent/utrunner.py?file=74-332199&c=true)). Works perfectly for me. — Jim Wright, Aug 03 '16 at 09:44
According to the issue thread, this will be fixed in 2017.1: https://youtrack.jetbrains.com/issue/PY-20171#comment=27-1821551 — steinar, Jan 04 '17 at 14:44

Bobby · Accepted Answer · 2017-03-06T20:01:04.350

65

This is a known issue introduced with the 2016.2 release. Progress can be followed on the JetBrains website here. According to this page it is due to be fixed in the 2017.1 release. You can follow the utrunner.py workaround that others have mentioned in the meantime - a copy of this file is attached to the linked ticket.

edited Mar 06 '17 at 20:01

answered Aug 02 '16 at 15:21

Bobby

797
6
10

7

Replaced the old file (/Applications/PyCharm.app/Contents/helpers/pycharm/utrunner.py) with the file for download from [youtrack.jetbrains.com](https://youtrack.jetbrains.com/issue/PY-20171) ([download link](https://youtrack.jetbrains.com/_persistent/utrunner.py?file=74-332199&c=true)). Works perfectly for me. – Jim Wright Aug 03 '16 at 09:47
There was a recent update the called 2016.2.2, which *did not* fix the issue yet... – Guy Sep 04 '16 at 05:26
18

This is still not fixed in pycharm-2016.2.3 – Ben Schmidt Sep 29 '16 at 13:49
9

This doesn't seem to be fixed in 2016.3, the same warning occurs. – Vadim Gremyachev Nov 25 '16 at 10:22
3

Doesn't appear to be fixed in 2016.3.1 – nevets1219 Dec 19 '16 at 20:15
4

Not fixed in 2016.3.2 – Michael Jan 05 '17 at 20:12
I just downloaded and implemented the workaround as per @Bobby 's instructions. Worked for me on Linux Debian Jessie running PyCharm 2016.3.2. NOTE: at the JetBrains url it states the bug is "obsolete" in PyCharm 2017.1. – MikeyE Mar 05 '17 at 10:50
How does this bug get released – RustyShackleford May 11 '17 at 17:43

score 36 · Answer 2 · answered Dec 28 '16 at 02:37

36

The latest recommendation (Dec. 19, 2016) is to put this line at the top of your unit test script:

from __future__ import absolute_import

answered Dec 28 '16 at 02:37

Brent Washburne

12,904
4
60
82

That fixes the problem for me, but I think it's not an official recommendation, as the user mentioning this doesn't seem to be a JetBrains dev. Since this warning turns up even if only doing absolute imports, wouldn't adding that line be an unnecessary piece of code which would need to be removed after their next release? – steinar Jan 04 '17 at 14:48
It will probably need to be removed at some point in the future, yes. For more information, see http://stackoverflow.com/q/7075082/584846 – Brent Washburne Jan 04 '17 at 20:45
Yeah, my point was that it's really unnecessary in this case, since this particular `__future__` import is only there for fixing a bug in PyCharm. The source code needs no fix, at least in my case. So it seems that following the advice in the accepted answer would be better, since then the source code doesn't need to be touched at all. – steinar Jan 05 '17 at 08:59
I am in favor of `from __future__ import absolute_import`. If your Python 2.7 code can take it, I prefer to use all the __future__ imports. It would simplify eventual move to Python 3.6. – user7610 Jan 11 '17 at 15:12
This is the only solution that worked for me. Downloading the other `utrunner.py` and replacing the original did not appear to work. Perhaps Pycharm was caching it; I didn't try restarting my machine. – Matthew Moisen Mar 01 '17 at 20:56

score 14 · Answer 3 · answered Jul 30 '16 at 06:21

14

On OS X I've fixed this by replacing

Applications/PyCharm.app/Contents/helpers/pycharm/utrunner.py

with an older version that can be found at http://code.metager.de/source/xref/jetbrains/intellij/community/python/helpers/pycharm/utrunner.py

answered Jul 30 '16 at 06:21

mircealungu

6,831
7
34
44

score 2 · Answer 4 · answered Nov 08 '16 at 14:30

2

On Ubuntu 16.04 Bobby's solution also works:

Just replace your local utrunner.py file at

/usr/local/pycharm-edu-3.0/helpers/pycharm/utrunner.py

by the one from the Jetbrains website: http://code.metager.de/source/xref/jetbrains/intellij/community/python/helpers/pycharm/utrunner.py

answered Nov 08 '16 at 14:30

petibonum

83
8

I found mine installed at a different place, however it worked after replacing it with above version -- why did they not rollback? will doing this not make python unstable?? – serup Dec 14 '16 at 10:40

score 0 · Answer 5 · answered Dec 04 '16 at 20:50

On Windows 10 Bobby's solution also works:

Just replace your local utrunner.py file at

C:\Program Files (x86)\JetBrains\PyCharm 2016.3\helpers\pycharm

with the one from the Jetbrains website: http://code.metager.de/source/xref/jetbrains/intellij/community/python/helpers/pycharm/utrunner.py

Pycharm import RuntimeWarning after updating to 2016.2

5 Answers5