Joey DiGiorgio added the comment:
Ok I have downloaded an installed via the Windows installer and the test I run
works as expected. I also tried the embedded package without the ._pth and it
also works according to the embedded documentation. Sorry for the confusion as
I did not specify
Joey DiGiorgio added the comment:
Steve Dower, I understand the purpose of the embedded package. The test was
also tried by calling the python executable without modifying the path and the
same thing happens.
i.e. %~dp0\Python_Embedded_Windows_32bit_v3.6.2\python main.py
in the zip package I
Joey DiGiorgio added the comment:
I run the test.bat file and get the import error.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Joey DiGiorgio added the comment:
I have tried from 3 computers now and have been able to reproduce the issue
with the same set of files described in my stackoverflow post. Here is a .zip
package with all of the files I used in all 3 tests. The python package is the
Windows 32bit embedded zip
Joey DiGiorgio added the comment:
I understand your comments. I will be at computer that has not ever had Python
installed in about an hour and will try it there to see if I can produce an
example showing the issue. I just found it weird that Python 3.5.2 worked just
fine in the same
Joey DiGiorgio added the comment:
I will mark the question appropriately as python3. I don't fully understand
your comment about venv. If you mean virtual environment or something, that is
not the case.
I am running an a standard Windows 7 install with Python3 as the only Python
install
New submission from Joey DiGiorgio:
I am running Windows 7 and Python 3.6.2 trying to import module A from withing
module B where both Module A and B are located in the same directory. I get the
ModuleNotFoundError. I try the exact same setup with Python 3.5.2 and get no
errors and I get
