Skip to content

Don't process shebangs in codehilite when processing fenced code #1166

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

Conversation

facelessuser
Copy link
Collaborator

Fixes #1156

@facelessuser
Copy link
Collaborator Author

Lint test can be ignored for now I guess. I have a fix for the failure in #1167. I'm unconcerned with caching and think having something not broken is more important in the short term than figuring out how to utilize npm caching correctly.

@facelessuser facelessuser force-pushed the bugfix/fenced_code_codehilite branch from 496032e to cc46681 Compare August 4, 2021 18:30
@facelessuser
Copy link
Collaborator Author

GitHub was having lagging response time, so checklinks failed after the rebasing on the tip. Re-ran tests once GitHub was more responsive and tests are now passing. require_changelog bot (or action) seems to be hanging, but changelog was updated 🤷🏻.

@waylan waylan merged commit e11cd25 into Python-Markdown:master Aug 4, 2021
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.

Don't eat "pathless shebang lines" that could be actual Rust code
2 participants