The underlying problem is that we started to infer a confusing union type
of __init__.py modules found both in site-packages and python_stubs
for such imported packages, but I want it to be addressed separately in PY-39911.
GitOrigin-RevId: 053a4a092ce7fcc71d192dbaa6b1623b82472a17
The correct way to use parameters is to add them to the test name.
"-k" is also works in some cases, but it is not official nor stable.
* pytest runner reports "testname[param]" as metainfo
* we fetch param
* add "parameters" field to the pytest
* glue it with test name
GitOrigin-RevId: 56c5d93fd93a12ba5742b21af51ea04823a9d8f7
replace `public static final String X = *Bundle.message(...)` with
```public static String getX() {
return *Bundle.message(...)
}
```
Also, let's mark fields that are used in third party plugins as `@deprecated`
GitOrigin-RevId: b9d42527ed14126b84dca91b837064c306c03177
* For cases when a TypedDict was defined in a separate file
* Fix race when typing near inherited TypedDict's field
GitOrigin-RevId: e19792592c744e9c5a7a7c00af847296efb11d0c
When test runner returns code > 0 (because of test failure), our runner must do the same.
See issue description for the reason
GitOrigin-RevId: 231c9ab337e80f70872bf6e6f61a397599f18e26
The previous version of the procedure could miss breakpoints when extra `EXTENDED_ARG` instructions are added before the injected code. This happened because in some corner cases after updating the opcodes to lines mapping an `EXTENDED_ARG` instruction could land as the last instruction in a line, and the instruction which argument it extends - on another. This lead to the situation when it was impossible to detect that we have hit the next line. These changes also add the ability to trace opcodes when the `PYDEVD_TRACE_OPCODES` environment variable is set to `True` (available only for Cython) to ease the debugging of such cases in the future.
(cherry picked from commit 77399d3b7b2b9bc6aac1b85d59ae305500cb6ecb)
GitOrigin-RevId: 105bf9d3d2cc51a940b03b1cb11c07e97074048b
If a process was started with `-m` key (and converted to `--module` flag), this parameter will be passed to all its child processes. So we need to clear this flag in SetupHolder before patching arguments
GitOrigin-RevId: 00ae0b23fc6107bee75272a03a5bd15ca474fbc7
Unresolved reference need to be error highlighted because
module is something certain and unresolved import is error in most cases.
GitOrigin-RevId: b91e54e695b908db193a35378e663288dae90059
rather delegating to the spell checker of the injected language.
Otherwise, we either just report typos twice (PY-36912) or, worse, report
numerous false positives since we try to apply tokenization rules for Python
to a different language as we notoriously have been doing all this time for
injected regular expressions.
Implementations of spell checkers for other languages such as Java or
JavaScript have been using this policy for ages.
GitOrigin-RevId: d1a2a3d48b7a5efff0dbb32ec2847fba1482f3a8
Implicits are slow.
* defaultContext() now doesn't have em
* implicits are enabled explicitly (no wordplay here!) for certain user-initiated actions and findReferenceAt
* Latter is for navigating to methods/attributes of unknown types
GitOrigin-RevId: 62df6707507584576ea4c193ccf6e7f0c128c5be
- move PyResolveTest to common tests
- support common test fixture for both platform and analysis tool
GitOrigin-RevId: dafe7a942b1c9d4d927dc5e2f412a0941e0b0dd1
