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 | serhiy.storchaka |
|---|---|
| Recipients | belopolsky, serhiy.storchaka |
| Date | 2017年01月04日.20:24:47 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1698135.JeCfcheUoZ@raxxla> |
| In-reply-to | <1483559394.32.0.335371111214.issue29159@psf.upfronthosting.co.za> |
| Content | |
|---|---|
Indeed, there is behavior change. It is easy to revert the old behavior. But was the old behavior designed? It looks as a side effect of the implementation. What is a reason of making an array an integer type? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017年01月04日 20:24:47 | serhiy.storchaka | set | recipients: + serhiy.storchaka, belopolsky |
| 2017年01月04日 20:24:47 | serhiy.storchaka | link | issue29159 messages |
| 2017年01月04日 20:24:47 | serhiy.storchaka | create | |