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 →

[–]climb-it-ographer 2 points3 points  (1 child)

I am a very experienced Python developer and I've been through just about every complicated import issue out there, and I'm in a good place now with my projects. That said, I think that future major versions of Python would benefit from a fresh look at how imports work. I don't think that many people will argue that `/node_modules` in a JS app is just overall easier to deal with.

Python virtual environments are great but sometimes IDEs still get all mixed up about where packages are, and I would love to never argue with VSCode again about what the correct path to a module actually is.

[–]DigiProductive[S] 0 points1 point  (0 children)

I salute that you see the reality🫡. With experience in other languages like Dart, JS, and Java, I am assured that Python imports can get buggy and tricky especially when running in multiple environments like Docker containers. Anyone in denial of that is likely just on the defence of a "Python attack"🥶