fix: renamed shebang to make the examples python3 compliant #110
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SpaciousCoder78
changed the title
LilSpazJoekp
approved these changes
Aug 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, I'm packaging this library into Debian so that people can install this as a dependency for asyncprawcore.
While packaging, I encountered an issue with the examples where the shebang
#!/usr/bin/env pythoninside these files usespythoninstead ofpython3which gave a warning about unusual interpreter.In general,
pythonusually refers to Python 2 where aspython3is the one that's used for modern python scripts and due topythonbeing mentioned, the interpreter was confused whether to use Python 2 or 3. This PR fixes that atleast on Linux side of things.I've patched this in the debian package hence I'm forwarding the changes to upstream.