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/2002-November/030574.html below:

[Python-Dev] int/long FutureWarning

[Python-Dev] int/long FutureWarning [Python-Dev] int/long FutureWarningMartin v. Löwis martin@v.loewis.de
Fri, 29 Nov 2002 17:19:00 +0100
> I grabbed it from the old discussion, so there's a good chance MAL
came
> up with it at that time. But Guido mumbled somthing about "k1"=="B"
and
> "k2"=="H" and that being overkill, and then the discussion stopped.
> Hence my  question: is k1/k2/k4/k8 what it's going to be?

+1. I personally don't care about the duplication, since I expect that
both the implementation and the documentation can be quite compact and
treat all sizes uniformly, so having one format more or less doesn't
matter.

Regards,
Martin




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