PyEmbed-Rst
Python reStructuredText directive for embedding content using OEmbed.
PyEmbed-Rst allows you to embed content in your reStructuredText websites and documents from a wide range of producers. You don’t need to configure anything - the extension automatically discovers how to embed content.
Usage
Initialize the directive like this:
PyEmbedRst().register()
You can then embed content by entering a link with the special text .. embed::, like this:
.. embed:: http://www.youtube.com/watch?v=9bZkp7q19f0
This will be turned into the following HTML:
<iframe width="480" height="270" src="http://www.youtube.com/embed/9bZkp7q19f0?feature=oembed" frameborder="0" allowfullscreen></iframe>
For more information, see the PyEmbed website.
Compatibility
PyEmbed-Rst has been tested with Python 2.7, 3.3 and 3.4.
Installation
PyEmbed-Rst can be installed using pip:
pip install pyembed-rst
Contributing
To report an issue, request an enhancement, or contribute a patch, go to the PyEmbed-Rst GitHub page.
License
PyEmbed-Rst is distributed under the MIT license.
Copyright (c) 2013 Matt Thomson Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Changes
v1.1.0, 2014-08-02
Upgrade to PyEmbed v1.1.0.
v1.0.0, 2014-02-05
Initial stable release
v0.7.0, 2014-02-02
Initial release
Metadata
Release files for pyembed-rst 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pyembed-rst-1.1.0.tar.gz | 4.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyembed_rst-1.1.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 12.4 kB
Release files / pyembed-rst-1.1.0.tar.gz
| Download URL | pyembed-rst-1.1.0.tar.gz |
|---|---|
| Size | 4.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
53702b4af9d497f734699f8bbdcca6d3ba476fabf82074d54a8d7e83ff248afc
|
|
BLAKE2b-256 checksum How to use checksums |
13b85239d7db969059848851ed55b34ca023e534cb25ad3650bb165a64f2ff3e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / pyembed_rst-1.1.0-py2.py3-none-any.whl
| Download URL | pyembed_rst-1.1.0-py2.py3-none-any.whl |
|---|---|
| Size | 8.3 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
6ddafdd25cf7a3c9d68abcc3a70b3b258194070441fbf87e1a7857d47b8e49e2
|
|
BLAKE2b-256 checksum How to use checksums |
d83ccdcd5094f767d14a26421f066c441dce08e387fd271be3c526a719561e01
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pyembed-rst 1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.