Pysmashgg

Latest version: v1.2.0.1

Safety actively analyzes 685670 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 2

1.2

- I figured I've been doing so many minor updates we'll call this a new version
- Added `tournament_show_by_owner(owner, page_num)`
- Added `startAt` to `tournament_show_event_by_game_size_dated`

1.1

- Added game results (and then fixed a bug with them)
- Added more fields for event_show_sets
- Bug fixes for like 20 different functions (Smashgg API is trash sometimes, I literally had to add a sort for like 1/10th of the events to even work)
- Added auto_retry function built into SmashGG object, for if you get denied for requesting too much you can auto-retry and it will increase the time it waits every time before a request
- Added character data to event_show_sets, functionality to others will be added later
- (THERE ARE PROBABLY MORE BUGS PLS LET ME KNOW IF YOU FIND ANY)

1.0

- Added a bunch of commands
- `league_show(league_name)`
- `league_show_schedule(league_name, page_num)`
- `league_show_standings(league_name, page_num)`
- `tournament_show_by_country(country_code, page_num)`
- `tournament_show_by_state(state_code, page_num)`
- `tournament_show_by_radius(coordinates, radius, page_num)`
- `tournament_show_players_by_sponsor(tournament_name, sponsor)`

- Adjusted return fields of a few functions (this WILL be the last time fields are modified for existing functions -- I cannot guarantee new return fields will not be added, but they won't affect your current scripts from now on)
- `tournament_show(tournament_name)`
- `tournament_show_event_brackets(tournament_name, event_name)`
- `tournament_show_with_brackets_all(tournament_name)`
- `tournament_show_events(tournament_name)` (just adjusted it from a dictionary with one entry (which was an array) to an array -- this aligns with the rest of the functions like this)

- Implemented tests

- Added lots of error checking (I was missing quite a bit, oops)

- Reordered filters so it has the same order as the commands in smashgg.py

0.8

- Ability to have event as event_id (if you have it saved)
- This was done with a whole new set of commands, the same name as the ones before but with `event_` instead of `tournament_` at the start
- List of Commands:
- `event_show_sets(event_id, page_num)`
- `event_show_entrants(event_id, page_num)`
- `event_show_entrant_sets(event_id, entrant_name)`
- `event_show_head_to_head(event_id, entrant1_name, entrant2_name)`
- This is done if you have a lot of data from one tournament, because currently with how smashgg's API works, it needs to send a query to get the event_id if you have the name of the tournament and the event -- In short, this saves a query, which will make you be able to do pagination faster
- For example, if you need to go through 30 pages of a tournament result, using `event_`, you'll only be sending 30 queries instead of 60 with `tournament_`
- This is encouraged to be used

- Added `tournament_show_event_id(tournament_name, event_name)` to retrieve just the event_id

- Added `tournament_show_event_by_game_size_dated(size, videogame_id, after, before, page_num)` which finds all tournaments with events (of a certain game) of a minimum size in between two unix timestamps

0.6

**Error Checking Update**

- All functions should now work with in progress and upcoming tournaments

- Added boolean value `completed` to functions involving sets, letting you know if the sets have been completed or not

- Renamed `tournament_show_event_brackets` from `tournament_show_events_brackets`

- Updated `exceptions.py` because I wrote too many exceptions

- Bug fixes

0.5

**Reorganization / Player Update**

- Added 3 new commands, `player_show_info`, `player_show_tournaments`, and `player_show_tournaments_for_game` (Usage is in README)

- Reorganized code by creating new files:

- `api.py`
- `b_queries.py`
- `brackets.py`
- `p_queries.py`
- `players.py`
- `t_queries.py`

- Made code more readable in some places

- Got rid of unecessary imports

(We skipped right to v0.5 because I combined v0.4 (reorganization) with v0.5 (player))

Page 1 of 2

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.