python3 setuptools is not package error

Question

I have a package with the following directory structure:

mypackage
   mypackage
      __init.py__
      users.py
   bin
      mypackage.py
   setup.py

My setup.py looks like this:

from setuptools import setup, find_packages

setup(
    name='mypackage.py',
    version='0.9',
    packages=find_packages(),
    scripts=['bin/mypackage.py'],
    install_requires=['np', 'filelock', 'python-dateutil', 'requests', 'numpy'])

The __init__.py contains:

import mypackage.users

My bin/mypackage.py includes among other things:

from mypackage.users import *

I am running

python3 setup.py install

Everything works great and then on the terminal I type:

mypackage.py

and I am greeted with the following error:

    from mypackage.users import *
ImportError: No module named 'mypackage.users'; 'mypackage' is not a package

If I attempt:

python3
import mypackage

I get no errors. I also use virtualenv (not shown here) but I am sure there are no other conflicts.

Does it work if you do name='mypackage' without the tailing .py? Probably would need to uninstall and reinstall to test. — scnerd
– scnerd, Commented Apr 20, 2018 at 21:07
Also, recommend using pip install -e ., but I don't think that would change anything in this case — scnerd
– scnerd, Commented Apr 20, 2018 at 21:08
Changing the name made no difference. pip install -e . is indeed much better but still no effect. It does uninstall and reinstall the module though successfully. — Michael
– Michael, Commented Apr 20, 2018 at 21:19
I added some additional info about the fact that through interactive pyhton I can import the package. It is only through my script that I cannot — Michael
– Michael, Commented Apr 20, 2018 at 21:22
Alright I managed to figure out what was happening. The script name was the same like the module name and that confused things. When renamed the script name to mypackagecli.py it resolves this issue. However, I have a follow up issue, when testing the tool, the command line tool won't find the mypackage.users unless it is already installed. But If I am programming, how can I quickly test changes on the code without having to install everytime? — Michael
– Michael, Commented Apr 20, 2018 at 21:37

Michael · Accepted Answer · 2018-04-20 21:40:13Z

7

Long story short, executable script cannot have the same name like the package. Lost 3 hours of my life.

answered Apr 20, 2018 at 21:40

Michael

1,8595 gold badges22 silver badges31 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

python3 setuptools is not package error

1 Answer 1

Comments

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Related