howlongtobeatpy 1.0.5

Python 3.6 has been deprecated for some time now, so I updated the project tests to Python 3.9 with a couple of fixes

Full Changelog: 1.0.3...1.0.5

howlongtobeatpy 1.0.3

Fixed a required package that was creating errors

Full Changelog: 1.0.2...1.0.3

howlongtobeatpy 1.0.2

This new release fix the time in the Entry to float as requested from #17 , so the user can now decide if and how to round or convert to int that value

Full Changelog: 1.0.1...1.0.2

howlongtobeatpy 1.0.1

This new version of the API was redone to be compatible with the new response, the HTML parser was removed because now the request return a JSON which is partially parsed to fill the entry, and left inside of it for full access to data.

Unluckly now there are less values directly available as it was before and more user-work is required to use the API.

For any change or problem please open an Issue, a Pull Request or a Discussion

What's Changed

• New version of the API parsing the JSON in #15

Full Changelog: 0.1.22...1.0.1

howlongtobeatpy 0.1.22

This is a small release after the fix #10 for 0.1.19

I fixed the url to the game page which was wrong since I changed the game url in the code

Full Changelog: 0.1.21...0.1.22

howlongtobeatpy 0.1.21

This is a small release after the fix #10 for 0.1.19

I basically fixed the issue from sonarcloud scanner and updated its configuration to the correct python version

Full Changelog: 0.1.20...0.1.21

howlongtobeatpy 0.1.20

This is a small release after the fix #10 for 0.1.19

I cleaned the code a little bit, everything looks to be working fine from the test
If you encounter any issue please feel free to open an issue or a discussion

howlongtobeatpy 0.1.19

Fixed #10

howlongtobeatpy 0.1.18

This version add the game title suffix in HowLongToBeatEntry, named game_name_suffix

This is not present in every game
Is present with games such as "God of War", where there is a suffix "(2018)" to indicate the specific game

For more informations see #8

howlongtobeatpy 0.1.17

Requests were reporting error 403

So added User Agent to requests header to avoid error 403
This is done using the library: fake-useragent
Requests might become a bit slower, because the library has to download and cache the list of user agents to randomize