Issue 547211: Warn for coerce in new-style classes (original) (raw)
Issue547211
➜
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.
This issue has been migrated to GitHub: https://github.com/python/cpython/issues/36485
classification
| Title: | Warn for __coerce__ in new-style classes | ||
|---|---|---|---|
| Type: | Stage: | ||
| Components: | Interpreter Core | Versions: | Python 2.3 |
process
| Status: | closed | Resolution: | later |
|---|---|---|---|
| Dependencies: | Superseder: | ||
| Assigned To: | nnorwitz | Nosy List: | gvanrossum, nnorwitz |
| Priority: | normal | Keywords: |
Created on 2002-04-22 18:51 by gvanrossum, last changed 2022-04-10 16:05 by admin. This issue is now closed.
| Messages (3) | ||
|---|---|---|
| msg10486 - (view) | Author: Guido van Rossum (gvanrossum) *  |
Date: 2002-04-22 18:51 |
| New-style classes don't support __coerce__, except that when you define it, coerce() will call it. (But it won't be called by the binary operators.) Methinks a warning should be issued when a new-style class defines __coerce__. | ||
| msg10487 - (view) | Author: Guido van Rossum (gvanrossum) * |
Date: 2002-06-03 21:04 |
| Logged In: YES user_id=6380 I think this is a PyChecker issue. Neal, can you add this to PyChecker? If you do, please close this bug report. | ||
| msg10488 - (view) | Author: Neal Norwitz (nnorwitz) * |
Date: 2002-06-04 16:20 |
| Logged In: YES user_id=33168 Added warning to pychecker. |
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-10 16:05:15 | admin | set | github: 36485 |
| 2002-04-22 18:51:12 | gvanrossum | create |