Re: [ARTIQ] artiq dependencies
What about pointing out to known good version numbers of dependencies in the ARTIQ documentation? [:: ] Agreed that that's a better solution. I propose we build into setup.py a pull of specific version numbers for external dependencies. This makes it straightforward for end users. And, provides a straightforward deployment path for upgrades. That is, pull a new copy of setup.py from m-labs's github and run install. Duplicating and maintaining all the code from the dependencies will be painful, and will conflict with the package managers of Linux or Python distributions. Having a version number associated with each dependency is necessary anyway to report bugs, update them, etc. Sébastien ___ ARTIQ mailing list https://ssl.serverraum.org/lists/listinfo/artiq ___ ARTIQ mailing list https://ssl.serverraum.org/lists/listinfo/artiq
Re: [ARTIQ] artiq dependencies
I advocate adding options to setup.py to include these dependencies if a user want's them. I think it would make sense to fork external dependencies into m-labs/artiq so that dependencies don't break over time. I second the motion. ___ ARTIQ mailing list https://ssl.serverraum.org/lists/listinfo/artiq
Re: [ARTIQ] artiq dependencies
On 01/29/2015 04:25 AM, Slichter, Daniel H. wrote: I think it would make sense to fork external dependencies into m-labs/artiq so that dependencies don't break over time. I second the motion. What about pointing out to known good version numbers of dependencies in the ARTIQ documentation? Duplicating and maintaining all the code from the dependencies will be painful, and will conflict with the package managers of Linux or Python distributions. Having a version number associated with each dependency is necessary anyway to report bugs, update them, etc. Sébastien ___ ARTIQ mailing list https://ssl.serverraum.org/lists/listinfo/artiq
Re: [ARTIQ] artiq dependencies
I advocate adding options to setup.py to include these dependencies if a user want's them. I think it would make sense to fork external dependencies into m-labs/artiq so that dependencies don't break over time. -Joe On Wed, Jan 28, 2015 at 8:39 AM, Yann Sionneau y...@m-labs.hk wrote: Hello, I'm wondering about which kind of dependencies we should enforce in ARTIQ installer (setup.py). For instance, if an ARTIQ device (PDQ2, Lda, Thorlabs TDC/TPZ, PXI6733) needs a Python dependency (PyDAQmx here for PXI6733), should we put it in setup.py thus enforcing it's installation? Or should we just document that dependency and let the user install only what he needs. For instance, one might just want to install ARTIQ to run the GUI/the master but would for instance not need to run a controller (at least not on this particular computer). For just running the master you don't need the driver dependencies. Regards, -- Yann Sionneau ___ ARTIQ mailing list https://ssl.serverraum.org/lists/listinfo/artiq ___ ARTIQ mailing list https://ssl.serverraum.org/lists/listinfo/artiq
