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
Many tutorials and walkthroughs exist for Sherlock, and they all use the old not-really-installed "install" method. With this, after the transition to a proper installable package, many users have opened bug reports relating to failed imports, when following these now outdated guides.
One of two things should happen to alleviate this --
Choose at runtime between proper module imports and relative script imports
Test at runtime if Sherlock is being ran as a package or as a script, and display a more informative error message if as a script
The former is more "friendly" in that it allows for old-style use, but the latter is more "proper" in my mind and more assertive in its use as a package. I lean towards the latter.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Description
Many tutorials and walkthroughs exist for Sherlock, and they all use the old not-really-installed "install" method. With this, after the transition to a proper installable package, many users have opened bug reports relating to failed imports, when following these now outdated guides.
One of two things should happen to alleviate this --
The former is more "friendly" in that it allows for old-style use, but the latter is more "proper" in my mind and more assertive in its use as a package. I lean towards the latter.
Code of Conduct
The text was updated successfully, but these errors were encountered: