Jukka Lehtosalo, David Fisher Static Types for Python PyCon 2017

แชร์
ฝัง
  • เผยแพร่เมื่อ 31 ธ.ค. 2024

ความคิดเห็น • 17

  • @ruthlessadmin
    @ruthlessadmin 7 ปีที่แล้ว +1

    Huh. I did not know you could annotate types like that. Very cool!

  • @TheJaniable
    @TheJaniable 4 ปีที่แล้ว +1

    I wish I knew about this before writing 5 entire projects in Python.

  • @harshilrastogi
    @harshilrastogi 6 ปีที่แล้ว

    I can't find the slides at the above-mentioned sources. Can anyone please point me the link?

  • @IamEchelon
    @IamEchelon 6 ปีที่แล้ว

    Python needs a better way to go about doing this because currently this clutters the code up significantly. I would suggest something more Haskell-esque.

  • @jonbarker6979
    @jonbarker6979 7 ปีที่แล้ว

    print(type(entries)) is how I do it. Why is this better?

  • @adamcunnington2593
    @adamcunnington2593 7 ปีที่แล้ว +1

    The introduction is completely flawed. It's completely clear what the code does - or if it isn't, that has nothing to do with static vs. dynamic types. The whole point is, you shouldn't care what the type is. It's irrelevant; the attributes and methods define the behaviour. Talk about completely missing the point.

    • @desprit
      @desprit 6 ปีที่แล้ว +3

      No it is NOT clear. And yes, you SHOULD care about typing.

    • @RicardoSuarezdelValle
      @RicardoSuarezdelValle 9 หลายเดือนก่อน

      Saying this just demonstrates you have never worked with a big enough codebase, just the amount of times I've had to write print type(someUnclearCrap) is worth the strict types

  • @RubenKelevra
    @RubenKelevra 7 ปีที่แล้ว

    Well, the introduction is bullshit, your ide can show you the definition of everything, if you use pycharm or similar, just a right click away.
    They just mess up python...