Stephen J. Turnbull wrote:
> I just (over?)reacted to
> the suggestion that *if* people do have trouble, telling them to
> change expectations will have a useful effect.
I wasn't really suggesting that they change their expectations,
only that we shouldn't use such expectations as a basis for
deci
Stephen J. Turnbull wrote:
> Greg Ewing writes:
>
> "Decimal"
> > means "base 10". On its own it doesn't imply anything
> > about fractions.
>
> "Decimal point" notwithstanding, I guess.
That's not "decimal" on its own -- it includes the
word "point", which is what tells you that you're
(pote
Guido van Rossum writes:
> I can't recall ever hearing about Python and programming newbies
> who had trouble with %d.
OK. I think Greg's basic point is correct, I just (over?)reacted to
the suggestion that *if* people do have trouble, telling them to
change expectations will have a useful eff
> All of the modules in plat-mac are full of this kind of stuff.
> Someone needs to run 2to3 over them, I think.
Actually, after looking at the code a bit more, I think 1to3 would be
more appropriate. :-)
Bill
___
Python-3000 mailing list
Python-3000@py
I found that an SSL test was failing on 3K because of the following:
Traceback (most recent call last):
File "/local/python/3k/src/Lib/test/test_ssl.py", line 818, in testAsyncore
f = urllib.urlopen(url)
File "/local/python/3k/src/Lib/urllib.py", line 75, in urlopen
opener = FancyURLop
2007/10/26, Stephen J. Turnbull <[EMAIL PROTECTED]>:
> Greg Ewing writes:
>
> > > most people expect decimals to have fractional parts).
> >
> > Then their expectations require adjustment. "Decimal"
> > means "base 10". On its own it doesn't imply anything
> > about fractions.
>
> "Decimal po
> I'm not sure what to use in PyArg_ParseTuple in 3K. I'm passing in
> bytes which may contain NUL characters. Using 's#' doesn't really
> work, because it erroneously accepts Unicode strings.
Ah, sorry, found it. "y#".
Bill
___
Python-3000 mailing l
2007/10/26, Bill Janssen <[EMAIL PROTECTED]>:
> I'm not sure what to use in PyArg_ParseTuple in 3K. I'm passing in
> bytes which may contain NUL characters. Using 's#' doesn't really
> work, because it erroneously accepts Unicode strings.
Use y# I think.
--
--Guido van Rossum (home page: http:
I'm not sure what to use in PyArg_ParseTuple in 3K. I'm passing in
bytes which may contain NUL characters. Using 's#' doesn't really
work, because it erroneously accepts Unicode strings.
Bill
___
Python-3000 mailing list
Python-3000@python.org
http://m
Greg Ewing writes:
> > most people expect decimals to have fractional parts).
>
> Then their expectations require adjustment. "Decimal"
> means "base 10". On its own it doesn't imply anything
> about fractions.
"Decimal point" notwithstanding, I guess.
Getting "them" to change their expec
> 2007/10/26, Bill Janssen <[EMAIL PROTECTED]>:
> > I think encodestring() should return a string, not bytes, and
> > decodestring() should take either a string, or bytes containing an
> > ASCII-encoded string. Otherwise, every place they'll ever be
> > used has to wrap an additional unicode/encod
2007/10/26, Bill Janssen <[EMAIL PROTECTED]>:
> I think encodestring() should return a string, not bytes, and
> decodestring() should take either a string, or bytes containing an
> ASCII-encoded string. Otherwise, every place they'll ever be
> used has to wrap an additional unicode/encode step aro
I think encodestring() should return a string, not bytes, and
decodestring() should take either a string, or bytes containing an
ASCII-encoded string. Otherwise, every place they'll ever be
used has to wrap an additional unicode/encode step around their
use.
Bill
_
Jim Jewett wrote:
> If it weren't for backwards compatibility, 'i' would be a much better
> option,
No, it wouldn't, because 'integer' is a data type, not
a display format. The Python format codes specify display
formats, not data types.
--
Greg
___
Pyt
Chris Monson wrote:
> 'd' - Decimal Integer. Outputs the number in base 10.
>
> Modern C now has
> 'i' as an alternative to 'd'
Considering that in printf formats the alternatives to
'd' or 'i' are 'x' for hexadecimal and 'o' for octal,
then 'd' for decimal makes a lot more sense to me th
2007/10/26, Christian Heimes <[EMAIL PROTECTED]>:
> I suggest that you create a branch for the transition period. It will
> take at least several days to kick and drag everything in place. We can
> work on the transition while the rest can play with a working py3k branch.
Thanks for the suggestion
Guido van Rossum wrote:
> Mid November sounds more like it.
>
> Below is a full updated status update; here's a short list of the
> tasks that remain to be done:
>
> - remove compatibility with PyString from PyUnicode
> - change lots of places (e.g. encoders) to return PyString instead of PyBytes
2007/10/26, Bill Janssen <[EMAIL PROTECTED]>:
> I'm looking at the Py3K SSL code, and have a question:
>
> What's the upshot of the bytes/string decisions in the C world? Is
> PyString_* now all about immutable bytes, and PyUnicode_* about
> strings? There still seem to be a lot of encode/decode
I'm looking at the Py3K SSL code, and have a question:
What's the upshot of the bytes/string decisions in the C world? Is
PyString_* now all about immutable bytes, and PyUnicode_* about
strings? There still seem to be a lot of encode/decode methods in
stringobject.h, operations which I'd expect
2007/10/19, Guido van Rossum <[EMAIL PROTECTED]>:
> On 10/7/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > I'd like to make complete implementation of PEP 3137 the goal for the
> > 3.0a2 release. It should be doable to do this release by the end of
> > October. I don't think anything else *nee
On 10/26/07, Larry Hastings <[EMAIL PROTECTED]> wrote:
> His point is that Python has a fixed-point number type called "Decimal",
> and that this will lead to confusion. I can see his point, but we all know
> from years of C programming that "%d" takes an int and formats it in base
> 10--there is
Oleg Broytmann wrote:
The article says "decimal" is a synonym. What is the point to use an
unknown synonym instead of a well-known word?
His point is that Python has a fixed-point number type called "Decimal",
and that this will lead to confusion. I can see his point, but we all
know from ye
On Fri, Oct 26, 2007 at 03:40:55PM +0100, Mark Summerfield wrote:
> http://www.thefreedictionary.com/denary
No need to use a word I have to lookup in a dictionary when "decimal" is
so widely used.
The article says "decimal" is a synonym. What is the point to use an
unknown synonym instead of
On 2007-10-26, Guido van Rossum wrote:
> 2007/10/26, Oleg Broytmann <[EMAIL PROTECTED]>:
> > On Fri, Oct 26, 2007 at 09:48:28AM -0400, Chris Monson wrote:
>
> [quoting Mark Summerfield]
>
> > > 'd' - Decimal Integer. Outputs the number in base 10.
> >
> > [skip]
> >
> > > 'd' - Dena
2007/10/26, Oleg Broytmann <[EMAIL PROTECTED]>:
> On Fri, Oct 26, 2007 at 09:48:28AM -0400, Chris Monson wrote:
[quoting Mark Summerfield]
> > 'd' - Decimal Integer. Outputs the number in base 10.
> [skip]
> > 'd' - Denary Integer. Outputs the number in base 10.
>
>-1. I know wh
On Fri, Oct 26, 2007 at 09:48:28AM -0400, Chris Monson wrote:
> 'd' - Decimal Integer. Outputs the number in base 10.
[skip]
> 'd' - Denary Integer. Outputs the number in base 10.
-1. I know what "decimal integers" are, but never heard about "denary"
(my spellchecker complains,
Forwarding to the group for discussion.
On 10/26/07, Mark Summerfield wrote:
There is one thing about this PEP I don't like:
The available integer presentation types are:
'd' - Decimal Integer. Outputs the number in base 10.
I think this is confusing (since this will not print a de
27 matches
Mail list logo
