Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate typing and mypyc #110

Open
masklinn opened this issue Apr 30, 2022 · 0 comments
Open

Investigate typing and mypyc #110

masklinn opened this issue Apr 30, 2022 · 0 comments

Comments

@masklinn
Copy link
Contributor

Glyph makes a case for using mypyc in order to build binary wheels / accelerators (?) https://glyph.twistedmatrix.com/2022/04/you-should-compile-your-python-and-heres-why.html

Might be interesting to take a look at it, probably related to or after #93 as a replacement or improved API would be more likely to help with the typing necessary.

However:

  • at the end of the day ua-parser is probably mostly dependent on regex performances (TODO: test), which mypyc likely can't do anything about
  • glyph had to update their bench program to a "low level / optimised implementation" (in Python) to get sensible benefits, ua-parser is all about strings
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant