Skip to content

Make sure the line comes from the same node as the col offset.#9189

Merged
miss-islington merged 1 commit into
masterfrom
benjamin-line-n0
Sep 11, 2018
Merged

Make sure the line comes from the same node as the col offset.#9189
miss-islington merged 1 commit into
masterfrom
benjamin-line-n0

Conversation

@benjaminp

Copy link
Copy Markdown
Contributor

Followup to 90fc898.

@miss-islington

Copy link
Copy Markdown
Contributor

@benjaminp: Status check is done, and it's a success ✅ .

@miss-islington miss-islington merged commit d13e59c into master Sep 11, 2018
@miss-islington

Copy link
Copy Markdown
Contributor

Thanks @benjaminp for the PR 🌮🎉.. I'm working now to backport this PR to: 3.7.
🐍🍒⛏🤖

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Sep 11, 2018
…nGH-9189)

Followup to 90fc898.

<!--
Thanks for your contribution!
Please read this comment in its entirety. It's quite important.

GH- Pull Request title

It should be in the following format:

```
bpo-NNNN: Summary of the changes made
```

Where: bpo-NNNN refers to the issue number in the https://bugs.python.org.

Most PRs will require an issue number. Trivial changes, like fixing a typo, do not need an issue.

GH- Backport Pull Request title

If this is a backport PR (PR made against branches other than `master`),
please ensure that the PR title is in the following format:

```
[X.Y] <title from the original PR> (GH-NNNN)
```

Where: [X.Y] is the branch name, e.g. [3.6].

GH-NNNN refers to the PR number from `master`.

-->
(cherry picked from commit d13e59c)

Co-authored-by: Benjamin Peterson <benjamin@python.org>
@bedevere-bot

Copy link
Copy Markdown

GH-9194 is a backport of this pull request to the 3.7 branch.

@benjaminp benjaminp deleted the benjamin-line-n0 branch September 11, 2018 22:36
miss-islington added a commit that referenced this pull request Sep 11, 2018
Followup to 90fc898.

<!--
Thanks for your contribution!
Please read this comment in its entirety. It's quite important.

GH- Pull Request title

It should be in the following format:

```
bpo-NNNN: Summary of the changes made
```

Where: bpo-NNNN refers to the issue number in the https://bugs.python.org.

Most PRs will require an issue number. Trivial changes, like fixing a typo, do not need an issue.

GH- Backport Pull Request title

If this is a backport PR (PR made against branches other than `master`),
please ensure that the PR title is in the following format:

```
[X.Y] <title from the original PR> (GH-NNNN)
```

Where: [X.Y] is the branch name, e.g. [3.6].

GH-NNNN refers to the PR number from `master`.

-->
(cherry picked from commit d13e59c)

Co-authored-by: Benjamin Peterson <benjamin@python.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants