> > > And it introduces incompatibilities.
> >
> > What kind? I thought it would be a new format code?
>
> Two new format codes ('k' and 'K'), and changes to existing format
> codes - per your request:
>
> | How about the following counterproposal. This also changes some of the
> | other format codes to be a little more regular.
> |
> | Code C type Range check
> |
> | b unsigned char 0..UCHAR_MAX
> | B unsigned char none **
> | h unsigned short 0..USHRT_MAX
> | H unsigned short none **
> | i int INT_MIN..INT_MAX
> | I * unsigned int 0..UINT_MAX
> | l long LONG_MIN..LONG_MAX
> | k * unsigned long none
> | L long long LLONG_MIN..LLONG_MAX
> | K * unsigned long long none
> |
> | Notes:
> |
> | * New format codes.
> |
> | ** Changed from previous "range-and-a-half" to "none"; the
> | range-and-a-half checking wasn't particularly useful.
Oh of course. None to worry about IMO.
> > > BTW: Since you want to release a beta version, what's the state
> > > of the FutureWarning about hex/oct constants: will this stay the
> > > way it is?
> >
> > Probably, unless you hve a better idea. :-(
>
> I haven't used warnings very much, but is there a possibility to
> disable them per module? You get a lot of them if you 'import
> win32con' for example.
Yes, you can suppress warnings per module. Please read the docs.
--Guido van Rossum (home page: http://www.python.org/~guido/)
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