Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2000-May/003984.html below:

[Python-Dev] issues with int/long on 64bit platforms

• Previous message: [Python-Dev] issues with int/long on 64bit platforms - eg stringobject (PR#306)
• Next message: [Python-Dev] At the interactive port
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I posted a couple of patches a couple of days ago to correct the string
methods implementing slice-like optional parameters (count, find, index,
rfind, rindex) to properly clamp slice index values to the proper range (any
PyInt or PyLong value is acceptible now). In fact the slice_index() function
that was being used in ceval.c was reused (renamed to _PyEval_SliceIndex).

As well, the other patch changes PyArg_ParseTuple's 'b', 'h', and 'i'
formatters to raise an OverflowError if they overflow.

Trent

p.s. I thought I would whine here for some more attention. Who needs that
Unicode stuff anyway. ;-)

• Previous message: [Python-Dev] issues with int/long on 64bit platforms - eg stringobject (PR#306)
• Next message: [Python-Dev] At the interactive port
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4