semvec/pypi-packages huggingface dataset:
gwtc-tools 0.3.1
A package for gwtc operations, including interactions with gracedb
Requires Python: >=3.6

# gwtc

A library for creating and interacting with Gravitational Wave Transient Catalogs in gracedb.

[[_TOC_]]

## Authentication

This package uses the `ligo-gracedb` client for authentication. Please refer to the [GraceDB documentation on SciTokens](https://gracedb.ligo.org/documentation/authentication.html) for information on how to authenticate using SciTokens.

## Tutorial

Please see: https://git.ligo.org/chad-hanna/gwtc/-/blob/main/examples/README.md


## installation from source

*Note these instructions will be improved and we will make this available in Conda*. This is just an example, modify as you see fit.

```
$ ssh chad.hanna@ldas-pcdev1.ligo-wa.caltech.edu
(igwn) [chad.hanna@ldas-pcdev1 ~]$ mkdir git
(igwn) [chad.hanna@ldas-pcdev1 ~]$ cd git
(igwn) [chad.hanna@ldas-pcdev1 git]$ git clone git@git.ligo.org:chad-hanna/gwtc.git
(igwn) [chad.hanna@ldas-pcdev1 git]$ pip install ./gwtc
```

### See latest catalog on gracedb

https://gracedb-test.ligo.org/api/gwtc/4/latest/

### See previous version on gracedb

https://gracedb-test.ligo.org/api/gwtc/4/1/
securesystemslib 1.3.1
A library that provides cryptographic and general-purpose routines for Secure Systems Lab projects at NYU
Requires Python: ~=3.8
Keywords: cryptography, ecdsa, ed25519, keys, rsa, signatures

# securesystemslib

[![CI](https://github.com/secure-systems-lab/securesystemslib/workflows/Run%20Securesystemslib%20tests/badge.svg)](https://github.com/secure-systems-lab/securesystemslib/actions?query=workflow%3A%22Run+Securesystemslib+tests%22+branch%3Amain)
[![Documentation Status](https://readthedocs.org/projects/python-securesystemslib/badge/?version=latest)](https://python-securesystemslib.readthedocs.io/en/latest/?badge=latest)

Securesystemslib is a cryptography interface for signing and verifying digital
signatures. It is developed for the [TUF](https://theupdateframework.io) and
[in-toto](https://in-toto.io) projects: the key and signature containers are
compatible with metadata formats from those projects.

Under the hood, Securesystemslib can use various digital signing systems
(e.g. [cryptography](https://pypi.org/project/cryptography/), PIV hardware keys
and multiple cloud-based key management systems).

## Installation

The default installation supports [pure-Python `ed25519` signature
verification](https://github.com/pyca/ed25519) only. To enable other schemes and
signature creation, `securesystemslib` can be installed with *extras*. See
[pyproject.toml](pyproject.toml) for available *optional dependencies*.

```bash
# Install with ed25519, RSA, ECDSA sign and verify support
pip install securesystemslib[crypto]
```

```bash
# ...or with HSM (e.g. Yubikey) support
pip install securesystemslib[hsm]
```

## Usage
[python-securesystemslib.readthedocs.io](https://python-securesystemslib.readthedocs.io)

## Contact
- Questions and discussions:
  [`#securesystemslib-python`](https://cloud-native.slack.com/archives/C05PF3GA7AL)
  on [CNCF Slack](https://communityinviter.com/apps/cloud-native/cncf)
- Security issues: see [Security policy](docs/SECURITY.md)
- Other issues and requests: [*Open a new
  issue*](https://github.com/secure-systems-lab/securesystemslib/issues/new)

## Contribute
See [Instructions for contributors](docs/CONTRIBUTING.md).

## Legacy key migration

Use
[`migrate_keys`](https://github.com/secure-systems-lab/securesystemslib/blob/v0.31.0/docs/migrate_key.py)
script to convert key pairs generated with legacy `keys` or `interface` modules
to a consistent standard format, which is compatible with
[`CryptoSigner`](docs/CRYPTO_SIGNER.md). The script requires
`securesystemslib~=0.31.0`.
py-gitea 0.2.10
A python wrapper for the Gitea API
Requires Python: >=3.11
Keywords: Gitea, api, wrapper

# py-gitea

A very simple API client for Gitea > 1.16.1

This has been somewhat tested (and used), so most things should work as expected.

Note that not the full Swagger-API is accessible. The whole implementation is focused
on making access and working with Organizations, Teams, Repositories and Users as pain
free as possible.

Originally forked from https://github.com/m301/py-gitea.

## Usage

First get a `gitea` object wrapping access and authentication (via an api token) for your gitea instance:

```python
from gitea import *

gitea = Gitea(URL, TOKEN)
```

Operations like requesting the Gitea version or authentication user can be requested directly from the `gitea` object:

```python
print("Gitea Version: " + gitea.get_version())
print("API-Token belongs to user: " + gitea.get_user().username)
```

Adding entities like Users, Organizations, ... also is done via the gitea object.

```python
user = gitea.create_user("Test Testson", "test@test.test", "password")
```

All operations on entities in gitea are then accomplished via the according wrapper objects for those entities.
Each of those objects has a `.request` method that creates an entity according to your gitea instance.

```python
other_user = User.request(gitea, "OtherUserName")
print(other_user.username)
```

Note that the fields of the User, Organization,... classes are dynamically created at runtime, and thus not visible
during divelopment. Refer to the Gitea-API documentation for the fields names.

Fields that can not be altered via gitea-api, are read only. After altering a field, the `.commit` method of the
according object must be called to synchronize the changed fields with your gitea instance.

```python
org = Organization.request(gitea, test_org)
org.description = "some new description"
org.location = "some new location"
org.commit()
```

An entity in gitea can be deleted by calling delete.

```python
org.delete()
```

All entity objects do have methods to execute some of the requests possible though the gitea-api:

```python
org = Organization.request(gitea, ORGNAME)
teams = org.get_teams()
for team in teams:
    repos = team.get_repos()
    for repo in repos:
        print(repo.name)
```

## Installation

Use ``pip install py-gitea`` to install.

## Tests

Tests can be run with:

```python3 -m pytest test_api.py```

Make sure to have a gitea-instance running on `http://localhost:3000`, and an admin-user token at `.token`.
The admin user must be named ``test``, with email ``secondarytest@test.org``.
meemoo-sip-validator 0.2.9
A library to validate meemoo SIP's
Requires Python: >=3.11

# Meemoo SIP Validator

> WARNING: This library is not yet finished.
> The [SIP specification](https://developer.meemoo.be/docs/diginstroom/sip/) must always be seen as the source of truth.
> Some messages produced by the validator may to be clear and user friendly.

Library to validate meemoo SIP's.

## Usage

You must have a Java runtime available.

Select a SIP version to validate from the [meemoo developer site](https://developer.meemoo.be/docs/diginstroom/sip/).
Run the validator from the CLI.

```
meemoo-sip-validator "2.1" ~/Downloads/uuid-97bb2a97-f991-46f5-a9a4-b474ab30d4de
```

Alternatively, you can run it in Python.

```py
from meemoo_sip_validator.v2_1 import validate

is_valid, report = validate("path/to/sip")
```

Examples of meemoo SIP's are found in [examples repository](https://github.com/viaacode/sip-examples).

## Release

Bump the version in `pyproject.toml` and add a tag `vX.Y.Z` to the commit to start the CI/CD.
The package will be build and uploaded to the interal registry.