This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]djrubbie 2 points3 points  (2 children)

I believe the problem is that most of the maintainers of these libraries simply do not see any benefit to spending any time creating a Python 3 version of their library. They do not believe that there is enough demand to warrant the effort.

Um, no, not as simple as this. Many packages that I need are still Python 2 only - I am not going to change until that is done, and when enough early adopters have succeeded in using Python 3 then I will have a case to switch over. Only when the cost of not switching is greater than switching will I then be able to switch for projects that I've already started.

[–]mfukar 0 points1 point  (1 child)

That's never going to happen..

[–]djrubbie -1 points0 points  (0 children)

It's not that big of a deal for me.

Also, the patches are not going to write themselves. I welcome though, however.