This directory contains the source code for prcs2hg, which is a command to convert a PRCS project to Mercurial. It can help you publish the revision history of an obsolete project.
prcs2hg is free software: you can redistribute it and/or modify it under the conditions specified in each file. The main part of prcs2hg is licensed with the OSI-approved MIT License <http://opensource.org/licenses/MIT>.
For more information about prcs2hg, visit the prcs2hg project at <http://www.vx68k.org/prcs2hg>.
# Installation
You should be able to install prcs2hg by using the included ‘setup.py’ script as typical Python package.
# Third-party components
The file ‘prcs/sexpdata.py’ was copied from the sexpdata package <https://github.com/tkf/sexpdata> and modified not to parse numbers so that we can handle PRCS version numbers correctly.
1 maintainer
Metadata
1 maintainer
Release files for prcs2hg 1.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 | |
|---|---|---|---|---|
| prcs2hg-1.1.tar.gz | 10.0 kB | Without provenance | Details |
Release files / prcs2hg-1.1.tar.gz
| Download URL | prcs2hg-1.1.tar.gz |
|---|---|
| Size | 10.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1c6a11a2d9e2b0541fde59ef64af09d431d68dd24db76b64e993df2fb3da996a
|
|
BLAKE2b-256 checksum How to use checksums |
b67315805e9f5006d8368e59ac61c62b318b9ac1b012e33861bc81d4c2f2a1b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for prcs2hg 1.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.
