[issue4799] handling inf/nan in '%f'

2009-04-12 Thread Eric Smith
Eric Smith added the comment: I believe this is a duplicate of issue 4482. I'm closing this and will add everyone who is nosy on this to be nosy on 4482. -- resolution: -> duplicate status: open -> closed ___ Python tracker

[issue4799] handling inf/nan in '%f'

2009-04-09 Thread Christoph Zwerschke
Christoph Zwerschke added the comment: This is a related problem on Windows: '%g' % 1e400 -> '1.#INF' '%.f' % 1e400 --> '1' -- nosy: +cito ___ Python tracker ___ __

[issue4799] handling inf/nan in '%f'

2009-03-30 Thread Mark Dickinson
Mark Dickinson added the comment: Assigning to Eric, at his request. -- assignee: marketdickinson -> eric.smith nosy: +eric.smith ___ Python tracker ___ _

[issue4799] handling inf/nan in '%f'

2009-02-11 Thread Mark Dickinson
Changes by Mark Dickinson : -- assignee: -> marketdickinson nosy: +marketdickinson ___ Python tracker ___ ___ Python-bugs-list mailing

[issue4799] handling inf/nan in '%f'

2008-12-31 Thread Cournapeau David
New submission from Cournapeau David : On windows, with python 2.6, s = '%s' % float('inf') is 'inf', but s = '%f' % float('inf') is equal to '1.#INF'. This patch fixes the inconsistency, by using the code from floatobject.f format_float into stringobject.c formatfloat. I think it would be bett