From: "Sjujskij Nikolaj" <sterkrig@myopera.com>
To: gentoo-python@lists.gentoo.org, "Johan Bergström" <bugs@bergstroem.nu>
Subject: Re: [gentoo-python] On Python 2.5
Date: Mon, 20 Feb 2012 11:44:40 +0400 [thread overview]
Message-ID: <op.v9yvsqa2gczkqj@verkdatorn.npdb-network> (raw)
In-Reply-To: <9DBD9C2050C542488A7B46D83B6D31B4@bergstroem.nu>
Den 2012-02-20 09:04:45 skrev Johan Bergström <bugs@bergstroem.nu>:
> Good day all,
> with Python 2.4 being removed and all (anyone seen complaints about
> this, btw?),
> I'd like to discuss the removal of Python 2.5.
>
> Although 2.5 was one of those versions that started to be useful, I
> really see no
> reason to just keep it around "just because".
>
> Did a quick glance in the tree and couldn't find a package that only
> depended
> on python:2.5 specifically. Please correct me if I'm wrong.
>
> The question is therefore: why keep python 2.5 in tree?
There're quite a few people developing for Python 2.5 (for other target
platforms) using Gentoo. Just as I know one guy who programs for RedHat
(with Python 2.4) using Gentoo ~amd64.
Though I'm not developer, I hold that there's no call to remove old Python
versions from tree: declare them unsupported, or mask, but don't remove
until it's too burdensome.
next prev parent reply other threads:[~2012-02-20 7:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 5:04 [gentoo-python] On Python 2.5 Johan Bergström
2012-02-20 5:16 ` Mike Gilbert
2012-02-20 6:13 ` Matthew Summers
2012-02-20 8:51 ` Dirkjan Ochtman
2012-02-20 23:36 ` Jesus Rivero (Neurogeek)
2012-02-20 7:44 ` Sjujskij Nikolaj [this message]
2012-02-20 7:59 ` Johan Bergström
2012-03-04 16:13 ` Nikolaj Sjujskij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=op.v9yvsqa2gczkqj@verkdatorn.npdb-network \
--to=sterkrig@myopera.com \
--cc=bugs@bergstroem.nu \
--cc=gentoo-python@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox