A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2004-January/041577.html below:

[Python-Dev] Pie-thon benchmark code ready

[Python-Dev] Pie-thon benchmark code ready [Python-Dev] Pie-thon benchmark code readySamuele Pedroni pedronis at bluewin.ch
Fri Jan 2 07:45:53 EST 2004
>So I'd be happy if we could standardize on 'at 0x...' at least for all
>objects where CPython currently uses that, letting implementations
>choose what to put after the 0x, as long as it's hex digits.

my proposal is that both the following forms should be acceptable:

1. <... at 0x<hex>>
2. <... id# <decimal>>

and would change Jython to use the 2nd one. If we really want to just go with
what is the status quo, i.e 1. then I would revert to use identityHashCode
although it's not unique.

regards. 


More information about the Python-Dev mailing list

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