New submission from jean-michel :
Hi.
Python-3.7.1 with LibreSSL-2.8.2 and patches from
https://github.com/python/cpython/pull/8055 and
https://github.com/python/cpython/pull/8050
Compilation failed because of test_ssl failed.
A detailed list of all the patches that I use for my python
Jean-Michel added the comment:
Sorry, the description was missing.
parse.py crashes if provided with unicode data like "voilà" :
[wsgi:error] [pid 20335] [client 127.0.0.1:44658] UnicodeEncodeError: 'ascii'
codec can't encode character '\\xe0' in position
New submission from Jean-Michel :
Here is the patch, working for me in Python 3.4.2
610,611c703
< #~ value = _coerce_result(value)
< value = _coerce_result(value,encoding=encoding)
---
> value = _coerce_result(value)
--
messages: 306953
n
Jean-Michel Fauth added the comment:
2012/3/3 Terry J. Reedy
>
> Terry J. Reedy added the comment:
>
> > That would mean in Python 3, '...' works and u'...' will not work.
>
> You misunderstand the PEP: in 3.3, '...' and u'...&#x
Jean-Michel Fauth added the comment:
You do not get it or I do not explain it correctly.
I do not care if Py 3.3 accepts '...' ou u'...'. I'm only
affraid, Py 3.3 is suffering from the same non working
behaviour Python 2 is suffering. I have seen so many things...
Jean-Michel Fauth added the comment:
Sorry, I neglected the most important information.
Python 3.2 is working perfectly. It is simply impossible
to create non valid strings (type/class 'str') from a
keyboard. (non programmatically created).
Like the limited characters set I used wh
Jean-Michel Fauth added the comment:
I deliberately hid the information about the used interactive
interpreter; just to show you the "experience" of new Python
user. (This is what I'm showing to potential Python devs who
are interested in this tool; I know Python and use it sinc
New submission from Jean-Michel Fauth :
Now, that the PEP 414 has been accepted, I can
only strongly recommend to fix the problem
of unicode literals as a partial workaround.
>>> print u'abcœé€'
abcé
>>>
If these six characters are not rendered correctly, you
shou
Jean-Michel Fauth added the comment:
> Ezio Melotti
Good catch.
I'm not complaining. I just find funny to see the number of editors
not "colorizing" this kind of Python valid expressions. (IDLE included)
For me, subject close.
--
Jean-Michel Fauth added the comment:
I have done a little bit hd/files archeology and
found some of my comments.
Pointing on number litterals is probably wrong. The fact
is that, this happens with practically any expression. And
strangely, not all keywords (constructs?) are affected
New submission from Jean-Michel Fauth :
Can this be fixed? As far as I can remember (ver. 1.5.6),
it has always existed. Python does not crash, I find it
inelegant. Should it not be a SyntaxError?
Side effect. Searching for keywords, (eg. with re, "\b") may
practically always implies
Jean-Michel Fauth added the comment:
Œ, œ or even & are historically ligatures or "ligatured forms".
In the French typography, they are "single plain letters" and
they belong the group of the 42 letters used in the French
typography.
Typographically speaking, usin
New submission from Jean-Michel Fauth :
Just relying a discussion open on comp.lang.python,
http://groups.google.com/group/comp.lang.python/browse_thread/thread/771aa9081ad6584c#
1) Windows 7, open PowerShell
2) Change code page to cp65001
3) Launch Python3.1.2 or Python3.2.rc1 -> crash
Jean-Michel Fauth added the comment:
2010/6/4 Ãric Araujo
>
> Ãric Araujo added the comment:
>
> Could you think of a way to improve the docs on that point?
>
> --
>
> Quick and dirty answer.
I have ~10 years experience with Python and it seems
to me the
Jean-Michel Fauth added the comment:
2010/6/4 R. David Murray
>
> R. David Murray added the comment:
>
> This is as documented:
>
> http://docs.python.org/dev/3.0/library/io.html#io.TextIOBase.newlines
>
> The keyword argument is named 'newline', the att
New submission from Jean-Michel Fauth :
I was confused about the newline argument/attribute
in the misc. classes of the io module until I realize
there is a spelling issue between the docs and the
real implementation. (Py 2.6.5, Py2.7b2). Py 3.x not
tested.
>>> sys.version
2.7b2 (r2
New submission from Jean-Michel Fauth :
>>> sys.version
2.6.5 (r265:79096, Mar 19 2010, 21:48:26) [MSC v.1500 32 bit
(Intel)]
>>> import re
>>> re.match("[-+]?[0-9]+[.]?[0-9]*([eE][-+]?[0-9]+)?", "1.23e-4").group()
1.23e-4
>>> re.search(&qu
New submission from Jean-Michel Fauth :
The "codecs — Codec registry and base classes" part of
the documentions (Python 2.6.4, 2.7.a?, 3.1.1) does not
mention the existence of the iso-8859-16 codec.
--
assignee: georg.brandl
components: Documentation
messages: 101047
nosy: ge
Jean-Michel Fauth added the comment:
Wow! I never been aware of this (documentation, dir(), __doc__)
Indeed:
>>> cStringIO.StringIO()
>>> cStringIO.StringIO('abc')
Sorry for the noise.
--
___
Python tracker
<h
New submission from Jean-Michel Fauth :
There is a malformed string in the module cStringIO.
StringI <--> StringIO
>>> sys.version
2.6.4 (r264:75708, Oct 26 2009, 08:23:19) [MSC v.1500 32 bit (Intel)]
>>> StringIO.StringIO('123')
>>> cStringIO.
New submission from Jean-Michel Fauth :
I did not find any report about this.
Windows 7, Python 2.6.4
>>> float('inf') == float('inf')
True
>>> float('-inf') == float('-inf')
True
>>> float('-inf') == float('
New submission from Jean-Michel Fauth :
When toying with the "with" statement, I fell on this:
Python 2.6.4
>>> with open('abc.txt', 'r') as f:
for line in f:
print line.rstrip()
abc
def
>>>
>>&g
Ravon Jean-Michel added the comment:
It works in python 2.5. Why not in jython?
--
nosy: +jmravon
title: IDLE - configDialog - new layout for key config -> Cannot write an array
in a file opened in r+b mode.
___
Python tracker
&l
Jean-Michel Fauth added the comment:
It is true, that on Windows the "mime types", .py, .pyw point to a
specific version of Python.
Having Python 2.4, 2.5, 2.6, 3.0, 3.1 installed on my hd and
applications using these (different) versions, I am *very glad* on that
system, al
Jean-Michel Fauth added the comment:
Quick feedback from a Windows user.
I made a few more tests with the freshly installed Pyton 3.1a1. The
compile() function is running very well.
As a side effect, it now possible to write an "execfile()" without
any problem. Tests with execfile(
Jean-Michel Fauth added the comment:
> Victor
Yes, I could, but I think this is not an IDLE issue, I'm just
using IDLE to illustrate the problem. I got the same when I'm
working from within an editor or with my interactive interpreter
I wrote for the fun.
Code in the editor:
Jean-Michel Fauth added the comment:
When I was preparing some test examples to be submitted here.
I noticed the module codeop.py used by the InteractiveInterpreter,
does not like byte strings very much.
IDLE, Python 3.0.1, winxp sp2
>>> source = b'print(999)'
>>&g
New submission from Jean-Michel Fauth :
A few hours ago I sent a comment to the issue #4626. I didn't notice the
issue was closed. So I repeat it here. I'm interested in comments
because I have the feeling it is still a pending annoying isssue.
---
I'm glad to have discovere
Jean-Michel Fauth added the comment:
I'm glad to have discovered this topic. I bumped into something similar
when I toyed with an interactive interpreter.
from code import InteractiveInterpreter
ii = InteractiveInterpreter()
source = ...
ii.runsource(source)
What should be the encodin
Jean-Michel Fauth <[EMAIL PROTECTED]> added the comment:
2008/11/17 Raymond Hettinger <[EMAIL PROTECTED]>
>
> Raymond Hettinger <[EMAIL PROTECTED]> added the comment:
>
> Feature :-)
>
> You will get the expected result if you skip the step where you ran
New submission from Jean-Michel Fauth <[EMAIL PROTECTED]>:
win XP sp2, Py3.0c2
I had to face an annoying problem when iterating over a map object.
With a range class, this works
>>> r = range(5)
>>> list(r)
[0, 1, 2, 3, 4]
With dict_keys/values/items objects, the fol
New submission from Jean-Michel Fauth <[EMAIL PROTECTED]>:
XP SP2 fr_CH cp1252
I have always found, there are some inconsistencies in the Python <=2.5
serie regarding the char endodings, especially the iso-8859-1, cp1252,
iso-8859-15 encodings.
I do not know if this must be considered
Jean-Michel Fauth <[EMAIL PROTECTED]> added the comment:
I think the problem is fixed.
See issue 3905.
--
nosy: +jmfauth
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Jean-Michel Fauth <[EMAIL PROTECTED]> added the comment:
> Georg Brandl
Thanks, patch applied on w2k+sp4 box, swiss french, Python 3.0rc1.
IDLE is working fine.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Jean-Michel Fauth <[EMAIL PROTECTED]> added the comment:
Python 3.0rc1
If the lines are now displayed correctly, I think there is still a
numbering issue, a +1 offset.
Python 2.5.2
# -*- coding: cp1252 -*- <<<< line 1, first line
s = 'abc'
import dummy
New submission from Jean-Michel Fauth <[EMAIL PROTECTED]>:
3.0rc1: When toying and attempting to import the scrolledtext module, I
noticed the tkinter library path is no more by default included in the
sys.path.
Unfortunate omission or new Python 3.0 design?
C:\Python30>python
Pyth
Jean-Michel Fauth <[EMAIL PROTECTED]> added the comment:
Just for information and from an end user perspective.
I have tried to replace the socketserver.py from the original 3.0rc1
distribution by the socketserver.py as proposed by Benjamin Peterson
(r66520).
Script difference (li
Jean-Michel Fauth <[EMAIL PROTECTED]> added the comment:
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.
C:\>cd python30
C:\Python30>python Lib/idlelib/idle.py
Traceback (most recent call last):
File "", line 1, in
File "C:\
Jean-Michel Fauth <[EMAIL PROTECTED]> added the comment:
I do not really know if this is related to this, but I suspect yes.
On my w2k+sp4 box, swiss french, Python 3.0rc1, IDLE does not start or
more precisely it starts by opening the following message box:
Subprocess Startup
Jean-Michel Fauth <[EMAIL PROTECTED]> added the comment:
Py3.0b2. This bug seems to be quite annoying. Especially when one works
with a main module importing modules which are importing modules and so
on, all modules having an encoding declaration. The Traceback (and the
user) is (are) a
New submission from Ravon Jean-Michel:
Here is my source:
def truc ():
line = ' hi \n'
line1 = re.sub('$', 'hello', line)
line2 = re.sub('$', 'you', line1)
print line2
Here is what I get:
>>> trace.truc()
hi hel
41 matches
Mail list logo
