Baptiste Carvello added the comment:
Hi all, here is a relevant user story. I'm afraid it won't help you much, but
it highlights the importance of consistent conventions in doc.
My girlfriend is learning Python with no prior programing experience. She quite
naturally got used to ca
Baptiste Carvello added the comment:
Le 14/11/2011 13:40, Ezio Melotti a écrit :
>> 1) she naturally understood the meaning of the [opt] notation
>
> I guess this depends on her background, I've seen people trying to use [] in
> function calls because they saw them in
Baptiste Carvello added the comment:
Le 14/11/2011 20:51, Eric Snow a écrit :
>
> So would it be worth the effort to identify each such place in the
> built-ins/stdlib and eventually change them all? I've seen support for doing
> so in other tracker issues and think
Baptiste Carvello added the comment:
Le 18/11/2011 05:29, Terry J. Reedy a écrit :
>
> In the following, I give objections to this PO (position only) rule and
> suggest an alternative ND (no default) rule: use 'name=default' when there is
> a default and '[name]&#x
Baptiste Carvello added the comment:
Hello,
the attached patch adds the requested feature to 3.2 (the patch is based on
6d67931c63f9), with appropriate doc changes and tests for the new behaviour.
It does not apply to 2.7, so I'll send another patch for that soon.
--
key
Baptiste Carvello added the comment:
here is the patch for 2.7.
Dave: I don't know if or when the patch will be accepted, as this is a new
feature. In the meantime, you can easily patch your system. As the code changes
are all in Python, you don't need to recompile. Going to you
Baptiste Carvello added the comment:
Eric: my bad, I guess I was living in the past, before 3.2 was released :-)
Anyway, my 3.2 patch applies to default (6354b4ceba1d), with just a one-line
offset for test_doctest.py. All tests pass.
By the way, my 2.7 patch was based on 76e5fe8e21fd
Baptiste Carvello added the comment:
Hello,
I just tried your patch on latest svn (r84707), but I found out that the
problem I reported can no more be reproduced. First, '_locale' seems now to be
built earlier. Also, a fallback has been introduced in
'locale.getpreferred
Baptiste Carvello added the comment:
Eric: the bug does not exist with 2.7, as the Makefile is read as bytes.
It exists with 3.1.2.
By the way, when I say the bug is solved on 3.2, I only mean the narrow
problem of using a
non-ascii prefix that *is* decodable with the current locale. I do
Baptiste Carvello added the comment:
Hello,
I can reproduce the exact same error as Éric. The end of the output is a
little bit more informative here:
Could not find platform dependent libraries
Consider setting $PYTHONHOME to [:]
Fatal Python error: Py_Initialize: Unable to get the locale
Baptiste Carvello added the comment:
A little bit more information:
the error message comes from Python/pythonrun.c, line 736, in function
initfsencoding.
This part of the code is protected with a preprocessor #if:
#if defined(HAVE_LANGINFO_H) && defined(CODESET)
so I tried replac
Baptiste Carvello added the comment:
Indeed, I retried with 534a9e274d88 (that was the tip of 3.2 sometime
yesterday) and my original problem is solved. Thank you.
While I was at it, I ran "make test", and got 3 unusual skips and 1
failure.
The skips are test_sax, test_xml
Baptiste Carvello added the comment:
Hello,
the patch solves the bug for me as well (using locale "C", the
filesystem encoding is utf-8). However, I do not understand why the
patch checks that the shebang line decodes with both utf-8 and the
file's encoding. The shebang line
Baptiste Carvello <[EMAIL PROTECTED]> added the comment:
If, as I understand, it is the application's job to call listdir with
bytes or unicode depending on the platform, it might be useful to have a
function in the os module telling whether the filesystem is bytes of
unicode-native.
New submission from Baptiste Carvello :
I have tried to build python (version 3.1 beta 1) on linux and install
it to a non-standard prefix which contains non-ascii utf-8 characters
(my locale being utf-8). The build directory's path is ascii-only. The
exact configure line is given i
Baptiste Carvello added the comment:
And here comes the patch
--
keywords: +patch
Added file: http://bugs.python.org/file13975/text_file.diff
___
Python tracker
<http://bugs.python.org/issue6
Baptiste Carvello added the comment:
OK, here is also the patch to 'Modules/_io/textio.c', as it is in fact
quite trivial. Choose which one you prefer :-)
Baptiste
--
Added file: http://bugs.python.org/file13984/textio.diff
___
Pyth
17 matches
Mail list logo
