This release is a pre-release and may not be stable for production use.
OOpen
Object-Oriented file and path handling.
The std lib file and path options aren’t very pythonic.
I should be able to perform basic tasks directly on the file.
Status: In development.
License: MIT
- Semantic Versioning
I will commit to not breaking the public API within major versions.
- Donations
If you would like to support it’s author, you may do so via gittip. Thanks for your support!
Example usage:
>>> from oopen import OOpen
>>> oofile = OOpen('example_file.py')
Retrieve and set the name of a file:
>>> oofile.name 'example_file.py' >>> oofile.path '/Users/ajhekman/Projects/oopen/oopen/example_file.py' >>> oofile.name = 'test.txt' >>> oofile.path '/Users/ajhekman/Projects/oopen/oopen/test.txt' # << note the changed filename >>> oofile.location '/Users/ajhekman/Projects/oopen/oopen/'
Retrieve other file information:
>>> oofile.sha1 # all of the hashes within hashlib are supported (md5 to sha 512) 'e90296612f91b8adf498884b20c8356113c83a73' >>> oofile.modified_time datetime.datetime(2013, 1, 14, 9, 10, 31) # << file times are represented as native datetime objects
Install
with pip (recommended):
Optional use virtualenv:
virtualenv venv
source venv/bin/activate
[sudo] pip install oopen
with easy_install:
sudo easy_install oopen
from source:
update version numbers where appropriate
Download latest release from PyPI
tar -xvzf oopen-x.x.x.tar.gz
cd oopen-x.x.x
[sudo] python setup.py install
from git:
Useful for specifying an exact commit, or for local development.
pip install-e git+https://github.com/ajhekman/OOpen#egg=oopen
you may also specify a tag or commit hash after the URL
pip install -e git+https://github.com/ajhekman/OOpen@0.1.1#egg=oopen
pip install -e git+https://github.com/ajhekman/OOpen@47f6e43cfc6391c06ae2a9eda6f63300c1b0558c#egg=oopen
Uninstall:
pip uninstall oopen
History
0.2.3 (2013-01-24)
using abspath for stat lookup
Added multiline support to history generation regex
0.2.2 (2013-01-24)
Fixed link formatting in similar projects
0.2.1 (2013-01-23)
corrected tag-version sync
0.2.0 (2013-01-23)
Added preliminary support for the extension property
Added related projects to README
0.1.3 (2013-01-20)
Added publishing tasks to fabfile
0.1.2 (2013-01-20)
modified .gitignore
Improvements to fabfile
Made reSt modifications for github
README.rst is now a compliation of INFO,INSTALL,HISTORY,LICENSE
Further packaging and install improvements
0.1.1 (2013-01-20)
Packaging updates
0.1.0 (2013-01-19)
Initial Release
For development only, needs to be tested.
Similar Projects:
not affiliated with oopen or it’s author
- Unipath
Object-oriented alternative to os/os.path/shutil
- filepath
Object-oriented filesystem path representation.
- forked-path
An object oriented file path module
- fpath
Filesystem paths as objects
- lilydjwg.Path
An object that handles path more easily
- path3
Object for working with files and directories
- pathlib
Object-oriented filesystem paths
- pathobject
An update of Jason Orendorff’s path.py.
- xpathrecord
XpathRecord: An XML to read-only Python objects library
- z3c.objpath
Generate and resolve paths to to objects.
- zope.traversing
Resolving paths in the object hierarchy
License
Metadata
Release files for oopen 0.2.3-dev
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 | |
|---|---|---|---|---|
| oopen-0.2.3-dev.tar.gz | 7.0 kB | Without provenance | Details |
Release files / oopen-0.2.3-dev.tar.gz
| Download URL | oopen-0.2.3-dev.tar.gz |
|---|---|
| Size | 7.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ed0d635337ca9b76a1e1e8c46d14c23dd047dac01d648b2201d46cef39e0637a
|
|
BLAKE2b-256 checksum How to use checksums |
66557bd32ad562fe06a0fd691fc3c813a9767f86c8dd5a2e7b23d21514dc1e0c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for oopen 0.2.3-dev
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.