A Microsoft SQL Server TDS connector for SQLAlchemy.
1 maintainer
Metadata
1 maintainer
Release files for sqlalchemy-pytds 1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sqlalchemy_pytds-1.0.3-py3-none-any.whl | Python 3 | none | any | Details |
| sqlalchemy_pytds-1.0.3-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 16.3 kB
Release files / sqlalchemy_pytds-1.0.3-py3-none-any.whl
| Download URL | sqlalchemy_pytds-1.0.3-py3-none-any.whl |
|---|---|
| Size | 8.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ed207cc0b121a25bd820c7d1695a80316d483fd88a8d9b890db20e68f1036a18
|
|
BLAKE2b-256 checksum How to use checksums |
1cf419766d13d10d7d0dde9b890f4d3373f6e12aa4f1bd7d3655238254730d2d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.5
|
Release files / sqlalchemy_pytds-1.0.3-py2.py3-none-any.whl
| Download URL | sqlalchemy_pytds-1.0.3-py2.py3-none-any.whl |
|---|---|
| Size | 8.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
8e611df50b187d611f86e5368c6b328b49610c2259ac95875ad6db909f7cb15e
|
|
BLAKE2b-256 checksum How to use checksums |
14313ad9fda0395d91caab21e340b783c9c3511be5cc1894a24905348eaafd12
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.5
|
Security for sqlalchemy-pytds 1.0.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.
