Hi,
I will need some "zombie-telnetlib" (so exactly the same API as
existing telnetlib)
because I maintain proprietary .deb (not "Debian packages") that need
to be installable without rebuild on Buster, Bookworm & Trixie.
I understand that "telnetlib3" / "exscript" are 'better/newer' API but
that does not fit the need.
Debian could also benefit from this zombie-telnetlib.
Should it be a native package or one with real upstream on PyPi ?
Greetings
Le ven. 2 août 2024 à 09:13, Louis-Philippe Véronneau
<pollo@debian.org> a écrit :
telnetlib:
* telnetlib3: a Telnet Client and Server library for python [2]
* exscript: automating network connections over protocols such as Telnet
or SSH [3]
Is anyone in the DPT interested in packaging and maintaining these libraries? They will likely be very useful for the 3.13 transition.>
From the stats I have, I currently count:
* 37 packages using telnetlib
Hi,
I will need some "zombie-telnetlib" (so exactly the same API as
existing telnetlib)
because I maintain proprietary .deb (not "Debian packages") that need
to be installable without rebuild on Buster, Bookworm & Trixie.
I understand that "telnetlib3" / "exscript" are 'better/newer' API but
that does not fit the need.
Debian could also benefit from this zombie-telnetlib.
Should it be a native package or one with real upstream on PyPi ?
Hi,
I will need some "zombie-telnetlib" (so exactly the same API as
existing telnetlib)
because I maintain proprietary .deb (not "Debian packages") that need
to be installable without rebuild on Buster, Bookworm & Trixie.
I understand that "telnetlib3" / "exscript" are 'better/newer' API but
that does not fit the need.
Debian could also benefit from this zombie-telnetlib.
Even today, 2 Aug 2024, is 2 months from the effective date. Please
file bugreports/issues to ask the packages you care about to migrate.
Also, even python3.11 is still there. Sure someone needing something expunged from 3.13 would be fine staying with 3.12?
Le ven. 2 août 2024 à 12:25, Blair Noctis <n@sail.ng> a écrit :
Debian could also benefit from this zombie-telnetlib.
How?
On the other hand, it would allow packages to continue relying on a thing
expunged from upstream, a maintenance burden for both Debian and upstream.
If we for example need to patch 10 dead-upstream projects to re-add telnetlib.py
& the corresponding stanza in d/copyright it might be less work
to scale it out in an external source package.
All of this depends on how many packages will need this telnetlib.
codesearch gives pages and pages of stuff with a lot of false positives
https://codesearch.debian.net/search?q=telnetlib&literal=1&perpkg=1&page=5
If we for example need to patch 10 dead-upstream projects
to scale it out in an external source package
Package authors should have had plenty of time to have this information propagated to them and migrate.
Package authors should have had plenty of time to have this information
propagated to them and migrate.
In general, stuff that works doesn't receive many updates.
And thinght might be
abandoned upstream but still work fine and be used as dependencies for other things.
If we for example need to patch 10 dead-upstream projects
which means the maintainer is now responsible for keeping it up to date. Including following Python upgrades and PEPs.
On Fri, 02 Aug 2024 at 19:40:59 +0800, Blair Noctis wrote:
Even today, 2 Aug 2024, is 2 months from the effective date. Please
file bugreports/issues to ask the packages you care about to migrate.
I agree with this part of what you said.
But, not this part:
Also, even python3.11 is still there. Sure someone needing something expunged
from 3.13 would be fine staying with 3.12?
In unstable, yes, at least temporarily; but not forever (and 3.11 has
already disappeared from testing).
Also, many Debian developers think of our stable releases as being our primary deliverable, with testing/unstable only being a tool that we
use to make the next stable release. In stable, we generally only have
one version of Python (for example Debian 12 has Python 3.11 and no
other version), because the Python maintainers and other core teams do not have the resources to security-support more than one branch for 3 years.
If we end up packaging these libraries, I think it should be clear that they won't be available for Forky (Debian 14). The last thing we want is
to maintain some deprecated zombie-libraries forever in Debian :(
The alternative to using asynccore might be major rewrites.
At this poinrt I think python is a joke.
Which is a popular opinion.
Still, asyncore was deprecated in 2016.
Which is a popular opinion.
Still, asyncore was deprecated in 2016.
Eh, software is 8 years old so it needs a full rewrite now?
Searching in regex mode with `import.*telnetlib path:*.py` should give more accurate results. But nevertheless:
https://codesearch.debian.net/search?q=telnetlib&literal=1&perpkg=1&page=5
to scale it out in an external source packagewhich is effectively going against Python upstream, allowing the thing to live
on, and people to say "it's still alive in Debian!"
Also, even python3.11 is still there. Sure someone needing something expunged from 3.13 would be fine staying with 3.12?
On 2024-08-02 20:40, Blair Noctis wrote:
to scale it out in an external source packagewhich is effectively going against Python upstream, allowing the thing
to live
on, and people to say "it's still alive in Debian!"
Also, even python3.11 is still there. Sure someone needing something
expunged
from 3.13 would be fine staying with 3.12?
The idea of having these libraries around for Trixie (and to remove them after the release) is to ease the 3.13 transition.
From my preliminary analysis, there are more than 600 packages that use
one of the stdlib that'll be removed in 3.13.
That is a lot of work and I doubt we'll have a successful transition
without this temporary measure.
On 2024-08-02 20:40, Blair Noctis wrote:
https://codesearch.debian.net/search?q=telnetlib&literal=1&perpkg=1&page=5Searching in regex mode with `import.*telnetlib path:*.py` should give more accurate results. But nevertheless:
I did this work already in Lintian:
https://salsa.debian.org/lintian/lintian/-/blob/master/lib/Lintian/Check/Languages/Python/StdlibDeprecation.pm?ref_type=heads
The current code for "uses-deprecated-python-stdlib" in Sid is flawed (see #1077324) but that will be fixed in the next Lintian release.
When that happens, I'm planning on making a MBF.
eamanu said he would make a list of upstream projects we could package, but if you have some time, getting a list of projects would be great.
On 2024-08-02 23:06, Salvo Tomaselli wrote:
Which is a popular opinion.
Still, asyncore was deprecated in 2016.
Eh, software is 8 years old so it needs a full rewrite now?
Please try to keep comments that are not productive to the current
efforts to some other channels?
That kind of email certainly doesn't motivate me to make things in
Debian better :(
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 349 |
Nodes: | 16 (3 / 13) |
Uptime: | 107:16:27 |
Calls: | 7,612 |
Calls today: | 3 |
Files: | 12,786 |
Messages: | 5,683,000 |
Posted today: | 2 |