
Security News
npm Adopts OIDC for Trusted Publishing in CI/CD Workflows
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
sphinxfeed
package.. image:: https://img.shields.io/github/actions/workflow/status/lsaffre/sphinxfeed/build.yml :alt: Build status :target: https://github.com/lsaffre/sphinxfeed/actions .. image:: https://img.shields.io/pypi/v/sphinxfeed-lsaffre?color=blue :alt: PyPI - package version :target: https://pypi.org/project/sphinxfeed-lsaffre .. image:: https://img.shields.io/pypi/pyversions/sphinxfeed-lsaffre :alt: PyPI - supported python versions :target: https://pypi.org/project/sphinxfeed-lsaffre
This Sphinx extension is a fork of Fergus Doyle's sphinxfeed package <https://github.com/junkafarian/sphinxfeed>
__ which itself is derived from Dan
Mackinlay's sphinxcontrib.feed <http://bitbucket.org/birkenfeld/sphinx-contrib/src/tip/feed/>
_ package. It
relies on Lars Kiesow's python-feedgen <https://feedgen.kiesow.be>
__ package
instead of the defunct feedformatter <https://code.google.com/archive/p/feedformatter/>
_ package or of Django utils to
generate the feed.
Support Python 3 (by using feedgen instead of feedformatter).
Don't publish items having a publication datetime in the future.
Ability to write
ATOM <https://validator.w3.org/feed/docs/atom.html>
__ instead of RSS.
Detect category
and tags
fields in the page metadata <https://www.sphinx-doc.org/en/master/usage/restructuredtext/field-lists.html>
__
and if either or both is present, call the feedgen.FeedEntry.category()
method to add <category>
elements to the feed item. The difference
between category
and tags
is that the category
of a blog post may
contain whitespace while the tags
metadata field is a space-separated list
of tags, so each tag must be a single word. Both the category and each tag
will become a <category>
element in the feed item.
Additional Sphinx config variables:
feed_field_name
to change the name of the
metadata field to use for specifying the publication date.
use_dirhtml
to specify whether dirhtml
instead of html
builder is
used when calculating the url
feed_entry_permalink
to set a permalink GUID for each feed entry
feed_use_atom
to generate an Atom feed instead of RSS
You can install it using pip::
pip install sphinxfeed-lsaffre
How to test whether the right version of sphinxfeed is installed:
import sphinxfeed sphinxfeed.version '0.3.1'
#. Add sphinxfeed
to the list of extensions in your conf.py
::
extensions = [..., 'sphinxfeed']
#. Customise the necessary configuration options to correctly generate the feed::
feed_base_url = 'https://YOUR_HOST_URL'
feed_author = 'YOUR NAME'
feed_description = "A longer description"
# optional options
feed_field_name = 'date' # default value is "Publish Date"
feed_use_atom = False
use_dirhtml = False
#. Optionally use the following metadata fields:
#. Sphinxfeed will include only .rst
files that have a :date:
field with a
date that does not lie in the future.
See also the files LICENSE
and CHANGELOG.rst
.
Install a developer version::
git clone https://github.com/lsaffre/sphinxfeed.git pip install -e ".[dev]"
Run the test suite::
$ pytest
Generate an HTML test coverage report::
$ pytest --cov-report=html $ python -m webbrowser test-reports/index.html
Release a new version to PyPI::
$ hatch version micro $ git commit -m "release to pypi" $ git tag v$(hatch version) $ git push --tags
See Hatch Versioning <https://hatch.pypa.io/1.8/version/>
. and Publishing to PyPI with a Trusted Publisher <https://docs.pypi.org/trusted-publishers/>
.
Manually release to PyPI using your machine and token::
$ hatch build $ twine check --strict dist/* $ twine upload dist/*
The twine upload
step requires authentication credentials in your
~/.pypirc
file.
FAQs
Sphinx extension for generating RSS feeds
We found that sphinxfeed-lsaffre demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.