Hey, I do Perl for money, you can't scare me.
this post was submitted on 13 Jun 2023
10 points (100.0% liked)
Python
6289 readers
2 users here now
Welcome to the Python community on the programming.dev Lemmy instance!
π Events
Past
November 2023
- PyCon Ireland 2023, 11-12th
- PyData Tel Aviv 2023 14th
October 2023
- PyConES Canarias 2023, 6-8th
- DjangoCon US 2023, 16-20th (!django π¬)
July 2023
- PyDelhi Meetup, 2nd
- PyCon Israel, 4-5th
- DFW Pythoneers, 6th
- Django Girls Abraka, 6-7th
- SciPy 2023 10-16th, Austin
- IndyPy, 11th
- Leipzig Python User Group, 11th
- Austin Python, 12th
- EuroPython 2023, 17-23rd
- Austin Python: Evening of Coding, 18th
- PyHEP.dev 2023 - "Python in HEP" Developer's Workshop, 25th
August 2023
- PyLadies Dublin, 15th
- EuroSciPy 2023, 14-18th
September 2023
- PyData Amsterdam, 14-16th
- PyCon UK, 22nd - 25th
π Python project:
- Python
- Documentation
- News & Blog
- Python Planet blog aggregator
π Python Community:
- #python IRC for general questions
- #python-dev IRC for CPython developers
- PySlackers Slack channel
- Python Discord server
- Python Weekly newsletters
- Mailing lists
- Forum
β¨ Python Ecosystem:
π Fediverse
Communities
- #python on Mastodon
- c/django on programming.dev
- c/pythorhead on lemmy.dbzer0.com
Projects
- PythΓΆrhead: a Python library for interacting with Lemmy
- Plemmy: a Python package for accessing the Lemmy API
- pylemmy pylemmy enables simple access to Lemmy's API with Python
- mastodon.py, a Python wrapper for the Mastodon API
Feeds
founded 1 year ago
MODERATORS
People designing Python surly didn't think of this. And when they see this now, the reaction would probably be "this should not be in any codebase, ever". But it can be. It is valid Python.
And it's a consequence of pushing features like unpacking and array comprehension and slice assigning and f-strings without fully exploring how they will interfere. One could argue that Python would be better of without some of these features.
But I don't blame them - exploring all possible combinations of features is just too much. The number of combinations grows exponentially and even if you have a fuzzer generating all possible expressions, you don't have enough time in your life to review all of the combinations.
Ultimately it's about the project leader what kind of code gets in.
You can write unmaintanable code in every language - some even ascending to esoteric levels, like JsFuck
Well, I'm saying that we could design a language where code would have to be formatted, so it would not be up to the project leader, at least syntactically.
I personally hate when code forces me to format things one way.
And there always be a way to go around formatting. Once I forced formatting on git server just to never worry about it.
Yeah, that's true, auto formatters will always have cases which format weirdly and have a nicer alternative.
But in the end, the formatting does not matter much, so we all benefit for it being formated one way, and one way only.
How would you format on git server? Create commits automatically, or ammend commits on push?
I... don't actually remember. It was a server side hook, I guess it tackled a new commit at the end. But it has been too long ago.
Nowadays I don't enforce such strict formatting, I just comment on MRs where I notice transgressions.
I never liked ammending commits. Had a colleague, team lead, who ammended other peoples commits. Ugh. That's when I started signing my own work.
I really don't see this as an issue, you could find this in any programming language. If you decide to abuse it, that's up to you