This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author brett.cannon
Recipients MrJman006, brett.cannon, paul.moore, steve.dower, tim.golden, zach.ware
Date 2017-07-28.17:49:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1501264142.42.0.29299575353.issue31056@psf.upfronthosting.co.za>
In-reply-to
Content
I also can't reproduce on Python 3.6 on Windows 10, so I'm closing this.

Looking at your SO question I noticed you didn't specify `python3` but `python` which suggests a venv, so I'm wondering if that's mucking with things? You also don't need to add __init__.py as long as you're executing within the directory (which it seems you are based on how you explained things). Basically you should be able to print out sys.path and see if the directory containing your code is listed there. If it isn't then something wonky is going on with your environment.

But if you are executing the code from outside the directory then do realize that Python 3 no longer supports implicit relative imports so module_a won't be picked up in a package context (that would require `from . import module_a`).
History
Date User Action Args
2017-07-28 17:49:02brett.cannonsetrecipients: + brett.cannon, paul.moore, tim.golden, zach.ware, steve.dower, MrJman006
2017-07-28 17:49:02brett.cannonsetmessageid: <1501264142.42.0.29299575353.issue31056@psf.upfronthosting.co.za>
2017-07-28 17:49:02brett.cannonlinkissue31056 messages
2017-07-28 17:49:02brett.cannoncreate