Supported options
This recipe supports the following options:
- url
URL pointing to the stud compressed archive. By default it uses: https://github.com/bumptech/stud/tarball/master
- target
Target can be one of the following: linux22, linux24, linux24e linux24eold, linux26, solaris, freebsd, openbsd, generic.
- cpu
CPU can be one of the following: i686, i586, ultrasparc, generic.
Example usage
To use this recipe, just create a part for it and define the recipe parameter:
[buildout]
parts =
...
stud
[stud]
recipe = fourdigits.recipe.stud
This will configure the default options for url, target, cpu and livevversion. If you like or need to you can override these parameters, e.g.:
[haproxy] recipe = foudigits.recipe.stud url = https://github.com/bumptech/stud/tarball/master target = linux26 cpu = i686 libevversion = 4.04
Reporting bugs or asking questions
Code repository
Contributors
Franklin Kingma, Author [kingel]
Roel Bruggink, Additional help
Releases
1.0.5 (2011-02-06)
libev configurable via libevversion in buildout [kingel]
1.0.3 (2011-02-06)
Updated libev version. [kingel]
1.0.2 (2011-01-12)
Fix broken egg. [kingel]
1.0.1 (2011-01-12)
Fix broken egg. [kingel]
1.0 (2011-01-12)
First release. [kingel]
Metadata
Release files for fourdigits.recipe.stud 1.0.5
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 | |
|---|---|---|---|---|
| fourdigits.recipe.stud-1.0.5.tar.gz | 5.9 kB | Without provenance | Details |
Release files / fourdigits.recipe.stud-1.0.5.tar.gz
| Download URL | fourdigits.recipe.stud-1.0.5.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d41368ab51f41a7da77614d4522ad083b8ef5f366de69284f66a604267f844c4
|
|
BLAKE2b-256 checksum How to use checksums |
0325bd74cd9380d5da7c4ce2e92e84e035dc14550f631e786bedc9d05a7874f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for fourdigits.recipe.stud 1.0.5
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.