Antipathy – for those tired of os.path
Tired of calling a function for every path manipulation you need to do?
Is:
>>> path, filename = os.path.split(some_name) >>> basename, ext = os.path.splitext(filename) >>> basename = basename + '_01' >>> new_name = os.path.join(path, basename+ext)
wearing on your nerves?
In short, are you filled with antipathy [1] for os.path?
Then get antipathy and work with Path:
>>> from antipathy import Path
>>> some_name = Path('/home/ethan/source/my_file.txt')
>>> backups = Path('/home/ethan/backup/')
>>> print some_name.path
'/home/ethan/source/'
>>> print some_name.ext
'.txt'
>>> print some_name.exists()
True # (well, if it happens to exist at this moment ;)
>>> backup = backups / some_name.filename + '_01' + some_name.ext
>>> print backup
'/home/ethan/backup/my_file_01.txt'
>>> some_name.copy(backup)
Because Path is a subclass of bytes/str/unicode, it can still be passed to other functions that expect a bytes/str/unicode object and work seamlessly [2].
[1] https://www.google.com/#q=antipathy
[2] in most cases – there are a few places that do a type check instead of an isinstance check.
1 maintainer
Metadata
1 maintainer
Release files for antipathy 0.85.4
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 | Actions |
|---|---|---|---|---|
| antipathy-0.85.4.tar.gz | 24.2 kB | Without provenance | Details for antipathy-0.85.4.tar.gz |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| antipathy-0.85.4-py3-none-any.whl | Python 3 | none | any | Details for antipathy-0.85.4-py3-none-any.whl |
| antipathy-0.85.4-py2-none-any.whl | Python 2 | none | any | Details for antipathy-0.85.4-py2-none-any.whl |
Total release size: 73.8 kB
Release files / antipathy-0.85.4.tar.gz
| Download URL | antipathy-0.85.4.tar.gz |
|---|---|
| Size | 24.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c3cd2500f342a08d282be66fb64239a97e893120dcc6ac80818a31d0f4bc3c70
|
|
BLAKE2b-256 checksum How to use checksums |
3bf5521943df43aff62607823712874542113346f2c425011a5c8aeea74eb24a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/58.1.0 requests-toolbelt/0.9.1 tqdm/4.57.0 CPython/3.9.13+
|
Release files / antipathy-0.85.4-py3-none-any.whl
| Download URL | antipathy-0.85.4-py3-none-any.whl |
|---|---|
| Size | 24.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3eecc7cfec2a5162502f60fda4b47b5595fbf41d1dc7808f4882bb447fdd2058
|
|
BLAKE2b-256 checksum How to use checksums |
62872b28f193e6b74cd71e94dc0fd4f81719bd9d344a4540c5ecef7812f43488
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/58.1.0 requests-toolbelt/0.9.1 tqdm/4.57.0 CPython/3.9.13+
|
Release files / antipathy-0.85.4-py2-none-any.whl
| Download URL | antipathy-0.85.4-py2-none-any.whl |
|---|---|
| Size | 24.8 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
0fad030872aca697b3529530a3d80863603716666f479083cd9e19151ab05319
|
|
BLAKE2b-256 checksum How to use checksums |
0fcd1e663f69a9e2db78a48e69998bb325f80369070e44aa2cd93c28bb1879ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/58.1.0 requests-toolbelt/0.9.1 tqdm/4.57.0 CPython/3.9.13+
|
Security for antipathy 0.85.4
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.
