ejmg / tomaty

tomaty is a gtk+3 based application for the pomodoro technique 🍅
MIT License
6 stars 1 forks source link

No module - tomaty.lib.serialization #53

Closed karlramberg closed 6 years ago

karlramberg commented 6 years ago

I installed after lots of trial and error. Just include a more extensive dependency list (e.g. gcc, alsa, python3-devel). I just didn't want to make a seperate issue.

Not the main issue...

When running, it can't find the library for serialization.

Output

Traceback (most recent call last):
  File "/usr/bin/tomaty", line 11, in <module>
    load_entry_point('tomaty==1.0.0', 'console_scripts', 'tomaty')()
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 565, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2631, in load_entry_point
    return ep.load()
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2291, in load
    return self.resolve()
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2297, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python3.6/site-packages/tomaty/tomaty.py", line 23, in <module>
    from tomaty.lib.serialization import tomaty_serialization
ModuleNotFoundError: No module named 'tomaty.lib.serialization'
ejmg commented 6 years ago

Hey Karl, thanks for reporting this.

I edited your comment for you, but anything that is a lot of lines of code/logs you should wrap around with three back-ticks for readability. It helps anyone who has to read it.

As for the error, I've patched it as of bfd296f55b1c04b682eb74baa5f670128772b5f2. You can update to the proper version via pip install --no-cache-dir tomaty==1.0.1 if pip install --upgrade tomaty does not work.

Finally, as for those other dependencies you needed: honestly put, those are very basic dependencies that would be considered "redundant" to post. If you are doing any kind of real development on linux or mac, you will eventually need them. This just happens to be your first project that needed them! For future reference, whenever you need to do development with X tool/language, you will often need x-dev or x-dlib etcetera. The naming isn't constant, but you get the idea clearly from python3-dev.

Thanks for reporting the bug, unfortunately local testing can only do so much. I hadn't bothered to install the app again via pypi myself after pushing the major release. It was luckily just a dumb mistake.

Actual question: Did you do this on a n*x system or Windows?

karlramberg commented 6 years ago

Thanks! This worked.