This release is a pre-release and may not be stable for production use.
This zc.buildout recipe will check out a number of URLs into its parts directory. It won’t remove its parts directory if there are any changes in the checkout, so it’s safe to work with that checkout for development.
This is an example buildout part that uses this recipe:
[development-products]
recipe = infrae.subversion
urls =
https://svn.plone.org/svn/collective/PDBDebugMode/trunk PDBDebugMode
This will maintain a working copy of PDBDebugMode in the parts/development-products/PDBDebugMode directory (not in the parts directory itself). Thus, the recipe handles multiple URLs fine.
If you have pysvn installed on the computer, it will be use. This implies better performances.
Update
By default, when buildout update the part, an svn up is done for each link. However, when a revision number is specified like this:
https://svn.infrae.com/buildout/infrae.subversion/trunk@27829
The SVN link is skipped for update. If you want to prevent update for all SVN link of the part even if they do not contain revision number, you can add the following option:
ignore_updates = true
Export
With pysvn installed, you can specify:
export = true
in your buildout part to get an SVN export instead of an SVN checkout.
Sample
For an example buildout that uses this recipe, please see the Silva buildout.
As well, the doctest file can provide more sample.
Latest version
The latest version is available in a Subversion repository.
Metadata
Release files for infrae.subversion 1.0dev-r28201
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 |
|---|---|---|---|---|
| infrae.subversion-1.0dev-r28201.tar.gz | 7.3 kB | Without provenance | Details for infrae.subversion-1.0dev-r28201.tar.gz |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| infrae.subversion-1.0dev_r28201-py2.5.egg | Legacy Egg format | - | - | Details for infrae.subversion-1.0dev_r28201-py2.5.egg |
| infrae.subversion-1.0dev_r28201-py2.4.egg | Legacy Egg format | - | - | Details for infrae.subversion-1.0dev_r28201-py2.4.egg |
Total release size: 40.4 kB
Release files / infrae.subversion-1.0dev-r28201.tar.gz
| Download URL | infrae.subversion-1.0dev-r28201.tar.gz |
|---|---|
| Size | 7.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c63edbce67b57022f57ab3ec3e39b2a984d582ed8eb7b8e73f8b5bbc13aa5a77
|
|
BLAKE2b-256 checksum How to use checksums |
167878f11bbac25e34ba4dce346c4d0e9358413900ac87589040047a119dcd09
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / infrae.subversion-1.0dev_r28201-py2.5.egg
| Download URL | infrae.subversion-1.0dev_r28201-py2.5.egg |
|---|---|
| Size | 16.5 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
25ada00dd3127e2bc72967a17d8b0b633c156917bf074b3bc6e75e1348657e3d
|
|
BLAKE2b-256 checksum How to use checksums |
23a5b09e5116c6a5884a78cf9aaec74c6699c83986980bb734072ae49f719d4c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / infrae.subversion-1.0dev_r28201-py2.4.egg
| Download URL | infrae.subversion-1.0dev_r28201-py2.4.egg |
|---|---|
| Size | 16.6 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
5bcce331c9d89f4f08fab42ef686141edb7288b309e9031a1563e53204be528f
|
|
BLAKE2b-256 checksum How to use checksums |
91743143ac44e1972f9e8e832538ab644ef39b67650921e02e7642cab815dfe6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for infrae.subversion 1.0dev-r28201
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.