Skip to content
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

Atom: Populate <summary> correctly if it comes after <content> #260

Merged
merged 2 commits into from
May 21, 2022
Merged

Atom: Populate <summary> correctly if it comes after <content> #260

merged 2 commits into from
May 21, 2022

Conversation

cristoper
Copy link
Contributor

@cristoper cristoper commented Jan 26, 2021

This fixes #59. It is merely a rebase (with some variable renaming) of @mosasiru's original pull request (PR #60) which was never merged for some reason so that it doesn't conflict with the current develop branch.

yusuke-enomoto and others added 2 commits January 25, 2021 22:19
If <summary> follows <content>, it should not be overwritten. (This is
apparently a regression introduced way back in b06df76)
feedparser/mixin.py Show resolved Hide resolved
@kurtmckee kurtmckee self-assigned this May 21, 2022
@kurtmckee kurtmckee merged commit 68ce246 into kurtmckee:develop May 21, 2022
@kurtmckee
Copy link
Owner

This is released as feedparser 6.0.10. Thanks for your work on this!

cristoper added a commit to cristoper/feedmixer that referenced this pull request May 12, 2023
Most notably we can now use upstream feedparser since issue 59 was fixed
in feedparser 6.0.10:
kurtmckee/feedparser#260
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.

feedparser depends on order of description and content
3 participants