GitLab

django2 requires you explicity define what happens when objects are deleted-- this used to default to cascade, and the whole project sort of assumes you're not deleting anything

alphabetized requirements and upgraded to roughly late 2018, in line with django 2.1, which we're using as a stepping stone to the even later 2.2 lts goal

wow we really had some kickass testing back in the day, didn't we... except block actually imports correct exception name

seems I indented a bunch of stuff an extra level so that lovely pythonic whitespace meant the changed code wasn't seen as identical... rip

added sessions-based authentication for the API... essentially, you may only access this information if you are logged in

essentially all listing information is made available on the listings page, minus bidding or user information

again something that's missing a .user-- did olde versions of django just imply user relationships? wth

added initial api views to bookshare; will need to determine what other information, if any we wish to expose for the first go round

turns out that we needed to bump up a few point releases for django rest framework to work nicely with django 1.10

- also start to figure out how to access messages from model validators