Message 123388 - Python tracker

➜

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.

Author	belopolsky
Recipients	belopolsky, eric.smith, ezio.melotti, lemburg, mark.dickinson, skrah
Date	2010年12月04日.19:31:46
SpamBayes Score	5.2038795e-05
Marked as misclassified	No
Message-id	<AANLkTikJA1uxZTvKHJnRGjwYFq90tdfrkSV6GXpNswVE@mail.gmail.com>
In-reply-to	<1291460599.21.0.736219181329.issue10557@psf.upfronthosting.co.za>

Content
On Sat, Dec 4, 2010 at 6:03 AM, Mark Dickinson <report@bugs.python.org> wrote: .. > I don't much like the extra boilerplate that's introduced (and repeated) > in longobject.c, floatobject.c and complexobject.c, though. > Yes, that's exactly what I meant when I called that code "repetitious." Maybe we can tighten this up during the beta period. What do you think about adding number parsers that operate directly on Py_UNICODE* strings?

Content

On Sat, Dec 4, 2010 at 6:03 AM, Mark Dickinson <report@bugs.python.org> wrote:
..
> I don't much like the extra boilerplate that's introduced (and repeated)
> in longobject.c, floatobject.c and complexobject.c, though.
>
Yes, that's exactly what I meant when I called that code
"repetitious." Maybe we can tighten this up during the beta period.
What do you think about adding number parsers that operate directly on
Py_UNICODE* strings?

History
Date	User	Action	Args
2010年12月04日 19:31:48	belopolsky	set	recipients: + belopolsky, lemburg, mark.dickinson, eric.smith, ezio.melotti, skrah
2010年12月04日 19:31:47	belopolsky	link	issue10557 messages
2010年12月04日 19:31:47	belopolsky	create

homepage