Plug n’ Play
Plug n’ PLay (PnP) is a Generic plug-in system inspired by Trac’s (http://trac.edgewall.org) internal component management. With PnP you can turn any program into a pluggable software very easily.
You just have to define the Interfaces and let others implement them. When your code is running you can dynamically retrieve who are the classes that implement a certain Interface, and call the specific methods.
A simple example
Think this way: You have e very simple program that just copy files around.
Say you want to check if the copy was OK by calculating the MD5 hash of the two files (the original and the copy). You can do this implementing the MD5 check inside your main code, that’s OK too, but when you need to add another check (e.g. calculate the SHA-1 of the files) you will have to modify your code so it can call two methods, the MD5 checker and the SHA-1 checker.
With PnP you write only the main piece of the program, the part that does only the copying, and the hash checkers you can implement whenever you want, without any modification to the main code.
PnP is roughly a implementation of the Observer pattern (http://en.wikipedia.org/wiki/Observer_pattern).
The code for this example
Ok, too much talk, now some code. A pseudo-code to the example above would be:
class CopyListener(Interface):
def copy_finished(self, original_file, new_file):
pass
The main code would be:
PnP.load_plugins("/some/path/with/python/files") # egg files in the future?.
copy_file(file1, file2)
# Would return all python classes that
# implement CopyListerner interface
copy_listeners = CopyListener.implementors()
# Call each of the listeners telling the copy finished
for listener in copy_listeners:
listener.copy_finished(file1, file2)
And an example of one such observer would be:
from myproject.interfaces import CopyListener
class MD5Check(Plugin):
implements = [CopyListener,]
def copy_finished(self, file1, file2):
md5_1 = hash.md5(file1.read()).hexdigest()
md5_2 = hash.md5(file2.read()).hexdigest()
if md5_1 is not md5_2:
# Do something very useful! =)
Conclusion
Did you like this project? Very nice, so help me write it! Fork the repo and send me some pull requests! Or talk to me directly if you have some great ideas to implement!
Thanks,
Dalton Barreto
Metadata
Release files for plugnplay 0.5.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 |
|---|---|---|---|---|
| plugnplay-0.5.4.tar.gz | 11.2 kB | Without provenance | Details for plugnplay-0.5.4.tar.gz |
Release files / plugnplay-0.5.4.tar.gz
| Download URL | plugnplay-0.5.4.tar.gz |
|---|---|
| Size | 11.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
877e2d2500a45aaf31e5175f9f46182088d3e2d64c1c6b9ff6c778ae0ee594c8
|
|
BLAKE2b-256 checksum How to use checksums |
7eb146bf913524b93361a4749da565204a924feeceb05c06e73830ad4c90c527
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/3.7
|
Security for plugnplay 0.5.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.