Uh oh!
There was an error while loading. Please reload this page.
Fix #833 - Failing test due to querystring order. - #834
Merged
Conversation
coveralls
commented
Apr 16, 2015
Changes Unknown when pulling 37f22dc on jgeewax:url-param-order into * on GoogleCloudPlatform:master*. |
dhermes
commented
Apr 16, 2015
Contributor
LGTM Thanks |
tseaver
commented
Apr 16, 2015
Contributor
Yup |
jgeewax
commented
Apr 16, 2015
ContributorAuthor
Sweet. Just saw the build pass (and I fixed this to follow the pattern you guys had using six.moves). Merging. |
jgeewax added a commit
that referenced
this pull request
Apr 16, 2015
Fix#833 - Failing test due to querystring order.
parthea pushed a commit
that referenced
this pull request
Sep 18, 2025
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
parthea pushed a commit
that referenced
this pull request
Nov 22, 2025
) Source-Link: googleapis/synthtool@d6103f4 Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-python:latest@sha256:39f0f3f2be02ef036e297e376fe3b6256775576da8a6ccb1d5eeb80f4c8bf8fb Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
parthea pushed a commit
that referenced
this pull request
Nov 24, 2025
* chore: Update CODEOWNERS updating codeowners to allow reviews from partner team * 🦉 Updates from OwlBot post-processor See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md --------- Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
parthea pushed a commit
that referenced
this pull request
Nov 24, 2025
parthea added a commit
that referenced
this pull request
Nov 24, 2025
…#834) Co-authored-by: Anthonios Partheniou <partheniou@google.com>
parthea pushed a commit
that referenced
this pull request
Nov 25, 2025
parthea pushed a commit
that referenced
this pull request
Nov 26, 2025
parthea pushed a commit
that referenced
this pull request
Mar 6, 2026
parthea pushed a commit
that referenced
this pull request
Mar 6, 2026
Source-Link: googleapis/synthtool@dede53f Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-python:latest@sha256:fac304457974bb530cc5396abd4ab25d26a469cd3bc97cbfb18c8d4324c584eb Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
parthea pushed a commit
that referenced
this pull request
Mar 9, 2026
This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [pyparsing](https://redirect.github.com/pyparsing/pyparsing) | `==3.2.5` → `==3.3.2` |  |  | --- ### Release Notes <details> <summary>pyparsing/pyparsing (pyparsing)</summary> ### [`v3.3.2`](https://redirect.github.com/pyparsing/pyparsing/blob/HEAD/CHANGES#Version-332---January-2026) [Compare Source](https://redirect.github.com/pyparsing/pyparsing/compare/3.3.1...3.3.2) - Defined pyparsing-specific warning classes so that they can be selectively enabled or disabled without affecting warnings raised by other libraries in the same Python app: - `PyparsingWarning` - base warning for all pyparsing-specific warnings (inherits from `UserWarning`) - `PyparsingDeprecationWarning` - warning for using deprecated features (inherits from `PyparsingWarning` and `DeprecationWarning`) - `PyparsingDiagnosticWarning` - warning raised when pyparsing diagnostics are enabled and a diagnostic feature is used (inherits from `PyparsingWarning`) - Added `as_datetime` parse action to `pyparsing.common` - a more generalized version of the `convert_to_datetime` parse action (supports any expression that extracts date/time fields into "year", "month", "day", etc. results names), and validates that the parsed fields represent a valid date and time. - Added `iso8601_date_validated` and `iso8601_datetime_validated` expressions to `pyparsing.common`, which return a Python `datetime.datetime` - Various performance improvements in `ParseResults` class and core functions, with 10-20% performance overall. - Added `regex_inverter` web page (using PyScript) to demonstrate using the `inv_regex.py` example. - Expanded regex forms handled by the `examples/inv_regex.py` example: - named capturing groups (`?P<name>`) - partial repetition (`{m,}` and `{,n}`) - negated character classes (`[^...]`) - Added `SPy` (Simplified Python) parser to examples. ### [`v3.3.1`](https://redirect.github.com/pyparsing/pyparsing/blob/HEAD/CHANGES#Version-331---December-2025) [Compare Source](https://redirect.github.com/pyparsing/pyparsing/compare/3.3.0...3.3.1) - Added license info to metadata, following PEP-639. Thanks to Gedalia Pasternak and Marc Mueller for submitted issue and PR. Fixes [#​626](https://redirect.github.com/pyparsing/pyparsing/issues/626). ### [`v3.3.0`](https://redirect.github.com/pyparsing/pyparsing/blob/HEAD/CHANGES#Version-330---December-2025) [Compare Source](https://redirect.github.com/pyparsing/pyparsing/compare/3.2.5...3.3.0) \=========================================================================================== The version 3.3.0 release will begin emitting `DeprecationWarnings` for pyparsing methods that have been renamed to PEP8-compliant names (introduced in pyparsing 3.0.0, in August, 2021, with legacy names retained as aliases). In preparation, I added in pyparsing 3.2.2 a utility for finding and replacing the legacy method names with the new names. This utility is located at `pyparsing/tools/cvt_pep8_names.py`. This script will scan all Python files specified on the command line, and if the `-u` option is selected, will replace all occurrences of the old method names with the new PEP8-compliant names, updating the files in place. Here is an example that converts all the files in the pyparsing `/examples` directory: ``` python -m pyparsing.tools.cvt_pyparsing_pep8_names -u examples/*.py ``` </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/googleapis/python-spanner-sqlalchemy). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My40OC4xIiwidXBkYXRlZEluVmVyIjoiNDMuNDguMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->
parthea pushed a commit
that referenced
this pull request
Mar 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes#833