• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

wemake-services / wemake-python-styleguide / 2223 / 2
100%
master: 100%

Build:
DEFAULT BRANCH: master
Ran 07 Nov 2019 11:44AM UTC
Files 104
Run time 7s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

07 Nov 2019 10:48AM UTC coverage: 100.0%. Remained the same
2223.2

push

travis-ci

sobolevn
revert: Annotations semantic checks

Why? Because it is too complex and bring a very little value.

Let me explain. Annotations can be used in multiple ways:

1. As Python structures: `List[int]`
2. As strings: `'SelfType[T]'`
3. As a mix of these two: `List['SelfType[T]']`

It is also really hard to tell that annotations are really the same.
Because, here's how one can write `Literal` (as an example):

1. `Literal[1]`
2. `typing.Literal[1]`
3. `t.Literal[1]`
4. `te.Literal[1]`
5. `typing_extensions.Literal[1]`
6. `'Literal[1]'`
7. ...

It would be the same annotation in all these cases. But different `ast` nodes.
Comparing them is hard. And error-prone.

We also break one very important princible of our project: we assume types.
That's why it is reverted.

2231 of 2231 branches covered (100.0%)

Branch coverage included in aggregate %.

4765 of 4765 relevant lines covered (100.0%)

1.0 hits per line

Source Files on job 2223.2
  • Tree
  • List 0
  • Changed 2
  • Source Changed 2
  • Coverage Changed 2
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Build 1574
  • Travis Job 2223.2
  • 02a934cb on github
  • Prev Job for on master (#2217.2)
  • Next Job for on master (#2224.2)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc