py-singleton
Singleton pattern for python 2 & 3.
Install
pip install py-singleton
Test
in the root folder, run pytest:
pytest
Dependencies
None
unit test needs pytest.
API
-
Apply class decorator singleton to any class;
-
Expected behaviors:
- class can be instantiated as usual, but only one instance is created;
- apis to access the class instance:
@singleton class Server(object): pass srv = Server()
or
srv = Server.instance()
- the function _init_() of decorated class will be called once and only once when the instance is created.
Example
from py_singleton import singleton
@singleton
class A(object):
count = 0
def __init__(self):
A.count += 1
a1 = A()
a2 = A()
a3 = A.instance()
assert A.count == 1
assert a1 is a2
assert a1 is a3
Limitation
For best performance, the code to create instance is not thread-safe, however, after the instance is created it should be safe for multi-threading.
It is recommended to call instance() once during the initial phrase of your app in a single thread.
Metadata
Release files for py-singleton 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 |
|---|---|---|---|---|
| py-singleton-1.0.0.tar.gz | 2.9 kB | Without provenance | Details for py-singleton-1.0.0.tar.gz |
Release files / py-singleton-1.0.0.tar.gz
| Download URL | py-singleton-1.0.0.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9922a69f6e6b9390e5c1b3d2b39e119d5fcffa92d9c3145de3b8533a93077fb7
|
|
BLAKE2b-256 checksum How to use checksums |
e94925659b2596ab0e536c168a90358e9cb4a70fd776955a6174a7fde76a9264
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.45.0 CPython/3.8.2
|
Security for py-singleton 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.