80
Python's experimental JIT to be removed (lwn.net)
submitted 1 week ago by to c/programming@programming.dev
49 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 1 week ago (5 children)

I write Bash, Python and Rust. And I love writing in Python. It helped me so much and prefer it over almost any compiled language. Bash is completely different beast and not a replacement for Python and vice versa. Just because import works different in the language than the ones you like, does not mean the language is crap. For any questions about the import system, have a look at https://docs.python.org/3/reference/import.html#package-relative-imports .

It depends on how you use the language, as a scripting like language or a full replacement for compiled languages. I personally don't build packages with Python. BTW you can even compile Python scripts to binary machine code, and I don't mean bundles, but real compilation process. It even speeds up the performance of the program.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 2 points 1 week ago

    I write C# and Python, and C# is much more expressive than Python is and performs about 10x to 77x better. C# has much better pattern matching and has operators to deal with null and support for it in the type system. C# records can be serialized without issue (Python's built in JSON serializer can only serialize dictionaries). Althoigh variable scoping in C# isn't perfect (object patterns in if statements pollute the outer scope) variables at least aren't just function scoped like in Python. You can define user defined primitve types in C# which enables bettrr support for domain typing than what is possible in Python.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 1 week ago (3 children)

    Just because import works different in the language than the ones you like, does not mean the language is crap.

    No, it means it's unsuitable for scripting, if you need anything more than a single file. Better than Bash of course (not hard).

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 0 points 1 week ago (2 children)

    Python is good for scripting. If you start importing and having multiple packages involved with relative imports, that's no longer "scripting". We have standard library and the package manager for a reason. I think you are conflicting with full fledged applications and scripting.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 1 week ago (1 child)

    There are plenty of things that are "scripting", i.e. ad-hoc admin of other projects that aren't actually Python projects, where you want to share code between multiple scripts.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 0 points 1 week ago

    For such important projects, its not a big deal to just create Python packages. I don't get your point. You can use Python for scripting, and you can use it for full fledged programs or share package dependencies.

    My only problem is, that non standard package dependencies need to be installed by the end user, or sometimes the Python version does not match. These are the biggest issues to me.

  • permalink
  • fedilink
  • source
  • parent