…ed from the new /SearchSeriesResults endpoint

Add flake8 linting task

Fix code formatting in setup.py

custid to cust_id
lowername to name_lower
shortname to name_short

SubSessionData.league_id
SubSessionData.league_season_id
SubSessionData.points_type
SubSessionData.reserve_status
SubSessionData.season_name
SubSessionData.season_name_short
SubSessionData.series_name
SubSessionData.series_name_short
SubSessionData.session_name
SubSessionData.special_event_type_text
SubSessionData.time_start
SubSessionData.time_start_sim
SubSessionData.track
SubSessionData.track_config

…ed it. Added parse_encode to objects with newly completed documentation to see the data

We previously had the help message inside the error we are raising, but
we really want to be logging that as that is where users will be looking
for help. Inside the error we can just dump the entire response. This
might be absurd and too much content, but it at least allows them to
make decisions based on this if they want.

We currently raise a `UserWarning` when we fail auth which isn't very
descriptive and doesn't tell us what actually failed.

This is a more accurate error for what is actually happening and lets us
save the actual response in case the user wants to do something with it.

Add a check for empty event results

Bump version to 0.1.1 for a release

Improve Login Flow

Fixed issue #74 (string replace is no longer required)

This is how we will model the data we get back from the league standings
endpoint.

This allows us to get the standings for a leage given the league ID and
league season ID. This can take in more parameters, but those are
documented on the URL, and I don't really see the use, so they can be
added later.

This does not include previous and next race, because I think those
might require some more thought, but this does give us the basics for
gettings the seasons for a league.

This lets us get the seasons for a given league so we can use them to
query leaderboard.

Add League Standings Endpoint

Add League Seasons

This will have `+` in all the spaces, as well as other weird encoding
things that iRacing uses, so we want them removed.

This is how we can get some specific data about a league by ID.

We want to represent all the data we can get from iRacing about leagues.
This only omits the data about images, since we don't have access to
the actual image anyways.

This is how we can get some basic data about a league from an ID.

This was just a typo, looks like a bad copy/paste. `pos` is the field
that represents position.

Fix position

…into endpoint-change