pySiesta
pySiesta provides a tool to work with siesta package within a Python script. You might find it most useful for tasks involving input generation. Typical usage often looks like this:
#!/usr/bin/env python
from pySiesta import location
from towelstuff import utils
if utils.has_towel():
print "Your towel is located:", location.where_is_my_towel()
(Note the double-colon and 4-space indent formatting above.)
Paragraphs are separated by blank lines. Italics, bold, and monospace look like this.
A Section
Lists look like this:
First
Second. Can be multiple lines but must be indented properly.
A Sub-Section
Numbered lists look like you’d expect:
hi there
must be going
Urls are http://like.this and links can be written like this.
Contributors
Is there any?
1 maintainer
Metadata
1 maintainer
Release files for pySiesta 0.2.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 | Actions |
|---|---|---|---|---|
| pySiesta-0.2.0.tar.gz | 34.0 kB | Without provenance | Details for pySiesta-0.2.0.tar.gz |
Release files / pySiesta-0.2.0.tar.gz
| Download URL | pySiesta-0.2.0.tar.gz |
|---|---|
| Size | 34.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
657ed610540fe78c1d408d2befba637cc88852579a0e306e8922ee3f776dd9d0
|
|
BLAKE2b-256 checksum How to use checksums |
0ed59e16eb5d77ae6a8154a07748c7ba96f9929fe416225f7eec4683757b4e67
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pySiesta 0.2.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
