This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | methane |
|---|---|
| Recipients | christian.heimes, methane, xtreak |
| Date | 2020年07月03日.03:14:45 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1593746085.12.0.193252032435.issue41165@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
Hmm. You are right. The warnings are shown by default. On the other hand, some project uses custom `setup.py test` command. It hides the DeprecationWarning. https://github.com/warner/python-ed25519/blob/master/setup.py https://github.com/warner/python-ed25519/blob/master/src/ed25519/test_ed25519.py#L42 How about emitting FutureWarning instead of DeprecationWarning? DeprecationWarning is hidden to avoid end users see noisy warnings. But test is for developers, not end users. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2020年07月03日 03:14:45 | methane | set | recipients: + methane, christian.heimes, xtreak |
| 2020年07月03日 03:14:45 | methane | set | messageid: <1593746085.12.0.193252032435.issue41165@roundup.psfhosted.org> |
| 2020年07月03日 03:14:45 | methane | link | issue41165 messages |
| 2020年07月03日 03:14:45 | methane | create | |