Hey all. First post - w00t! Realistically I'm unlikely to use P3K in production code until it comes as part of a redhat distro. Not doubt it will be in redhat ES12 sometime around 2020 :) I had a fair amount of pain installing python 2.5/mod_python on a bunch of 64-bit RHES4 machines recently. Don't fancy going through it again unless I really have to.
Karl On Fri, Dec 5, 2008 at 2:51 PM, Michael Twomey <[EMAIL PROTECTED]> wrote: > > Even 2.6 is going to be a "bit new" for a while. For example numpy > won't build with it at all until the next release (1.3). > > mick > > On Fri, Dec 5, 2008 at 10:01, Daniel Kersten <[EMAIL PROTECTED]> wrote: > > > > I had thought of that right after I sent the email - obviously I can't > > switch until all the libraries I use are supported (so pygtk, > > matplotlib, numpy and scipy at a minimum). > > > > 2008/12/5 David Wilson <[EMAIL PROTECTED]>: > >> > >> 2008/12/4 Daniel Kersten <[EMAIL PROTECTED]>: > >>> > >>> Has anyone used it yet? Whats it like? Who's planning on moving from > 2.x? > >>> > >> > >> It's unlikely that it will see much uptake for the coming months if > >> not years, and probably not by many companies until they are forced to > >> (i.e. 2.x is no longer getting maintained). > >> > >>> I'm about to start writing some Python code for extracting data from > >>> log files for reliability testing in work, but I'll be doing it in > >>> Python 2.6, so I'm curious if other people are going to switch > >>> immediately or stick with 2.6 for a while longer. I intend on checking > >>> out 3.0 fairly soon (over the weekend maybe) and switching for > >>> personal projects. > >> > >> I'd suggest sticking to 2.x for the time being, even for hobby type > >> code, since at the present time practically none of the third party > >> libs have 3.0 support, never mind being tested and stable. > >> > >>> > >>> On a side note, how does execution performance of 3.0 compare to 2.6? > >>> (Not that its an issue for me, but I am curious) > >> > >> Significantly slower for some operations, particularly on integers. As > >> noted in the 3.0 What's New document, 3.0 is about 10% slower running > >> PyStone (this is part of the stdlib as test.pystone apparently). > >> > >>> > >>> -- > >>> Daniel Kersten. > >>> Leveraging dynamic paradigms since the synergies of 1985. > >>> > >>> > > >>> > >> > >> > > >> > > > > > > > > -- > > Daniel Kersten. > > Leveraging dynamic paradigms since the synergies of 1985. > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Python Ireland" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.ie/group/pythonireland?hl=en -~----------~----~----~----~------~----~------~--~---
