scratch-dir
Unit test mixin which creates a scratch director. Sets self.scratch_dir on initialization, and deletes it when finished.
import unittest
from scratch_dir import ScratchDirMixin
class TestThing(CreateScratchDirectoryMixin, unittest.TestCase):
def setUp(self):
import json
import os
super(TestThing, self).setUp()
self.local_json_file = self.get_tmp_path('example.json')
json.dump({'a': 42}, self.local_json_file)
print 'Example file written to scratch dir: {}'.format(self.scratch_dir)Development
pip install -r requirements_dev.txt
rake lintContribute
Issue Tracker: https://github.com/bodylabs/scratch-dir/issues
Source Code: https://github.com/bodylabs/scratch-dir
Pull requests welcome!
Support
If you are having issues, please let us know.
License
The project is licensed under the two-clause BSD license.
1 maintainer
Metadata
1 maintainer
Release files for scratch-dir 1.0.0
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 |
|---|---|---|---|---|
| scratch-dir-1.0.0.tar.gz | 2.1 kB | Without provenance | Details for scratch-dir-1.0.0.tar.gz |
Release files / scratch-dir-1.0.0.tar.gz
| Download URL | scratch-dir-1.0.0.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
946c327fc508f5c590460f70f418a787960181ff724332f669a84c5e57405f9a
|
|
BLAKE2b-256 checksum How to use checksums |
03bfdf5bd4c9ba10e86607af608deb450b42f3551645dc63fb7c055c47fd1110
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for scratch-dir 1.0.0
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.
