Message347387
| Author | Mark.Williams |
|---|---|
| Recipients | Mark.Williams, aldwinaldwin, miss-islington, ned.deily, nedbat, p-ganssle, pablogsal, scoder, serhiy.storchaka, tim.peters, xtreak |
| Date | 2019-07-05.21:17:13 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1562361433.5.0.23697565365.issue37500@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
As a user of Python who maintains at least one large code base, I rely on coverage to limit the damage my changes can inflict. Some of the code I maintain uses __debug__; I would not expect moving to 3.8 to be the cause of reduced line coverage in that project, and I would be baffled by the difference between a coverage report from 3.8 and < 3.8. Please don't break a package as fundamental as coverage. Can the compiler be changed to not emit bytecode under some circumstances? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-07-05 21:17:13 | Mark.Williams | set | recipients: + Mark.Williams, tim.peters, scoder, nedbat, ned.deily, serhiy.storchaka, p-ganssle, pablogsal, miss-islington, xtreak, aldwinaldwin |
| 2019-07-05 21:17:13 | Mark.Williams | set | messageid: <1562361433.5.0.23697565365.issue37500@roundup.psfhosted.org> |
| 2019-07-05 21:17:13 | Mark.Williams | link | issue37500 messages |
| 2019-07-05 21:17:13 | Mark.Williams | create | |