flit6
Cross-compat flit install. Flit doesn’t support Python 2 at all, but authors of cross-compat libs might still want to use flit’s packaging for the simplicity. After pip install flit6 you can use flit install on Python 2 in your CI, with flit whatever else working as usual on Python 3.
I did not port any of flit itself. This project merely subprocesses a Python 3 build of your distribution, and then installs the generated release in the Python 2 environment. That requires flit to exist in the python3 runtime, for build.
dev
Clone the repo and then:
$ pip install pytest pytest-mock
$ pytest
To generate a release, use python setup.py bdist_wheel --universal. Upload with twine.
Metadata
Release files for flit6 0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| flit6-0.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for flit6-0.1-py2.py3-none-any.whl |
Release files / flit6-0.1-py2.py3-none-any.whl
| Download URL | flit6-0.1-py2.py3-none-any.whl |
|---|---|
| Size | 2.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
b5f5d435dcba1955dbc210f0c460d80b6e1b178edbb58efdbcec0f11a6c418bd
|
|
BLAKE2b-256 checksum How to use checksums |
fc0204cb04a7f2897bf4e5bbc5e882be16814f714524db9dceee6a4c2c194922
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.21.0 setuptools/40.6.3 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.7.0
|
Security for flit6 0.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.