Skip to main content

PDS Lasso Requirements

The PDS Lasso Requirements generates requirements reports of software projects based on GitHub issues. It's part of the "Lasso" family of products.

Please visit our website at: https://nasa-pds.github.io/lasso-requirements

It may have useful information for developers and end-users.

Prerequisites

Installing this software requires git to be present on the target systme.

User Quickstart

Install with:

pip install lasso-requirements

To execute, run:

(put your run commands here)

Code of Conduct

All users and developers of the NASA-PDS software are expected to abide by our Code of Conduct. Please read this to ensure you understand the expectations of our community.

Development

To develop this project, use your favorite text editor, or an integrated development environment with Python support, such as PyCharm.

Contributing

For information on how to contribute to NASA-PDS codebases please take a look at our Contributing guidelines.

Installation

Install in editable mode and with extra developer dependencies into your virtual environment of choice:

pip install --editable '.[dev]'

Configure the pre-commit hooks:

pre-commit install
pre-commit install -t pre-push
pre-commit install -t prepare-commit-msg
pre-commit install -t commit-msg

These hooks check code formatting and also aborts commits that contain secrets such as passwords or API keys. However, a one time setup is required in your global Git configuration. See the wiki entry on Git Secrets to learn how.

Packaging

To isolate and be able to re-produce the environment for this package, you should use a Python Virtual Environment. To do so, run:

python3 -m venv venv

Then exclusively use venv/bin/python, venv/bin/pip, etc. Or, "activate" the virtual environment by sourcing the appropriate script in the venv/bin directory.

If you have tox installed and would like it to create your environment and install dependencies for you run:

tox --devenv <name you'd like for env> -e dev

Dependencies for development are specified as the dev extras_require in setup.cfg; they are installed into the virtual environment as follows:

pip install --editable '.[dev]'

All the source code is in a sub-directory under src.

Tooling

The dev extras_require included in the template repo installs black, flake8 (plus some plugins), and mypy along with default configuration for all of them. You can run all of these (and more!) with:

tox -e lint

Metadata

Release files for lasso.requirements 1.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for lasso.requirements 1.1.0
File Size Uploaded Provenance Actions
lasso_requirements-1.1.0.tar.gz 15.4 kB Without provenance Details for lasso_requirements-1.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for lasso.requirements 1.1.0
File Interpreter ABI Platform Actions
lasso_requirements-1.1.0-py3-none-any.whl Python 3 none any Details for lasso_requirements-1.1.0-py3-none-any.whl

Total release size: 31.3 kB

Release files / lasso_requirements-1.1.0.tar.gz

Download URL lasso_requirements-1.1.0.tar.gz
Size 15.4 kB
Tags Source
SHA-256 checksum
How to use checksums
79aa0461c30e6e0da0e8de010ab6a3567c88cbfb2b894bd53bb8a4b433883d8b
BLAKE2b-256 checksum
How to use checksums
1ac2b77870beff638d12c77a211e5599cacfc8684dc8a2deed8adf23cfc90224
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.7

Release files / lasso_requirements-1.1.0-py3-none-any.whl

Download URL lasso_requirements-1.1.0-py3-none-any.whl
Size 15.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4fcb7ff1a527ffed4af51279259eda84cc79d162c225af1878b4924109f81625
BLAKE2b-256 checksum
How to use checksums
c8f17f20da375609bed10e20e49f10e23a96533927ecc418f78ddadf14e9a89b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.7

Security for lasso.requirements 1.1.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.

Release history Release notifications | RSS feed

This release

1.1.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page