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 | Tim.Graham |
|---|---|
| Recipients | SilentGhost, Tim.Graham, eric.snow, larry, ncoghlan, ned.deily, python-dev, r.david.murray, ryan.petrello, serhiy.storchaka, yselivanov |
| Date | 2017年04月27日.01:30:20 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1493256620.88.0.664408816802.issue27172@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Does it seems likely that getfullargspec() will be deprecated after Python 2 is EOL? Django is currently reimplementing getargspec(): https://github.com/django/django/blob/8ab7ce8558792f41637d6f87f2a8a117e169dd18/django/utils/inspect.py#L4-L24 A pull request proposes to modify that implementation to behave as getfullargspec(): https://github.com/django/django/pull/8410 Django master now supports Python 3.4+, so I guess we would rather use getfullargspec() if it's not going to be deprecated in the future. The only downside is that it would introduce deprecation warnings for Python 3.5 users since those warnings haven't been removed yet. I guess Django could silence them. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017年04月27日 01:30:21 | Tim.Graham | set | recipients: + Tim.Graham, ncoghlan, larry, ned.deily, r.david.murray, SilentGhost, python-dev, eric.snow, serhiy.storchaka, yselivanov, ryan.petrello |
| 2017年04月27日 01:30:20 | Tim.Graham | set | messageid: <1493256620.88.0.664408816802.issue27172@psf.upfronthosting.co.za> |
| 2017年04月27日 01:30:20 | Tim.Graham | link | issue27172 messages |
| 2017年04月27日 01:30:20 | Tim.Graham | create | |