➜
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.
Created on 2007-07-15 11:01 by thomasglee, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| alt_neq_deprecation_2007071502.patch | thomasglee, 2007-07-15 11:01 | Initial patch | ||
| Messages (2) | |||
|---|---|---|---|
| msg52878 - (view) | Author: Tom Lee (thomasglee) | Date: 2007-07-15 11:01 | |
Generates a DeprecationWarning for the use of <>. Is it a hack to do this within Parser/tokenizer.c? Can't see any other immediate way to do it without generating an alternate token code for <> vs. !=: tom@localhost:~/src/python-trunk$ ./python -3 warning: callable() not supported in 3.x warning: callable() not supported in 3.x warning: callable() not supported in 3.x warning: callable() not supported in 3.x warning: callable() not supported in 3.x warning: callable() not supported in 3.x warning: callable() not supported in 3.x warning: callable() not supported in 3.x Python 2.6a0 (trunk:56394M, Jul 15 2007, 21:00:33) [GCC 4.1.2 (Ubuntu 4.1.2-0ubuntu4)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> 1 <> 2 sys:1: DeprecationWarning: <> not supported in 3.x True >>> 1 != 2 True >>> |
|||
| msg57778 - (view) | Author: Christian Heimes (christian.heimes) *  |
Date: 2007-11-23 09:11 | |
Applied in r59132 Thanks! |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:25 | admin | set | github: 45200 |
| 2007-11-23 09:11:05 | christian.heimes | set | status: open -> closed resolution: fixed messages: + msg57778 nosy: + christian.heimes |
| 2007-07-15 11:01:24 | thomasglee | create | |