On Tue, Jul 24, 2018 at 5:48 PM, Brad Warren <b...@eff.org> wrote: > Do you know if our approach to using setuptools entry_points to find plugins > will work [with conda]? This is described at > https://setuptools.readthedocs.io/en/latest/setuptools.html#dynamic-discovery-of-services-and-plugins.
Yes, installing Python inside a conda environment gives you a regular Python environment, and things like entry_points work fine. > On Jul 23, 2018, at 11:10 PM, James Bennett <ubernost...@gmail.com> wrote: > >> On Mon, Jul 23, 2018 at 8:17 PM, Alex Walters <tritium-l...@sdamon.com> >> wrote: >>> >>> As a user of certbot, docker, conda, nix, and guix are non-starters. I'm >>> not depending on those tools for my production server (and while docker may >>> be a dependency for some people, that is hardly universal). Adding >>> heavyweight technical dependencies are problematic if your goal is to get >>> everyone using your software. You're better off with cx_freeze or >>> pyinstaller binaries downloaded from a website or a PPA-like-system to add >>> to system package managers, which are not perfect solutions either. >> >> I would emphasize this point. > > Not wanting to install a lot of extra software to use Certbot is certainly > fair and we’d obviously prefer our packaging solution to be as lightweight > as possible. Thanks for bringing this up as a consideration. I feel like these responses may be lumping things together more than is helpful... using docker is quite heavyweight in the sense that it makes major demands on the host system: you need a docker daemon running, it has to be root, maybe it needs some special kernel modules to handle overlay filesystems, and so forth. That's fine if it's there already, but if it's not then certbot shouldn't be trying to bootstrap a docker installation from scratch. Conda OTOH is nothing like that -- it's just tools and conventions for working with regular files on a regular filesystem. One of its core design goals was that non-technical grad students should be able to drop it into a random directory on some HPC cluster where they don't have root and that's running some weird old distro like Scientific Linux 6, run one command, and have everything just work. Which sounds pretty similar to your use case. I don't know where nix and guix fall on this spectrum. > On Jul 24, 2018, at 4:36 AM, Nick Coghlan <ncogh...@gmail.com> wrote: > > However, there *are* folks that have been working on allowing > applications to be defined primarily as Python projects, and then have > the creation of wrapper native installers be a pushbutton exercise, > rather than requiring careful human handholding. But it sounds like they also want to be able to install/remove/upgrade *parts* of the Python project, for their plugin support. And maybe upgrade the Python interpreter as well. Do any of these tools allow that? That's the thing that really made me think about conda. -n -- Nathaniel J. Smith -- https://vorpus.org -- Distutils-SIG mailing list -- distutils-sig@python.org To unsubscribe send an email to distutils-sig-le...@python.org https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/mm3/archives/list/distutils-sig@python.org/message/S5YXVIMB3JTPNZKR3LNIGJGQ4ZL2P4VK/
