Thanks to visit codestin.com
Credit goes to github.com

Skip to content

DEVELOPER_MODE=1 needs to be set manually, fixes #22 #30

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

Merged
merged 2 commits into from
Oct 9, 2020

Conversation

ThomasWaldmann
Copy link
Collaborator

the automatic way caused lots of troubles:

  • broke travis
  • often broke tests with specific python versions or OSes

By default, we just want to compile it as long as there is nothing
serious enough to really break a compiler run.

DEVELOPER_MODE=1 can be used on the dev machine to enable more warnings
and to be way more strict.

the automatic way caused lots of troubles:
- broke travis
- often broke tests with specific python versions or OSes

By default, we just want to compile it as long as there is nothing
serious enough to really break a compiler run.

DEVELOPER_MODE=1 can be used on the dev machine to enable more warnings
and to be way more strict.
@ThomasWaldmann
Copy link
Collaborator Author

this also fixes #27 (the "aborting" part of that).

it does not fix that the code uses deprecated functions, but hopefully they will only go away in python 3.10+.

@ThomasWaldmann ThomasWaldmann merged commit 74ed4a5 into python-llfuse:master Oct 9, 2020
@ThomasWaldmann ThomasWaldmann deleted the dev-mode-opt-in branch October 9, 2020 22:51
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 this pull request may close these issues.

1 participant