https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234816
--- Comment #10 from gronke <ste...@gronke.net> --- > Said another way, when a python package supports multiple python versions > (almost all of them), then concurrently installable versions should not > conflict with each other. There is no need to install multiple versions on the same host. The build target is always the distributions default Python 3 version. > There are plenty of python packages that only provide > console_scripts/scripts, not providing importable libraries, that use all of > the standard distribution/installation mechanics that the python ecosystem > offers and recommends. These all end up living in the version specific python > environment even if the only normal way of accessing functionality is via > LOCALBASE/bin scripts. Users of the ioc CLI tool do not care what language it is written in - they want to install it and use it to manage their jails. I don't find it necessary to require users knowing their target Python version, if we could instead depend on the same environment that we cover with our automated tests. > If you don't want to prefix the 'portname' (and its svn dir) to be prefixed, > that's fine, but I still would. The language this is written in does not have an effect on the use of this CLI tool. If a tool written in RUST imports libioc and provides the same interfaces, there would be no noticeable difference for the user. Therefore I prefer to call it just ioc. > On the dependency front, one should depend on the respective python ports > rather than install them via pip (or any other alternate mechanism) done -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ freebsd-python@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
