| |||||||||||||
|
| |||||||||||||
Red Hat as the "next Redmond"Red Hat as the "next Redmond"Posted Aug 27, 2002 17:24 UTC (Tue) by rdieter (subscriber, #3460)Parent article: Red Hat as the "next Redmond"
Red Hat has pushed its users toward bleeding-edge versions of gcc while providing (and requiring) ancient versions of Python.Incorrect, about python anyway. RedHat 7(.3) includes both python(1) and python2.
(Log in to post comments)
Red Hat as the "next Redmond" Posted Aug 27, 2002 19:23 UTC (Tue) by jake (editor, #205) [Link] Well, except that you can't install python2 as python or all the redhatconfig programs break in heinous ways ... they require 1.5.2 for their python code (and expect 'python' to be 1.5.2) ... jake
Red Hat as the "next Redmond" Posted Aug 29, 2002 15:57 UTC (Thu) by iabervon (subscriber, #722) [Link] If you're using python 2 features in your scripts, you should probably invoke it with #!python2 anyway, so that it fails in a more obvious way for people who don't have 2.x
Red Hat as the "next Redmond" Posted Aug 27, 2002 19:23 UTC (Tue) by tjc (guest, #137) [Link] Red Hat has pushed its users toward bleeding-edge versions of gcc while providing (and requiring) ancient versions of Python.I'd like to comment further on the Python situation. The reason that Red Hat has used 1.5.2 for the longest time now is that some of the system tools that they ship as part of the 7.x series use Python, and Red Hat has a policy of not breaking compatibility within a major number series. Seeing that they're targeting the "enterprise" market they don't want to do this too often. So Python has been lagging far behind while waiting for gcc 3.2 to be released so that Red Hat can ship a new major number series. It was just bad luck that Python 2 wasn't ready for Red Hat 7.0.
Red Hat as the "next Redmond" Posted Aug 28, 2002 11:43 UTC (Wed) by MGPoolman (guest, #3469) [Link] .. . Incorrect, about python anyway. RedHat 7(.3) includes both python(1) and python2.
|
|
||||||||||||