-
Notifications
You must be signed in to change notification settings - Fork 154
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
update uap-core submodule #70
update uap-core submodule #70
Conversation
@admitad-github could you please look at the failing tests? |
Yes, will look at it today |
@selwin ok, looks like all tests are passing now. Also, we added build matrix for Travis CI, so tests run in parallel now. |
Would be great to get this one through, really usefull @admitad-github |
I could definitely use this update. Thank you @admitad-github Thank you in advance @selwin |
awesome, can't wait for it to be merged |
@mattrobenolt any chance we can get this PR merged? Would be super helpful! |
Also would like to see this ship, but I think I need uap-core 0.6.8 (as I want to see support for parsing the new Edge Chromium user agent). It looks like uap-core@0.6.8 is not included in the latest version of this PR? |
@elsigh mind merging this one too? I'll send a PR to update to uap-core 0.6.9 after this is merged; figuring it doesn't make sense for me to redo this work. |
@@ -61,15 +61,15 @@ def Parse(self, user_agent_string): | |||
if self.v1_replacement: | |||
v1 = self.v1_replacement | |||
elif match.lastindex and match.lastindex >= 2: | |||
v1 = match.group(2) | |||
v1 = match.group(2) or None |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am curious, is there any impact of this or None? seems like it would just cause v1 = None
instead of v1 = ''
- is that the intent?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it was intended to match with the tests in uap-core, e.g. uap-core/tests/test_os.yaml, where some fields have None
instead of empty string.
or perhaps I could interest @tobie in merging this? |
I'm rolling with checks passing = ok |
awesome! |
pyyaml hasn't been a required dependency for a very long time, it's really not clear why ua-parser#70 reintroduced a requirements.txt for it, unless there were points at which `install_requires` was not resolved as a *dependency*, so pyyaml had to be separately installed for `develop` to work?
pyyaml hasn't been a required dependency for a very long time, it's really not clear why ua-parser#70 reintroduced a requirements.txt for it, unless there were points at which `install_requires` was not resolved as a *dependency*, so pyyaml had to be separately installed for `develop` to work? See also: ua-parser#103
pyyaml hasn't been a required dependency for a very long time, it's really not clear why ua-parser#70 reintroduced a requirements.txt for it, unless there were points at which `install_requires` was not resolved as a *dependency*, so pyyaml had to be separately installed for `develop` to work? See also: ua-parser#103
pyyaml hasn't been a required dependency for a very long time, it's really not clear why ua-parser#70 reintroduced a requirements.txt for it, unless there were points at which `install_requires` was not resolved as a *dependency*, so pyyaml had to be separately installed for `develop` to work? See also: ua-parser#103
pyyaml hasn't been a required dependency for a very long time, it's really not clear why ua-parser#70 reintroduced a requirements.txt for it, unless there were points at which `install_requires` was not resolved as a *dependency*, so pyyaml had to be separately installed for `develop` to work? See also: ua-parser#103
pyyaml hasn't been a required dependency for a very long time, it's really not clear why ua-parser#70 reintroduced a requirements.txt for it, unless there were points at which `install_requires` was not resolved as a *dependency*, so pyyaml had to be separately installed for `develop` to work? See also: ua-parser#103
Also update internal version thingie to match. And remove 2.6 from the classifier tags, as it was dropped way back in 2019 (ua-parser#70, a9665f7)
pyyaml hasn't been a required dependency for a very long time, it's really not clear why ua-parser#70 reintroduced a requirements.txt for it, unless there were points at which `install_requires` was not resolved as a *dependency*, so pyyaml had to be separately installed for `develop` to work? See also: ua-parser#103
Also update internal version thingie to match. And remove 2.6 from the classifier tags, as it was dropped way back in 2019 (ua-parser#70, a9665f7)
pyyaml hasn't been a required dependency for a very long time, it's really not clear why #70 reintroduced a requirements.txt for it, unless there were points at which `install_requires` was not resolved as a *dependency*, so pyyaml had to be separately installed for `develop` to work? See also: #103 Closes #106
Also update internal version thingie to match. And remove 2.6 from the classifier tags, as it was dropped way back in 2019 (ua-parser#70, a9665f7)
Updated uap-core submodule have support for many new browsers.
Related issues #66, #68.