You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some people are worried to see "broken" packages that are actually just fine when they run eopkg check
This is for example the case of all the python packages for which the interpreter compiles the source to bytecode.
I don't think you'll really like it, but what about implementing a hack in sol to ignore the sha256sum of some file types like the .pyc and .pyo, especially if their parent directory is __pycache__ ?
Of course there should be an option to ignore this hack; something like sol check --force-check-all
The text was updated successfully, but these errors were encountered:
Some people are worried to see "broken" packages that are actually just fine when they run
eopkg check
This is for example the case of all the python packages for which the interpreter compiles the source to bytecode.
I don't think you'll really like it, but what about implementing a hack in sol to ignore the sha256sum of some file types like the
.pyc
and.pyo
, especially if their parent directory is__pycache__
?Of course there should be an option to ignore this hack; something like
sol check --force-check-all
The text was updated successfully, but these errors were encountered: