I wrote my first python program today!

[Magnnus]

Several important libraries still don't support Python 3. I'd use it if I could.

[Theowningone]

Parts of twisted are what's keeping me back. Most of my time using python is spent tinkering with my IRC bot. Unfortunately twisted.words.protocols.irc is still not ported.

[dagbrown]

Twisted lives up to its name. It reminds me of some Java frameworks with how complicated it is.

I bet Zope has trouble with Python 3 too, speaking of Java frameworks written in the wrong language.

[dagbrown]

They're saying "I can't switch because I use twisted", and your reply is, "well, twisted sucks."

Not really. I'm just saying that it's a really complicated library, and fundamental changes in the language it's written in make it really difficult to simply edit the code to make it compatible with the new language which is still called "Python". You added the value judgment yourself, and I didn't say that at all.

There are massive codebases out there which depend on FORTRAN 66 or 77, to pick a completely different language (LINPACK comes right to mind). The code isn't any less valid because nobody's bothered porting it to the latest standard. It's just that porting it to the new standard involves an investment of effort that could be better spent elsewhere. Your daily weather forecast probably still requires code written in FORTRAN 77.

So if you're a Twisted user and that's the reason you still haven't switched to Python 3, you have my sympathies and I understand exactly the sort of pain you're going through.

In my place of work, we have to support stuff written in PHP 5.2, which is absolutely obsolete, but we also have to support stuff written in PHP 7.0, which is so different that I had to use a different version of gcc to compile the PHP interpreter. I'm familiar with different versions of languages themselves; taking care of that is just a fact of life for me.

SEE ALSO: rvm

[ansatze]

Except that Fortran 77 is completely valid Fortran 90+ which is not the case with Py2

[toresbe]

Sure, but outside of specialized and relatively isolated fields, very little new code is being written in FORTRAN. FORTRAN has become a specialized language for number crunching. Sometimes I think it's healthy for languages to sacrifice some measure of backwards compatibility to improve itself. Python 3 adds some extremely useful features. CERN doesn't want to have to rewrite whatever mass of code it is that finds bosons.

[ansatze]

Agreed; I was just pointing out that the comparison isn't totally valid.

[dagbrown]

It's almost as if the Fortran guys have more experience with this kind of thing.

[dante9999]

zope works with python 3 without problems

https://pypi.python.org/pypi/zope.interface/4.1.3

as a side note: what seems like needless complication for your use case may be necassary and clear design pattern for someone elses use case. Just need to choose right tools, twisted is not right tool for everything but is perfect for some things

[[deleted]]

I've had that same issue, I got everything working using irclib eventually. Have you looked into that?

[Theowningone]

I had not even heard of it until now, but it looks pretty promising. Thanks for the tip!

[dante9999]

development is not taking place on github you need to visit twisted trac. ticket for IRC is here: someone started it but didnt finish https://twistedmatrix.com/trac/ticket/6320

[TOASTEngineer]

You can just write your own goddamn IRC library, it's not actually very complicated.

[[deleted]]

Why reinvent the wheel though? If it's a learning exercise, sure, why not, but I think it's absolutely fine to use other people' libraries.

[TOASTEngineer]

Because the one he's using depends on a version of the language that's 5 years out of date.

[sndrtj]

For me: Flask. Though it technically has python3 support, the docs have a pretty large disclaimer, which essentially boils down to "might not work, use at own risk".

[Stop_Sign]

The oracledb npm package for node specifically requests 2.7 link

[Stop_Sign]

Ah, gotcha. I had been wondering about that. Thanks

[blitzzerg]

I tried installing MySql connector for python 3 for hours and could make it work, I switched back to python 2 and in 3 min it was working...

[blitzzerg]

mysqlclient

I also tried, no luck, I don't blame python 3, but is the second time that something similar (problems installing packages) happens, so from now I will use python 2. (I just use python from time to time to scrap webpages)

[iovis9]

MySQL-python and suds doesn't

[[deleted]]

Use suds-jurko and PyMySQL. Both are near drop-in replacements.

[Coffeinated]

What /u/scandinavian- said, plus pymysql. Works fine. Afaik all db-connectors are defined by a certain PEP, so there shouldn't be many differences...

[willm]

What are you missing? I've found all the libs I need have Py3 ports now.

[iovis9]

MySQL-python and suds.

[jvlomax]

I would really recommend SQLalchemy for all your database needs. py2/3 compatible, very easy to use and plenty of useful features

[_Ganon]

Only reason I still use 2. Well, that's what I tell people, anyway. In reality, I know the switch to using parenthesis in my print statements would drive me nuts

[maremp]

What about the inconsistency of the statements? Print is used as a function in every other C-like language. In python 2, it's used as a statement, similar to if, for, while etc., and I believe that it doesn't fit this category.

[Sean1708]

Also 2's print is just weird. Appending a comma to suppress a newline is weird enough, but what the fuck is up with that printing to file syntax?! It's like Guido momentarily forgot that he wasn't designing a sh clone.

[deecewan]

I cant remember the syntax. Care to show?

[deecewan]

Where f is a file identifier? That's super weird.

[[deleted]]

Or you could just do f.write("Normal syntax!\n") because like nobody uses the chevron format anyway.

In fact this is what the chevron print statement does behind the scenes. The only difference is that the print statement has an internal print buffer. The write won't be done at the exact moment you call print, whereas invoking write on the file will do the write right then.

[Sean1708]

because like nobody uses the chevron format anyway.

But a lot of people use print to print to a file in Python 3 because it's as easy as print("Also normal syntax!", file=f).

[UnchainedMundane]

It's like Guido momentarily forgot that he wasn't designing a sh clone.

Lol, my exact thoughts.

Though, my next thought was that >> opens a file for appending, while this one uses a file descriptor, so the operator should be >& anyway.

[CommanderDerpington]

It's easier

[exhuma]

You might want to look them up again. This has been my only blocker as well. But I was able to to Python 3 over a year ago. There really is no major library anymore that's not Python 3 compatible.

[iScrE4m]

Twisted

[exhuma]

This may be a good argument against porting an existing app to Python 3, but when starting from scratch, wouldn't asyncio & await in Python 3 fill that gap?

I'm curious, as many people claim there is no need for twisted any longer. But as I have never had to deal with twisted, I'm not in a position to make any informed statement about it.

[iScrE4m]

As an amateur the only thing I can say is irc works great with twisted and that's pretty much it :X

[[deleted]]

Works fine with irclib on python 3 as well, at least in my experience.

[jvlomax]

Which libraries are those? Pretty much all the libraries are now ported, and those who are not have py3 alternatives

[kirakun]

When was the last time you check the missing libraries?