Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pymmdevice as its own seperate package #4

Open
henrypinkard opened this issue Jun 28, 2024 · 2 comments
Open

pymmdevice as its own seperate package #4

henrypinkard opened this issue Jun 28, 2024 · 2 comments

Comments

@henrypinkard
Copy link
Member

Should pymmdevice be a standalone python package separate form the Core? Any disadvantages or challenges to doing this?

@marktsuchida
Copy link
Member

Any advantages, given that you still need an MM installation? (Unless you are using pymmcore and all of your devices of PyDevice.)

Disadvantage is that the Core needs to be configured to find it, somewhere buried in site-packages.

@henrypinkard
Copy link
Member Author

The advantage I would see is that this ultimately may contain a collection of python code for controlling devices that implements a consistent API across device types, since many devices can be controlled independently of the core (is that right @@IvoVellekoop?), I imagine there may be people who just want to use these, directly, in python.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants