Entry points for Robot Framework
Robot framework does not have setuptools compatible entry points. This makes it hard to setup Robot with buildout.
robotentrypoints provides them.
With the buildout hereunder, you get bin/pybot and bin/rebot scripts.
[buildout] parts = robot [robot] recipe = zc.recipe.egg eggs = robotentrypoints
Changelog
0.1 (2012-05-17)
First release.
Metadata
Release files for robotentrypoints 0.1
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 | Actions |
|---|---|---|---|---|
| robotentrypoints-0.1.tar.gz | 5.8 kB | Without provenance | Details for robotentrypoints-0.1.tar.gz |
Release files / robotentrypoints-0.1.tar.gz
| Download URL | robotentrypoints-0.1.tar.gz |
|---|---|
| Size | 5.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b7551ad130b66391db12a248e6ba287bbe7951450a6d3955a7a3a8ac49ce8755
|
|
BLAKE2b-256 checksum How to use checksums |
5534a1f7ea561b1f891e63991b7a48179baec1d62c59bea4201e61bfa6fb0a47
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for robotentrypoints 0.1
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.