# requirements_dev.txt we use for the testing It makes it easier to install and manage dependencies for development and testing, separate from the dependencies required for production.
# difference between requirements_dev.txt and requirements.txt
requirements.txt is used to specify the dependencies required to run the production code of a Python project, while requirements_dev.txt is used to specify the dependencies required for development and testing purposes.
# tox.ini We use if for the testing in the python package testing against different version of the python
## how tox works tox enviornment creation 1. Install depedencies and packages 2. Run commands 3. Its a combination of the (virtualenvwrapper and makefile) 4. It creates a .tox
# pyproject.toml it is being used for configuration the python project it is a alternative of the setup.cfg file. its containts configuration related to the build system such as the build tool used package name version author license and dependencies
# setup.cfg In summary, setup.cfg is used by setuptools to configure the packaging and installation of a Python projec
# Testing python application types of testing 1. Automated testing 2. Manual testing
Mode of testing 1. Unit testing 2. Integration tests
Testing frameworks
pytest
unittest
robotframework
selenium
behave
doctest
# check with the code style formatting and syntax(coding standard)
pylint
flake8(it is best because it containt 3 library pylint pycodestyle mccabe)
pycodestyle
Metadata
Release files for automationdb 0.0.7
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 | |
|---|---|---|---|---|
| automationdb-0.0.7.tar.gz | 3.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| automationdb-0.0.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.3 kB
Release files / automationdb-0.0.7.tar.gz
| Download URL | automationdb-0.0.7.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ab5bd6792ef768ffd01056418ac45a526772b0010583c2c8a8f21be7e59b9500
|
|
BLAKE2b-256 checksum How to use checksums |
74881eaa15a2db22b10bd0aef287ee1499b1e6bd6e61ca9a8989178dd6c04ef4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.18
|
Release files / automationdb-0.0.7-py3-none-any.whl
| Download URL | automationdb-0.0.7-py3-none-any.whl |
|---|---|
| Size | 3.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e635334d17a2134dea0e013c478df94c36ab98f41a3cbf3f536ba58f6e040341
|
|
BLAKE2b-256 checksum How to use checksums |
e78e8d81e99e7064880610f51217232988561ed680eee01f51f8bf4dc3a6b2a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.18
|
Security for automationdb 0.0.7
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.