2 files were added to this release more than 14 days after its initial publication. Inspect the release files before installing.
This Python package creates a class named RemoteDevice, which contains an instance of serial_device2.SerialDevice and adds methods to it, like auto discovery of available remote devices in Linux, Windows, and Mac OS X. This class automatically creates methods from available functions reported by the remote device when it is running the appropriate firmware.
Authors:
Peter Polidoro <polidorop@janelia.hhmi.org>
License:
BSD
Example Usage:
from remote_device import RemoteDevice
dev = RemoteDevice()
dev = RemoteDevice() # Automatically finds device if one available
dev = RemoteDevice('/dev/ttyACM0') # Linux specific port
dev = RemoteDevice('/dev/tty.usbmodem262471') # Mac OS X specific port
dev = RemoteDevice('COM3') # Windows specific port
dev.get_device_info()
dev.get_methods()
devs = RemoteDevices() # Automatically finds all available devices
devs.items()
dev = devs[name][serial_number]
1 maintainer
Metadata
1 maintainer
Release files for remote_device 1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Files added late
2 files were uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
We recommend inspecting the release files before installing.
Source distributions (sdists)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| remote_device-1.0.zip | 12.3 kB | Without provenance | Details | |
| remote_device-1.0.tar.gz | 7.9 kB | Without provenance | Details |
Release files / remote_device-1.0.zip
File added late
This file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
We recommend inspecting the release file before installing.
| Download URL | remote_device-1.0.zip |
|---|---|
| Size | 12.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ab4b4d131aa98cba5d62170b66d4da2e4ffb749727b4c2cd5b1a94b5db5133c7
|
|
BLAKE2b-256 checksum How to use checksums |
efc46e039cd12b9bf18dcee501f04ccfdcf4c4f8481d56a59d0835243903b686
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / remote_device-1.0.tar.gz
File added late
This file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
We recommend inspecting the release file before installing.
| Download URL | remote_device-1.0.tar.gz |
|---|---|
| Size | 7.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2fcbd6eb2641615934c2fd456ca08c889dba0f1b15081450026000f2dc675bb0
|
|
BLAKE2b-256 checksum How to use checksums |
fbc6e68a323351237a5fb8d504e66f7aacafeb77f0c5c457aff1bfb11d54907d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for remote_device 1.0
Upload timing
Files added late
2 files were uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
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.
