Fix col_offset attribute for nodes involving with on PyPy

[DanielNoord]

Steps

• For new features or bug fixes, add a ChangeLog entry describing what your PR does.
• Write a good description on what the PR does.

Description

For some reason these are incorrect on PyPy...

Type of Changes

	Type
✓	🐛 Bug fix

Related Issue

[coveralls]

Pull Request Test Coverage Report for Build 2208563637

• 6 of 9 (66.67%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.02%) to 91.473%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
astroid/rebuilder.py	6	9	66.67%

Totals
Change from base Build 2207055108:	-0.02%
Covered Lines:	9097
Relevant Lines:	9945

---

💛 - Coveralls

[DanielNoord]

@Pierre-Sassoulas What do we think of postponing running PyPy 3.8 on pylint CI until after 2.14?

There seems to be an issue with PyPy 3.6 and I don't really want to spend another couple of hours investigating it since we drop support in a couple of weeks.

I'd propose:

1. Release pylint 2.14
2. Drop support for 3.6 in astroid
3. Release astroid 2.x with this fix in it.
4. Merge Run PyPy 3.8 and 3.9 in CI pylint#6406

[Pierre-Sassoulas]

Yes, let's drop python 3.6 first !

[cdce8p]

@DanielNoord I just pushed some small changes which did fix PyPy on Python 3.6. I believe the issue was with function decorators and resulting different lineno. Turns out though, we can just reuse position.col_offset for that.

[DanielNoord]

@DanielNoord I just pushed some small changes which did fix PyPy on Python 3.6. I believe the issue was with function decorators and resulting different lineno. Turns out though, we can just reuse position.col_offset for that.

Thanks for taking the time to investigate this a little further. I gave up once I saw it was 3.6, but this is indeed quite easy and elegant.

[cdce8p]

Tests are fixed now, guess we don't need to wait before merging this one. Will leave the decision up to you @DanielNoord.