<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">On Sun, Apr 7, 2013 at 6:53 AM, Christian Tismer <span dir="ltr"><<a href="mailto:tismer@stackless.com" target="_blank">tismer@stackless.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Hi Skip,<div class="im"><br>
<br>
On 07.04.13 14:10, Skip Montanaro wrote:<br>
</div></div><div class="im">
<blockquote type="cite">
<pre>I started writing this last night before the flurry of messages which
arrived overnight. I thought originally, "Oh, Skip, you're being too
harsh." But now I'm not so sure. I think you are approaching the
issue of 2.7's EOL incorrectly. Of those discussing the end of Python
2.7, how many of you still use it in your day-to-day work? Have any of
you yet to move to Python 3? It sounds like many people at PyCon are
still 2.x users.
Where I work (a trading firm that uses Python as just one of many
different pieces of technology, not a company where Python is the core
technology upon which the firm is based) we are only just now
migrating from 2.4 to 2.7. I can't imagine we'll have migrated to
Python 3 in two years. It's not like we haven't seen this coming, but
you can only justify moving so fast with technology that already
works, especially if, like Python, you use it with lots of other
packages (most/all of which themselves have to be ported to Python 3)
and in-house software.
I think the discussion should focus on who's left on 2.x and why, not,
"yeah, releases every six months for the next couple years ought to do
it."
</pre>
</blockquote>
<br></div>
when I read this, I was slightly shocked. You know what?<br>
"""<br>
<span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:start;font-style:normal;display:inline!important;font-weight:normal;float:none;line-height:21px;text-transform:none;font-size:15px;white-space:normal;font-family:Arial,Verdana,Geneva,'Bitstream Vera Sans',Helvetica,sans-serif;word-spacing:0px">We are pleased to announce the release of<span> </span></span><strong style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:start;font-style:normal;line-height:21px;text-transform:none;font-size:15px;white-space:normal;font-family:Arial,Verdana,Geneva,'Bitstream Vera Sans',Helvetica,sans-serif;word-spacing:0px">Python 2.4, final</strong><span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:start;font-style:normal;display:inline!important;font-weight:normal;float:none;line-height:21px;text-transform:none;font-size:15px;white-space:normal;font-family:Arial,Verdana,Geneva,'Bitstream Vera Sans',Helvetica,sans-serif;word-spacing:0px"><span> </span>on November 30, 2004.<br>
"""<br>
<br>
I know that companies try to save (time? money?) something by not
upgrading<br>
software, and this is extremely annoying.<br></span></div></blockquote><div><br></div><div style>You're not looking at it from the users perspective. They see:</div><div style><br></div><div style>"we are pleased to announce that RHEL 4 will be supported until the year 3325"</div>
<div style><br></div><div style>and continue to use everything that it ships with and only that. its their own loss for not investing in maintaining infrastructure of their own rather than investing in a support contract from their vendor but it is a valid choice none the less. it has nothing to do with what python-dev chooses to do release wise.</div>
<div style><br></div><div style>I think this thread has already settled the question that Benjamin set out to ask: it doesn't matter when we stop issuing bug fix releases of 2.7, users will exist long enough for even today's deniers to hate them for using an old version.</div>
<div style><br></div><div style>If Benjamin wants to see bug fix releases made for two years, great! If not, no big deal either. We as python-dev are a bunch of volunteers and it is up to each one of us if we'll bother to continue back porting fixes or investigating bugs on 2.7 or not. I strongly suspect that many of us will only continue to do so as long as 2.7 is relevant to our day jobs.</div>
<div style><br></div><div style>We don't need to close the 2.7 branch to commits and bug fixes. Ever. But most of us will stop caring about making changes to it at some point. For me that point is after 3.4.</div>
<div style>
<br></div><div style>my 3 cents,<br></div><div style>-gps</div></div></div></div>