[issue2343] Raise a Py3K warning when using a float where an int is expected

2008-04-28 Thread Brett Cannon
Brett Cannon <[EMAIL PROTECTED]> added the comment: Closing as out of date since it seems to have already been handled. -- resolution: -> out of date status: open -> closed __ Tracker <[EMAIL PROTECTED]> ___

[issue2343] Raise a Py3K warning when using a float where an int is expected

2008-03-22 Thread Brett Cannon
Changes by Brett Cannon <[EMAIL PROTECTED]>: -- assignee: -> brett.cannon __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list

[issue2343] Raise a Py3K warning when using a float where an int is expected

2008-03-22 Thread Benjamin Peterson
Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- type: -> behavior __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Uns

[issue2343] Raise a Py3K warning when using a float where an int is expected

2008-03-22 Thread Benjamin Peterson
Benjamin Peterson <[EMAIL PROTECTED]> added the comment: I think so. The warning is implemented in getargs.c, so any conversion from a float to int will result in a warning. __ Tracker <[EMAIL PROTECTED]>

[issue2343] Raise a Py3K warning when using a float where an int is expected

2008-03-22 Thread Brett Cannon
Brett Cannon <[EMAIL PROTECTED]> added the comment: Is there any other place where this might be an issue? That's the real question; are all reasonable cases covered. __ Tracker <[EMAIL PROTECTED]> __

[issue2343] Raise a Py3K warning when using a float where an int is expected

2008-03-22 Thread Benjamin Peterson
Benjamin Peterson <[EMAIL PROTECTED]> added the comment: This is already implemented: >>> [].insert(.5, 0) __main__:1: DeprecationWarning: integer argument expected, got float -- nosy: +benjamin.peterson __ Tracker <[EMAIL PROTECTED]>

[issue2343] Raise a Py3K warning when using a float where an int is expected

2008-03-17 Thread Brett Cannon
Changes by Brett Cannon <[EMAIL PROTECTED]>: -- priority: immediate -> urgent __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing lis

[issue2343] Raise a Py3K warning when using a float where an int is expected

2008-03-17 Thread Brett Cannon
New submission from Brett Cannon <[EMAIL PROTECTED]>: Using a float where an int should only be used (e.g., ``[].insert(.5, 0)``) should raise a Py3K warning. -- components: Interpreter Core keywords: 26backport messages: 63704 nosy: brett.cannon priority: immediate severity: normal stat