kokada 26 minutes ago

From this example:

    lazy from typing import Iterator

    def stream_events(...) -> Iterator[str]:
        while True:
            yield blocking_get_event(...)

    events = stream_events(...)

    for event in events:
        consume(event)
Do we finally have "lazy imports" in Python? I think I missed this change. Is this also something from Python 3.15 or earlier?
  • rad120 3 minutes ago

    Python is such a weird language. Lazy imports are a bandaid for AI code base monstrosities with 1000 imports (1% of which are probably Shai Hulud now).

    And now even type imports are apparently so slow that you have to disable them if unused during the normal untyped execution.

    If Instagram or others wants a professional language, they should switch to Go or PHP instead of shoehorning strange features into a language that wasn't built for their use cases.

  • boxed 21 minutes ago

    Yes, 3.15+

brianwawok 36 minutes ago

I was so into Python for 10 years, was enjoyable to work in. But have deleted 100k+ lines this year already moving them to faster languages in a post AI codebot world. Mostly moving to go these days.

  • stuaxo 2 minutes ago

    This is straightforward in the first instance, but how do you see maintenance of those projects going forward - especially adding more complex features ?

    I can see one way forward being to prototype them in python and convert.

  • shankysingh 27 minutes ago

    Thats very intersting, If I may ask was it from professional projects or personal projects?

  • physicsguy 18 minutes ago

    Go is terrible for scientific/ML work though, the libraries just aren't there. The wrapping C API story is weak too even with LLMs to assist.

    Try and write a signal processing thing with filters, windowing, overlap, etc. - there's no easy way to do it at all with the libraries that exist.

    • LtWorf 16 minutes ago

      I think the purpose of go is to write CRUD. Stray from that and you're on your own.

  • mountainriver 22 minutes ago

    Same, I’m not sure how Python survives this outside of machine learning.

    All of our services we were our are significantly faster and more reliable. We used Rust, it wasn’t hard to do

    • prodigycorp 17 minutes ago

      the funny thing is that everyone, including myself, posited that python would be the winner of the ai coding wars, because of how much training data there is for it. My experience has been the opposite.

      • lsbehe 3 minutes ago

        The tons of python code would be great training data if there was any consistency across the ecosystem. Yet every project I've touched required me to learn it's unique style. Then I'd imagine they practically poisoned half the training set because python2 is subtly different.

      • lexicality 4 minutes ago

        a lot of the training data is either for python 2 or just generally very low quality

        • stuaxo a few seconds ago

          The quality issue doesn't seem unique to Python.

          The versioning issue I've seen across libraries that version change in many languages.

          I don't tend to hit Python 2 issues using LLMs with it, but I do hit library things (e.g. Pydantic likes to make changes between libraries - or loads of the libraries used a lot by AI companies).

    • LtWorf 17 minutes ago

      You can test on the device directly, without needing to recompile to try something.