Skip to main content

PyDM Converter

PyDM Converter is an PyDM-based tool developed at SLAC National Accelerator Laboratory. PyDM Converter is an open-source project.

For more information and a how to guide on PyDM Converter see the project's website

Report bug · Request feature

Contributing to PyDM Converter

Thank you for your interest in contributing to PyDM Converter! Your contributions help make the project better for everyone. Below are the guidelines to ensure a smooth and efficient collaboration.

How to Contribute

  1. Fork and Clone the Repository

    • Fork the PyDM Converter repository on GitHub.
    • Clone your fork to your local machine:
      git clone https://github.com/your-username/pydm-converter-tool.git
      cd pydm-converter-tool
      
  2. Set Up Your Development Environment

    • Install the necessary dependencies:
      pip install -r requirements.txt
      
  3. Implement Your Changes

    • Code Style: Follow the PEP8 style guide for Python code.
    • Documentation: Add docstrings to all new methods and classes using the NumPy style guide.
    • Unit Tests: Write unit tests for your changes using Pytest.
  4. Run Tests Locally

    • Ensure all tests pass before submitting:
      pytest
      
  5. Create a Pull Request (PR)

    • When you feel like your feature is ready to be merged into the pydm converter make a PR and request feedback from the Maintainers.
    • Provide a descriptive title and detailed description of your changes.

Pull Request Requirements

To ensure your PR is reviewed efficiently, please adhere to the following:

  • Unit Tests:

    • Include tests for all new functionality.
    • Ensure tests cover different scenarios and edge cases.
  • Documentation:

    • All new methods and classes must have comprehensive docstrings.
    • Follow the NumPy style guide for consistency.
  • Code Quality:

    • Adhere to the PEP8 style guide.
    • Ensure your code is clean, well-organized, and free of unnecessary complexity.

Additional Guidelines

  • Communication:
    • For significant changes, consider opening an issue to discuss your approach before starting.

Resources

Notes on Contributing to the Documentation

  1. Set Up Your Development Environment

    • Ensure you are working on your development environment.
  2. Navigate to the Project Directory

    • Go to the top-level pydm-converter-tool project directory, which contains the mkdocs.yml file.
  3. Make and Test Your Changes Locally

    • Edit the documentation files as needed.
    • Test your changes locally using MkDocs before submitting a pull request.

Detailed Steps

  1. Set Up Your Development Environment

    • Make sure you have all the necessary tools installed (e.g., Python, MkDocs).
  2. Navigate to the Project Directory

    cd path/to/pydm-converter-tool
    
  3. Install Dependencies

     pip install -r requirements.txt
    
  4. Serve the Documentation Locally

     mkdocs serve
    
  • Open your browser and go to http://localhost:8000 to preview your changes.
  1. Submit Your Changes
  • After verifying your changes, commit and push them to your forked repository.
  • Create a pull request to submit your updates.

If you have any questions or need further assistance, feel free to open an issue or reach out to the maintainers.

Metadata

Release files for PyDMConverter 1.0.7

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for PyDMConverter 1.0.7
File Size Uploaded
pydmconverter-1.0.7.tar.gz 502.0 kB Details

Release files / pydmconverter-1.0.7.tar.gz

Download URL pydmconverter-1.0.7.tar.gz
Size 502.0 kB
Tags Source
SHA-256 checksum
How to use checksums
0e43bad54416358c787591a50dc48cc78b43f6df9c817f59da48013c75de2357
BLAKE2b-256 checksum
How to use checksums
1f44a6462e5a79bc38d9e28049fdfa212c43a885c8c40ccbc80aec496659651d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 15, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.0.7 This release

1 release file

1.0.6

1 release file

1.0.5

1 release file

1.0.4

1 release file

1.0.3

1 release file

1.0.2

1 release file

0.0.0

1 release file

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page