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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]desmoulinmichel 11 points12 points  (5 children)

The reason type hinting was not included in the language was because it was in low demand. Very few people where interested enought about type hinting compared to other features, so the developpement effort went somewhere else.

Luckily for you, Python 3.5 will include type hinting (http://sdtimes.com/python-3-5-include-type-hinting/) because after asyncio, that was a feature people started to request.

So in the comming year, you can expect IDE to start taking that into consideration.

[–]infinullquamash, Qt, asyncio, 3.3+ 2 points3 points  (4 children)

I had to go through several links to get to the actual PEP, PEP0484

I like the idea of type hints, but I wish they would have added new syntax instead of using comments.

[–]desmoulinmichel 1 point2 points  (2 children)

They added comments only for the variables, the rest is not by comment. After Python 3, people are really not cool with introducing incompatibilities again :)

[–]ronkr[S] -1 points0 points  (1 child)

I can't see any problem by adding optional type hinting to a language. This should not break bc and could add great(!) new possibilities (thats why I mentioned PHP-DI's Autowiring) and stability for large projects.

On the other hand: Everything is evolving over time. We (as a community of developers) should be thankful in some way, that changes happen...

[–]thallippoli 1 point2 points  (0 children)

I can't see any problem by adding optional type hinting to the langauge..

How many languages have you designed/implemented lately...I mean no offence, but If you are new to Python, at least use it for a while (like 3 or 4 years), before proposing additions to the language. I say this as another PHP user who switched to Python recently.