On Fri, May 29, 2020, at 8:36 AM, Mark Sapiro wrote:
On 5/29/20 7:49 AM, Ralf Wiegand wrote:
https://docs.mailman3.org/en/latest/install/install.html
I was following this "official" page. There is no word on "pip install mailman" as an alternate choise?
There is also a reference in regards to "Virtualenv Installation <https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-install>, recommended for Production" ... why is this recommended? Does the "pip install mailmail" install a production environment I can trust?
I didn't write that page, but I think it is saying that for production, installing in a virtualenv is preferred over installing globally, and not that it is necessarily preferred over installing a Docker container or a distro package.
Should we edit the wording to signify something else? I guess the definition of production varies a lot. While many would prefer distro packages to use in their sites, some others want the latest bug-fixed version.
Debian picks up their packages from PyPI too, but they verify the signatures on packages, which pip doesn't. So, from a strict security point of view, Debian might be slightly better, but with the lack of a proper Web Of Trust in PyPI, the value of the signature depends on how much you trust my signing key.
However, if you actually read the Virtualenv Installation document, you will see under Installing Mailman Core <https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mailman-core> it says to install Mailman core via
pip install mailmanin the virtualenv.-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)