> 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
