8 Commits

Author	SHA1	Message	Date
Trenton H	6f163111ce	Upgrades black to v23, upgrades ruff	2023-04-26 09:35:27 -07:00
Trenton H	3bcbd05252	Fixes ruff not running isort against the codebase	2023-04-26 09:35:27 -07:00
Trenton H	ce41ac9158	Configures ruff as the one stop linter and resolves warnings it raised	2023-04-01 17:03:52 -07:00
kpj	fc695896dd	Format Python code with black	2022-02-27 15:26:41 +01:00
dadosch	efc57852d1	remove atomic=False where it is obviously not needed)	2018-08-29 00:37:07 +02:00
dadosch	91cecd47af	apply some patches from @brookst	2018-08-29 00:04:48 +02:00
Daniel Quinn	8bc2dfe4c6	Django migrations doesn't account for PostgreSQL completely ... This was a weird bug to run into. Basically I changed a CharField into a ForeignKey field and ran `makemigrations` to get the job done. However, rather than doing a `RemoveField` and an `AddField`, migrations created a single `AlterField` which worked just fine in SQLite, but blew up in PostgreSQL with: psycopg2.ProgrammingError: operator class "varchar_pattern_ops" does not accept data type integer The fix was to rewrite the single migration into the two separate steps.	2017-02-18 17:55:52 +00:00
Daniel Quinn	d1c811555c	Created a Sender model	2016-01-11 12:52:19 +00:00