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

Python 3.7 #65

Open
Aliervo opened this issue Aug 10, 2018 · 3 comments
Open

Python 3.7 #65

Aliervo opened this issue Aug 10, 2018 · 3 comments

Comments

@Aliervo
Copy link

Aliervo commented Aug 10, 2018

Python 3.7 was released a couple weeks ago and in my testing thus far, lcurse has not broken. All that is needed is to change the 3.6 to a 3.7 in the Pipfile. I will continue to watch for issues, but I was wondering if this will be officially making the version jump.

@ephraim
Copy link
Owner

ephraim commented Aug 10, 2018

Thank you for testing this.
Will change it to 3.7 with a version jump.

@Zerqz
Copy link

Zerqz commented Aug 11, 2018

After updating to python 3.7 on Arch I get the following error:

Traceback (most recent call last): File "/usr/bin/lcurse", line 16, in <module> from modules import defines ModuleNotFoundError: No module named 'modules'

@ephraim
Copy link
Owner

ephraim commented Aug 11, 2018

is /usr/bin/lcurse a link or a copy? lcurse is expecting a folder "modules" next to it which in case of a copy you most likely don't have.
Cheers,
ephraim

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

No branches or pull requests

3 participants