Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #13239
| From | "Bailey, Josh" <josh@vandervecken.com> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | python3.5 + oldstable dilemma |
| Date | 2021-03-01 04:20 +0100 |
| Message-ID | <BNHge-1AW-5@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
Hi all, I'm a maintainer for a python based SDN network controller, FAUCET. One of the platforms we've been supporting to-date is python3.5/oldstable. Of course, now, python3.5 is EOL. To some degree we can keep building our package under python3.5, but now not all of our dependencies (like pyyaml) build or are even released for 3.5 anymore. That's an issue as there are security vulnerabilities that are now difficult to address. Given that oldstable will be around until 2022, does that mean python3 as python3.5 will live on in oldstable until then? I can understand the case for not adding a newer python3 version, but also OTOH addressing security vulnerabilities over the LTS window will probably only get harder. Any advice appreciated,
Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar | Unroll thread
python3.5 + oldstable dilemma "Bailey, Josh" <josh@vandervecken.com> - 2021-03-01 04:20 +0100 Re: python3.5 + oldstable dilemma Jeremy Stanley <fungi@yuggoth.org> - 2021-03-01 14:20 +0100 Re: python3.5 + oldstable dilemma Giacomo Catenazzi <cate@debian.org> - 2021-03-01 15:30 +0100
csiph-web