On Sat, 13 Apr 2019 21:05:39 +1000
Steven D'Aprano wrote:
> If you're running MM2 under Python 2.7, and you also have Python 3.7
> installed, the two Python interpreters don't share packages unless
> you're doing something unusual. So updating one version of the
> installed package shouldn't
On 4/10/19 7:36 PM, Dave McGuire wrote:
> On 4/10/19 12:25 PM, Mark Sapiro wrote:
>> The path forward is to increase the community of MM 3 users which will
>> result in more people contributing to the project and faster progress.
>
> On that note, I migrated my half-dozen lists (a few hundred
On Thu, Apr 11, 2019 at 03:25:50PM -0500, Dimitri Maziuk via Mailman-Users
wrote:
> The problem is reliance on third-party libraries coupled with absence of
> usable package management system. It will "generally" run within the
> same major interpreter version unless it imports a package that
Matthew Goebel writes:
> Won't redhat just apply/support fixes provided the software vendor?
For RHEL, no, they'll do a lot more than that if it's covered by the
support contract. That's the business model: if they were just
providing the integration testing, Centos would eat their lunch.
>
On 4/12/19 10:21 AM, Matthew Goebel wrote:
> Won't redhat just apply/support fixes provided the software vendor? If
> something comes up with python
> how likely are they to build their own fix?
https://access.redhat.com/security/updates/backporting/
--
Dimitri Maziuk
Programmer/sysadmin
Won't redhat just apply/support fixes provided the software vendor? If
something comes up with python
how likely are they to build their own fix?
Matt
On Fri, Apr 12, 2019 at 11:17 AM Dmitri Maziuk via Mailman-Users <
mailman-users@python.org> wrote:
> On Fri, 12 Apr 2019 15:58:36 +0900
>
On Fri, 12 Apr 2019 15:58:36 +0900
"Stephen J. Turnbull" wrote:
> PS Just saw this:
>
> https://mobile.twitter.com/zooba/status/1116364827146854401
Whoever came up with that should upgrade to centos/SL/orrible 6: RedHat
will maintain and fix RHEL6 with its python 2.6 and apache 2.2 until
Mike Flannigan writes:
> I'm surprised to hear there is so much migration in Python with
> limited backward compatibility. Perl has never had that problem.
Of course it has. I had Perl 4 on my Debian box for a decade after
Perl 5 was released, because various apps had scripts or something
PS not that I disagree that the practical way out right now is to make a
simple e.g. flask-based UI for MM3.
--
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
signature.asc
Description: OpenPGP digital signature
On 4/11/19 12:15 PM, Mark Sapiro wrote:
> Generally older Python 3 code will run on newer versions. The issues are
> trying to run code developed for newer Python 3 versions on older versions.
The problem is reliance on third-party libraries coupled with absence of
usable package management
On 4/11/19 10:05 AM, Mike Flannigan wrote:
>
> I'm surprised to hear there is so much migration in
> Python with limited backward compatibility.?? Perl
> has never had that problem.?? I almost never have to
> modify my old code.?? I'd recommend you use Perl, but
> everybody knows Perl is dead :-)
I'm surprised to hear there is so much migration in
Python with limited backward compatibility.?? Perl
has never had that problem.?? I almost never have to
modify my old code.?? I'd recommend you use Perl, but
everybody knows Perl is dead :-)
Mike
On 4/10/2019 6:03 PM,
On 4/11/2019 3:22 AM, Stephen J. Turnbull wrote:
... If you want something that's never going to
change, Python 2.7 is as good as anything else.
Some orgs have "cybersecurity" with "vulnerability scanners". You may
have to spend more time hiding your python version from them, then
you'll
Carl Zwanzig writes:
> On 4/10/2019 11:36 AM, Dimitri Maziuk via Mailman-Users wrote:
> > (That said, given the history of python, my question would be if there
> > are any plans to port MM2 to golang or maybe gnat.)
Not within the Mailman project.
It seems pointless to me. If you want
On 4/10/19 12:25 PM, Mark Sapiro wrote:
> The path forward is to increase the community of MM 3 users which will
> result in more people contributing to the project and faster progress.
On that note, I migrated my half-dozen lists (a few hundred recipients
in total) to MM3 yesterday. I'm
On 4/10/19 2:53 PM, Jim Popovitch via Mailman-Users wrote:
>
> What Mailman things need assistance in MM3? I've avoided jumping in because
> honestly every time I looked it seemed like all the focus was everything but
> the email reflector bits.
There are (at the moment) 509 open issues at
On 4/10/19 12:08 PM, Carl Zwanzig wrote:
>
> Maybe there's a place for a community-driven port of MM2 onto python3. I
> am not volunteering, too many other projects currently.
I think a much more productive use of the community's resources would be
implementation of a light weight, non-Django
On 4/10/19 12:08 PM, Carl Zwanzig wrote:
>
> The main thing is that from appearances MM3 is large enterprise-grade
> list manager, but many of us don't need that, we need something for a
> few (<100?) lists with a few (<500?) members. I can run that on a small
> BSD box; spinning up django, sass,
On Wed, 2019-04-10 at 09:25 -0700, Mark Sapiro wrote:
>
> The path forward is to increase the community of MM 3 users which will
> result in more people contributing to the project and faster progress.
What Mailman things need assistance in MM3? I've avoided jumping in because
honestly every
On 4/10/19 2:08 PM, Carl Zwanzig wrote:
> Or rust, or python3 (which might be the easiest). I'm not sufficiently
> up on the python differences, but. it can't be -that- difficult.
> (and aren't there tools to assist? some code claims to be both v2 and v3
> compatible) (gnat? that's really
I'm more worried another DMARC style debacle myself, more than a Python
security issue, although that could be an issue.
Thanks,
Matt
On Wed, Apr 10, 2019 at 3:29 PM Sean McBride
wrote:
> On Wed, 10 Apr 2019 13:36:59 -0500, Dimitri Maziuk via Mailman-Users said:
>
> >On 4/10/19 12:49 PM, Sean
On Wed, Apr 10, 2019 at 11:36:24AM -0400, Matthew Goebel wrote:
> Now that all support for Python 2 is supposed to go away in 2020 are people
> going to move off of mailman 2?
Most of my mailman lists are run off a CentOS 6 box, have done for a long time,
quite stable.
CentOS 8 will (is
On Wed, 10 Apr 2019 13:36:59 -0500, Dimitri Maziuk via Mailman-Users said:
>On 4/10/19 12:49 PM, Sean McBride wrote:
>> On Wed, 10 Apr 2019 12:38:34 -0500, Dimitri Maziuk via Mailman-Users said:
>>
>>> How much support for python 2 have you been getting until now, and why
>>> do you believe you
On 4/10/2019 11:36 AM, Dimitri Maziuk via Mailman-Users wrote:
With a properly sandboxed application your security vulnerability has to
be a) exploitable through that application and b) able to break out of
the sandbox and wreak havoc to your host system.
Exactly.
(That said, given the
On 4/10/19 12:49 PM, Sean McBride wrote:
> On Wed, 10 Apr 2019 12:38:34 -0500, Dimitri Maziuk via Mailman-Users said:
>
>> How much support for python 2 have you been getting until now, and why
>> do you believe you will need it in the future?
>
> Fixes to security vulnerabilities basically.
On Wed, 10 Apr 2019 12:38:34 -0500, Dimitri Maziuk via Mailman-Users said:
>> Now that all support for Python 2 is supposed to go away in 2020 are
>> people going to move off of mailman 2?
>
>How much support for python 2 have you been getting until now, and why
>do you believe you will need it
On 4/10/19 10:36 AM, Matthew Goebel wrote:
> Hey,
>
> Now that all support for Python 2 is supposed to go away in 2020 are
> people going to move off of mailman 2?
How much support for python 2 have you been getting until now, and why
do you believe you will need it in the future?
--
Dimitri
On 4/10/19 8:46 AM, Carl Zwanzig wrote:
>
> I'll probably continue with MM2 until either it's ported
> to python3 or I stop running these lists.
The GNU Mailman project will never port Mailman 2.1 to Python 3.
--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area,
On 4/10/19 8:36 AM, Matthew Goebel wrote:
>
> Now that all support for Python 2 is supposed to go away in 2020 are
> people going to move
> off of mailman 2? I've been looking at mailman 3 and finding it hard to
> grok after using
> mailman 2 for many years. I haven't seen a discussion about
On 4/10/2019 8:36 AM, Matthew Goebel wrote:
Now that all support for Python 2 is supposed to go away in 2020 are
people going to move
off of mailman 2? I've been looking at mailman 3 and finding it hard to
grok after using
mailman 2 for many years. I haven't seen a discussion about this so
Hey,
Now that all support for Python 2 is supposed to go away in 2020 are
people going to move
off of mailman 2? I've been looking at mailman 3 and finding it hard to
grok after using
mailman 2 for many years. I haven't seen a discussion about this so I
thought I would
check and see if people
31 matches
Mail list logo
