I just found a bug in my code that is related to this, and wanted to circle
back...
I keep forgetting that these are not the same comparison on Postgres:
Foo != True
Foo IS NOT True
They match as follows:
`!= True` = [False, ]
`IS NOT True` = [False, NULL]
--
You received
There are two approaches:
1. disable E711 and E712. this is what I'm doing for the project itself.
2. use == sqlalchemy.null(), == sqlalchemy.true(), == sqlalchemy.false()
instead of None, True, False. This might be a better idea for everyone else
who cares about super-clean code.
On Jul
thanks. I already added `# noqa` to those lines.
that pep8 test is actually bad, digging into the docs, it's actually
recommending the "worst case" format. there's a bunch of debate on it in a
github ticket.
do you know of any other odd behaviors?
--
You received this message because you a
You can try adding "# nopep8" or "# noqa" at the end of any line to suppress
pep8/flake8 messages for that line.
There may be more in the docs about this about how to suppress which errors
specifically:
https://pypi.python.org/pypi/flake8
--Mike
From: sqlalchem
