This patch implements the source element for feed entries/items. Note
that only the set of RSS elements (URL and title) are implemented right
now. ATOM supports additional elements which cannot be set at the
moment.
This fixes#79
This patch renames the entries `pubdate` method to `pubDate` to be
consistent with the feed's method as well as the documentation. Note
that for now, the old method is preserved as well but is marked as
deprecated and to be removed.
This fixes#71
RSS does not require an author's name, but only his email address. This
patch makes the name optional for RSS. Note that the name is required in
ATOM feeds and an author will not be included if the name is missing.
This fixes#59
The `isPermalink` attribute can now be set using the `guid()` function
for entries. Note that this only effects RSS feeds. This patch does not
change Atom feeds in any way.
This fixes#60
This patch extends the test coverage of the unit tests. It also enables
python-coverage and coveralls to track unit test coverage.
There are some additional minor issue fixed discovered during the test
creation.
Signed-off-by: Lars Kiesow <lkiesow@uos.de>
This patch makes the feedgen flake8 compatible, fixing some minor issues
along the way. Most noticeable, this switches from tabs to spaces.
Signed-off-by: Lars Kiesow <lkiesow@uos.de>
According to RFC 4287, there is no atom:url element, only atom:uri, so
replace occurrences of atom:url with atom:uri for compliance.
Also rename variables holding atom:uri from email to uri to better
indicate what they actually are.
This fixes some minor problems with the pull request from jvanasco so
that it may be included into the next release:
- Only one extension registry is used internally and custom extensions
do not have to be stored two times.
- Fix the bug that entry extensions were loaded for feeds.
- Do not fail if there is only a feed extension.
- Extensions for entries do not need a feed extension class.
Signed-off-by: Lars Kiesow <lkiesow@uos.de>
Now the content element now supports the type attribute and the content
is encoded accordingly:
- text and html are escaped
- xhtml is surrounded with a div and then included as XML
- XML is directly included
- base64 support was *not* added. Please file a bug if you need it