Message316910
| Author | ssbarnea |
|---|---|
| Recipients | barry, jwilk, serhiy.storchaka, ssbarnea |
| Date | 2018-05-17.11:22:57 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1526556178.06.0.682650639539.issue31973@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I agree that this deprecation approach is not very helpful because it does not indicate a recommended way to fix. Yep, we all know that we will be forced to rename these parameters/variables everywhere and likely break few APIs due to it. I am curious if there is any emerging pattern for new naming as I find really annoying if every python project using these keywords would endup picking different alternatives for their rename. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-05-17 11:22:58 | ssbarnea | set | recipients: + ssbarnea, barry, jwilk, serhiy.storchaka |
| 2018-05-17 11:22:58 | ssbarnea | set | messageid: <1526556178.06.0.682650639539.issue31973@psf.upfronthosting.co.za> |
| 2018-05-17 11:22:57 | ssbarnea | link | issue31973 messages |
| 2018-05-17 11:22:57 | ssbarnea | create | |