Hi @SrdjanNikitovic, we have forked this repo and updated uap-core here. You can do the same or use our fork.

Related issue #66.

https://github.com/soon/uap-python-next it looks like this project/package may have done the same

Good to see that @soon attempted to contribute back the changes needed. I stopped bumping commits from uap-core because tests started to break, and I don't have the bandwidth or capacity to fix them. Bumping versions is trivial and I was doing them regularly until it started to break tests.

@mattrobenolt there is PR #70 with fixed tests and updated uap-core and it's waiting to be merged.

Now that the PR has been merged, what do we need to do to get a release created and pushed to pypi?

Only maintainers have rights to create a release and push it to the PyPI.
@mattrobenolt @selwin can you please do this?

Any updates making a new PyPl release? There is a key uap-core fix that my team would be interested in receiving via the update.

Thanks @mattrobenolt - I'm on the Edge engineering team (Chromium based Edge) and we're watching this update closely too as it's impacting users of our Canary, Dev and Beta channels. Would love to see this tagged and uploaded for downstream adoption. Thanks! - Jason

Just FYI for everyone waiting for pypi release: I've forked this repo a while ago and deployed to pypi: https://pypi.org/project/ua-parser-next/. It contains the most recent changes from uap-core, passes all tests and allows to pass custom device parses in case if uap-core is not currently supporting them (I needed to parse a new samsung device). The package was renamed to ua_parser_next in order not to conflict with base ua_parser package, all other functions are the same. I'm currently using it in several projects, so if you need the most recent features from uap-core you can try ua-parser-next

@soon I would be happy to make you a maintainer/dev on this repo and then you could update from here? I'm a maintainer but don't depend on or use this repo so..

Also since I merged #79 I think this particular issue is now moot (but not the overall/future issues)

@elsigh Thank you, will be happy to help

@soon sorry to bother you, but do you know when you'll be able to release the new version?
If you don't have the resources in the next couple of weeks, I'd be happy to help out as well.

@einhorntee I don't have access to this repo and I'm unable to release it. But I just checked, my fork (https://github.com/soon/uap-python-next) points to the latest commit in master in uap-core. So if switching to fork is an option you can try it

I have pushed 0.9.0.

https://pypi.org/project/ua-parser/0.9.0/