On 5/27/06, Just van Rossum <[EMAIL PROTECTED]> wrote:
> Oleg Broytmann wrote:
>
> > On Sat, May 27, 2006 at 03:15:32PM +0200, tomer filiba wrote:
> > > which makes it impossible to diffrenciate between
> > > >>>y[1, 2]
> > > (1, 2)
> > >
> > > and
> > > >>>y[(1, 2)]
> > > (1, 2)
> >
> >Tuples
Please be specific. Which places are affected? This shouldn't be
answered generically but on a case-by-case basis.
--Guido
On 5/27/06, Collin Winter <[EMAIL PROTECTED]> wrote:
> On 5/21/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > Since **kwds is already a dict (i.e. a mutable container) a
Guido van Rossum wrote:
> I have to ignore this topic. It's too big and contentious to get easy
> agreement. (The one thing I *don't* want is move the entire stdlib
> hierarchy under 'py' or something like that.) Eric Raymond once made
> detailed proposal, you can probably still find it somewhere.
[Adding the py3k list; please remove python-dev in followups.]
On 5/29/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> I thought Py3k will have a single integer type whose representation
> varies depending on the value being represented.
That's one proposal. Another is to have an abstract 'int
Guido van Rossum wrote:
>> struct PyInt{
>> struct PyObject ob;
>> Py_ssize_t value_or_size;
>> char is_long;
>> digit ob_digit[1];
>> };
>>
>
> Nice. I guess if we store the long value in big-endian order we could
> drop is_long, since the first digit of the long would always be
> nonzero
