Metadata-Version: 2.4
Name: plesty-sdk
Version: 0.0.2.dev2
Summary: Command-line application for developing Python modules compliant with the Plesty standard.
Author: Plesty Development Team
License-File: COPYING
License-File: COPYING.LESSER
License-File: LICENSE
Requires-Python: >=3.12
Requires-Dist: click>=3.8
Requires-Dist: livereload>=2.7.1
Requires-Dist: myst-parser>=5.0.0
Requires-Dist: pydata-sphinx-theme==0.17.1
Requires-Dist: ruff>=0.14
Requires-Dist: sphinx-autoapi>=3.6.1
Requires-Dist: sphinx-copybutton>=0.5.2
Requires-Dist: sphinx-design>=0.7.0
Requires-Dist: sphinx-external-toc>=1.1.0
Requires-Dist: sphinx>=9.1.0
Requires-Dist: sphinxcontrib-mermaid>=2.0.0
Requires-Dist: watchfiles>=1.1.1
Description-Content-Type: text/markdown

# plesty-sdk - Setting the Coding Standard


### What to standardize:
1.	Code hygiene 
2.  Documentation / examples
3.	Data standards
4.	Module-specific Integration standards (interfaces, version management, …) on different levels (unit, integration, end to end) and modules (device, instrument, analyzer)
5.	GUI
6.	Simulator / Testing
7.	Error management

The plesty-sdk module must check for those standards. It must be simple to use, well documented and verbose. 


### Standardization levels

The suggested levels of plesty standards are:

**Plexy Pixel (Easy):**
- Basic repository structure (readme, src, example?)
- Code Hygiene (#1) and documented example (#2)
- For executable modules: Standard vor execution (e.g. via uvx)

**Plexy Nebula (Intermediate):** Focus on basic functionality and interconnected modules
- #1 and #2 (extended),#3, #4, partial testing
(standards are just checked if exists, e.g. GUI)

**Plexy Quantum (Advanced):**
- Full check of all standardization goals
- modules with these standards should be able to all work together and be actively maintained (dependency management etc) 


## LICENSE
Plesty is licensed under the GNU Lesser General Public License v3.0 or later
(LGPL-3.0-or-later). See the LICENSE file.