Skip to main content

Template README.md
This file is from the template repository. Rewrite it for your own package.

Python Package Setup

Setup Base

To install required pip modules for generate_toml.py, run

source scripts/setup_base.sh

User Setup

  • go to generate_toml.py file, and complete the setup in the User Setup session.
options = Options(
    # Will you use the discussion session in your repo?
    discussion=False
)

# Define the general information of your package
kwargs = Kwargs(
    name_space="None",
    module_name="None",
    description="None",
)

If you wrote all the information, run

python generate_toml.py

Template

If you want to understand the generation process, check the template variable in generate_toml.py.

Setup Env

Prerequisite

Finish User Setup first. Of course, conda command must be available.

Setup Env

Run

source scripts/setup_env.sh

steps

  • create an conda environment named as your $MODULE_NAME
  • activate the environment.
  • install requirements.txt

Generate Private Env

Generate a private repository in this repo. I recommend you to write all the unstructured codes in this repo.

source scripts/generate_dev_repo.sh

It will ask you the name of your repo, and then, generate a repo named f'{your_repo_name}-dev'.

Usage Tip

If you wrote your codes in a wrong branch,

  • backup the files to the dev repo
  • remove changes in your main(not main branch) repo
  • move to your correct branch
  • place back the backup codes

Workflows

I currently setup test and release workflows.

Test

If you make a PR with the patterns [ main, develop, 'release/', 'feature/' ],

It will perform your unittest in ["3.9", "3.10", "3.11"]

Release

required secret : PYPI_API_TOKEN

I usually make PRs only when I start release branches. release workflow is not conducted automatically. If you think your branch is ready to be published,

Metadata

Release files for crimson-anytree-extension 0.1.3

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

Source distribution (sdist)

Source distribution for crimson-anytree-extension 0.1.3
File Size Uploaded Provenance Actions
crimson_anytree_extension-0.1.3.tar.gz 8.5 kB Without provenance Details for crimson_anytree_extension-0.1.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for crimson-anytree-extension 0.1.3
File Interpreter ABI Platform Actions
crimson_anytree_extension-0.1.3-py3-none-any.whl Python 3 none any Details for crimson_anytree_extension-0.1.3-py3-none-any.whl

Total release size: 18.2 kB

Release files / crimson_anytree_extension-0.1.3.tar.gz

Download URL crimson_anytree_extension-0.1.3.tar.gz
Size 8.5 kB
Tags Source
SHA-256 checksum
How to use checksums
4e035ac0739907bacd8d6fcfba7bd436033806edde3665d055b070ec46ad6ff5
BLAKE2b-256 checksum
How to use checksums
7531217d3c762c8a18ff7926522c1b8e33976fefe7079261e95e1aa8b36c9fb9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.1.0 CPython/3.10.16

Release files / crimson_anytree_extension-0.1.3-py3-none-any.whl

Download URL crimson_anytree_extension-0.1.3-py3-none-any.whl
Size 9.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
bc2fe78c6578a9a25a65bea5cda69f7234c430817e66e5eff00b1f5cd4889042
BLAKE2b-256 checksum
How to use checksums
98e8519d1f454cdcb18d54f30ab3f852943b0b015a548b1e84b40be063cc2030
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.1.0 CPython/3.10.16

Security for crimson-anytree-extension 0.1.3

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.

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