por.models
for more details visit: http://getpenelope.github.com/
1.6 (2013-08-12)
make sure new tracs sets PM for CC notifications [amleczko]
refactor for penelope.core [amleczko]
1.5 (2013-04-30)
change post-commit hook [amleczko]
1.4 (2013-04-23)
fix SMTP problems with newly created tracs [amleczko]
1.3 (2013-04-16)
mandrill integration [amleczko]
1.2.1.1 (2013-04-04)
authz.ini patch [amleczko]
1.2.1 (2013-04-02)
add more verbose logging [amleczko]
fix problem with strange smtp configuration [amleczko]
fix trac reports and remove unsed fields [amleczko]
add SVN authz manage screen [amleczko]
1.2.0 (2013-02-18)
sets Backlog’s date to now+1year [massimoazzolini]
sets trac’s name and descr [massimoazzolini]
removes default trac’s milestones, components, versions [massimoazzolini]
fixes for project wizard [amleczko]
1.1.10 (2013-02-15)
fix problem with duplicated authz section [amleczko]
1.1.9 (2013-01-31)
fix cache keys for authz generation [amleczko]
normalize repository URI [amleczko]
1.1.8 (2013-01-30)
move to github [amleczko]
fixes for SVN integration [amleczko]
Backlog is the new default milestone for newly created tracks [amleczko]
Release files for por.trac 1.6
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 |
|---|---|---|---|---|
| por.trac-1.6.tar.gz | 10.7 kB | Without provenance | Details for por.trac-1.6.tar.gz |
Release files / por.trac-1.6.tar.gz
| Download URL | por.trac-1.6.tar.gz |
|---|---|
| Size | 10.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fd79b773301306fc0649baf81ec34b1c5c44919d2c2dfd41fabbcff3b845aa53
|
|
BLAKE2b-256 checksum How to use checksums |
de8156d5c8b03754c91e309a32dde4472c743b6460acdeba760545481472927b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for por.trac 1.6
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.
