clawlor
Joined 14 years ago
Joined 14 years ago
Given this, I tend to prefer a single, formatting-only commit when introducing formatting standards to an existing codebase. Otherwise, it’s difficult to take advantage of QOL features like auto formatting in your editor, or other formatting tools which tend to operate on entire files. Then PRs end up being mixed with formatting changes, which adds friction to the review process.
> Rather than build the commits that have been pushed to the branch the pull request is from, we build the merge between the source branch and the upstream branch.
https://docs.travis-ci.com/user/pull-requests/#how-pull-requ...
Good news on that front at least. PEP-895 [1] removes the need for `T = TypeVar(...)` boilerplate in Python 3.12.
- https://docs.djangoproject.com/en/4.1/ref/settings/#debug
Setting DEBUG = False doesn't cause in Internal Server Issue. The issue is caused by something else, having DEBUG = True just means Django will return a detailed error page, instead of a generic 500 error page.
IIRC, DEBUG = True also used to leak memory, which doesn't matter so much for local development, where it's intended to be used.
> Any identifier of the form __spam (at least two leading underscores, at most one trailing underscore) is textually replaced with _classname__spam, where classname is the current class name with leading underscore(s) stripped.
See https://docs.python.org/3/tutorial/classes.html#private-vari...
Obviously your choice depends greatly on budget + availability of hardware, as well as your desired resolution, but I'd suggest the 2070 or 2080 (maybe 2080ti?) as a good starting point.