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
[–] 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