Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ModuleNotFoundError: No module named 'validate' #419

Closed
aleprovencio opened this issue Dec 21, 2020 · 6 comments · Fixed by #434
Closed

ModuleNotFoundError: No module named 'validate' #419

aleprovencio opened this issue Dec 21, 2020 · 6 comments · Fixed by #434

Comments

@aleprovencio
Copy link

aleprovencio commented Dec 21, 2020

Hello,

I started getting this error after updating python-configobj from 5.0.6-9 to 5.0.6-10 on Arch. I've noticed it has changed its installation directory so I guess todoman should import from configobj.validate instead.

@alpaca1thunder
Copy link

Having the same issue here, Arch as well.

martinmake added a commit to martinmake/todoman that referenced this issue Dec 22, 2020
@polyzen
Copy link

polyzen commented Dec 24, 2020

A fix has been applied to the Arch package:
archlinux/svntogit-community@2cefd39

@WhyNotHugo
Copy link
Member

ArchLinux is currently packaging an unreleased 5.1.0 version.

$ python -c "import configobj; print(configobj.__version__)"
5.1.0

$ pacman -Qi python-configobj
Name : python-configobj
Version : 5.0.6-10
...

I can't fix this in todoman, since I can't really support something that's unreleased. It does seem that configobj's next minor release will have breaking changes though, so I'll keep this open to keep an eye on that.

@polyzen
Copy link

polyzen commented Dec 24, 2020

This seems like the best solution to deal with distro's that don't package the shim:
https://github.com/scheibler/khard/pull/283/files

@WhyNotHugo
Copy link
Member

There's nothing I can do to fix this; this will probably be addressed via #426.

@WhyNotHugo
Copy link
Member

This is fixed in main and will be released with 4.0.0.

The configuration format has changed, so that requires some (minor) manual attention.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants