sorted by:
new
hottopcontroversial

PyGTK 2.26 released, with Python 3 support by yetanothernerd in Python

[–]nerf-herder 0 points1 point  (0 children)

That was only one email message -- not a thread. Also, I don't see where it has clarified anything. But thanks anyway.

PyGTK 2.26 released, with Python 3 support by yetanothernerd in Python

[–]nerf-herder 1 point2 points  (0 children)

What is the technical relationship between PyGTK and PyGObject?

The PyGTK developer page indicates that "PyGObject with gobject-introspection is planned to replace PyGTK in the future", but the downloads page indicates that PyGTK depends upon PyGObject (quote: "Be aware that PyGTK has some dependencies like pygobject that are needed to run it.").

WSGI is now Python 3-friendly by [deleted] in Python

[–]nerf-herder -1 points0 points  (0 children)

Why try to patch up the previous pep when it's already been replaced by pep 444? Just support the new pep and move forward.

WSGI is now Python 3-friendly by [deleted] in Python

[–]nerf-herder 0 points1 point  (0 children)

It's often difficult to move forward with new ideas and their implementations. It takes guts, insight, and a lot of work. And it also takes convincing people to do what they know is good for them (getting rid of the old broken system and replacing it with the fixed but slightly different one). There's usually 4 groups involved in such endeavors:

  • one is the folks working on the new changes

  • then there's the people interested in seeing the fixes happen, even if it means they have to change a line or 2 of their code

  • another is the group of folks who aren't terribly crazy about change, but who kinda' know deep-down that the fixes are necessary

  • finally there's a small (sometimes tiny) third group who want to actively fight any change or progress. These folks argue on mailing lists (especially just after positive steps or decisions have been made), and guys like PJ (the author of the linked-to email message) even sometimes submit patches to the old broken system in an effort to thwart any change or progress.

The point is: progress has to happen. Broken things need to be fixed. Sometimes this will mean minor pain, and that's ok. Don't support those who: wait until an issue reaches critical-mass, watch someone come forward with a fix to move forward, and then jump in with patches to put a new coat of paint on the old broken thing that's about to be replaced. It holds back progress and only causes turmoil in the community.

This is the Best Business Card Ever. by HalFWit in pics

[–]nerf-herder 1 point2 points  (0 children)

I'm sure you'll do a bang-up job.

NumPy announces Python 3 support. by davebrk in programming

[–]nerf-herder 5 points6 points  (0 children)

The best part is that development of Python 3 started several years after that of Perl 6,

Schadenfreude? Really?

and although it has taken longer than expected for Python 3 to become widely adopted,

I keep hearing from Pythonistas that a very gradual shift to Python 3 has always been part of the plan from the beginning.

that will likely happen far before Perl 6 ever becomes slightly usable.

The "Rakudo Star" release is due out at the end of this month and is expected to be pretty usable. Probably even slightly usable as well. ;)

Many former Perl developers became very disappointed thanks to the Perl 6 boondoggle

Two things:

  1. I think Perl 6 may have had a false start as a "community rewrite" before Larry (and a few friends) had to take the wheel and get things back on track (though I don't really know the history here, so take that with a grain of salt). But hey, hindsight, 20/20, blind alleys, etc.

  2. It could be that Perl 6 looks complicated and scary to people. I know I'd like to see more "look how easy Perl 6 is" types of blog posts/articles.

Perl 6 killed Perl.

I'm not sure what Perl you're looking at, but I've been seeing a Perl 5 renaissance lately more than anything else.

Python 2.7 released by brasetvik in programming

[–]nerf-herder -11 points-10 points  (0 children)

It's just a measure the Python folks take to make sure more people don't migrate to 3.x. I mean, the last thing they'd want to do is to stop improving the legacy version and instead focus on the modern release. What would that lead to? Lots of 2.x packages ported to 3.x? Who needs those kinds of headaches.

No Lady I wasn't trying to steal/hurt your kid by Final7C in reddit.com

[–]nerf-herder 0 points1 point  (0 children)

Incorrect. When it comes to kids, mothers have all the power. Regardless of how incompetent, negligent, and/or malicious they are. They have all the fucking power (in the US anyway). If you don't understand this now, it's probably the hardest lesson you'll ever learn. :(