On 23/09/2014 23:52, Mark Lawrence wrote:
On 23/09/2014 22:48, blindanagram wrote:
On 23/09/2014 20:30, Mark Lawrence wrote:
On 23/09/2014 18:43, blindanagram wrote:
All you need do is raise an issue on the bug tracker, provide a patch to
code, test and docs and the job is done.
Thank you for your helpful comment. I will happily do this if after
discussion here there is a reasonable level of support and encouragement
for such an action.
However, there is at least one person here who takes the view that
backward compatibility outranks mathematical correctness and I don't
want to find that 'I am banging my head against a brick wall' if this is
likely to be the stance that Python developers take.
From https://docs.python.org/devguide/experts.html Mark Dickinson and
Raymond Hettinger are listed as the maintainers of the fractions module.
If they're not lurking here I'd guess the simplest way to contact them
is via the bug tracker. That also gives the official mechanism as to
whether or not an enhancement request such as this is accepted or
rejected and the rationale behind the decision. For example it is
feasible that the current behaviour would be deprecated in Python 3.5
and changed in 3.6 to match your needs. I don't have enough knowledge
of the maths to say one way or another, but I'm certain that others will
chip in with their comments. Best of luck anyway :)
Somebody got there first http://bugs.python.org/issue22477
--
My fellow Pythonistas, ask not what our language can do for you, ask
what you can do for our language.
Mark Lawrence
--
https://mail.python.org/mailman/listinfo/python-list
