Antoine Pitrou pit...@free.fr added the comment:
Here is a patch.
--
keywords: +patch
stage: needs patch - patch review
Added file: http://bugs.python.org/file24060/binasciistr.patch
___
Python tracker rep...@bugs.python.org
Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset 20b52be99b5d by Antoine Pitrou in branch 'default':
Issue #13634: Add support for querying and disabling SSL compression.
http://hg.python.org/cpython/rev/20b52be99b5d
--
nosy: +python-dev
Antoine Pitrou pit...@free.fr added the comment:
Now committed in 3.3.
--
resolution: - fixed
stage: patch review - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13634
Charles-François Natali neolo...@free.fr added the comment:
As I said, I'm skeptical about the benefit vs maintenance burden ratio,
especially since cPython doesn't target performance critical applications. I
just fear that's a lot of intrusive code which will only be used by a handful
of
Charles-François Natali neolo...@free.fr added the comment:
1. On FreeBSD, we must assume that every blocking system call, in
*every thread*, can be interrupted, and we need to catch EINTR.
That's true for every Unix. Every blocking syscall can return EINTR, and there
are may non restartable
Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset c9facd251725 by Charles-François Natali in branch '2.7':
Followup to issue #11867: Use socketpair(), since FreeBSD 8 doesn't really
http://hg.python.org/cpython/rev/c9facd251725
New changeset 9dee8a095faf by
Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset eb8d62706d5f by Antoine Pitrou in branch 'default':
Issue #13637: a2b functions in the binascii module now accept ASCII-only
unicode strings.
http://hg.python.org/cpython/rev/eb8d62706d5f
--
nosy:
New submission from Antoine Pitrou pit...@free.fr:
Similarly to #13637 for the binascii module, the decoding functions in the
base64 module could accept ASCII-only unicode strings.
--
components: Library (Lib)
keywords: easy
messages: 149912
nosy: pitrou
priority: normal
severity:
Antoine Pitrou pit...@free.fr added the comment:
Committed now.
--
resolution: - fixed
stage: patch review - committed/rejected
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13637
___
Changes by Antoine Pitrou pit...@free.fr:
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13637
___
___
Python-bugs-list
Antoine Pitrou pit...@free.fr added the comment:
This looks like a reasonable request to me, and the patch looks generally ok as
well.
--
nosy: +neologix, pitrou
stage: - patch review
versions: -Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.4
New submission from Joonas Kuorilehto oh8...@gmail.com:
Reproduction:
import urllib
urllib.urlopen(https://example.com/;)
Enter username for Test Site at example.com: user
Enter password for user in Test Site at example.com: top secret
Enter username for Test Site at example.com:
# If the
Antoine Pitrou pit...@free.fr added the comment:
One nit: the patch needs versionadded tags for the two new functions.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12708
___
Changes by Joonas Kuorilehto oh8...@gmail.com:
--
nosy: +joneskoo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9725
___
___
Python-bugs-list
Changes by Antoine Pitrou pit...@free.fr:
--
nosy: +lars.gustaebel
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13639
___
___
Python-bugs-list
anatoly techtonik techto...@gmail.com added the comment:
A good analysis of the issue is made by Jason Conti at Ubuntu bug report
mentioned in the first commit.
--
title: `setup.py register` fails with traceback - `setup.py register` fails if
long_description contains RST
anatoly techtonik techto...@gmail.com added the comment:
s/commit/comment/ sry.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13614
___
___
samwyse samw...@gmail.com added the comment:
[issue5847] fixed in 2.7/3.1
--
resolution: - out of date
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6321
___
Tycho Andersen ty...@tycho.ws added the comment:
Attached is a patch which contains a testcase as well. A few notes about this
testcase:
1. I couldn't figure out how to get it to run correctly after all the other
tests had run, so I had to run it first. This seems lame. One possible fix is
Hynek Schlawack h...@ox.cx added the comment:
Thanks for the feedback Antoine!
I updated the patch to latest default tip and added the requested tags to the
docs.
--
hgrepos: +97
___
Python tracker rep...@bugs.python.org
Changes by Hynek Schlawack h...@ox.cx:
Added file: http://bugs.python.org/file24062/8a9e14cda106.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12708
___
Changes by Hynek Schlawack h...@ox.cx:
Removed file: http://bugs.python.org/file22860/mp-starmap-w-docs.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12708
___
Changes by Christian Häggström paj...@kalvdans.no-ip.org:
--
nosy: +chn
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3905
___
___
Charles-François Natali neolo...@free.fr added the comment:
Looks good to me, except for another minor nit:
the elements of the `iterable` are expected to be tuples
AFAICT, you just require the elements of `ìterables` to be iterables, not
necessarily tuples.
--
Hynek Schlawack h...@ox.cx added the comment:
You're right. I've updated the docs accordingly, thanks!
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12708
___
Changes by Hynek Schlawack h...@ox.cx:
Added file: http://bugs.python.org/file24063/c02fbcda56f3.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12708
___
Changes by Hynek Schlawack h...@ox.cx:
Removed file: http://bugs.python.org/file24062/8a9e14cda106.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12708
___
New submission from Martin gzl...@googlemail.com:
Currently when running Python on a non-OSX posix environment under either the C
locale, or with an invalid or missing locale, it's not possible to operate
using unicode filenames outside the ascii range. Using bytes works, as does
reading
R. David Murray rdmur...@bitdance.com added the comment:
I'm not sure why having a locale set to C or something invalid should be
considered a Python bug. You have to handle un-decodable filenames no matter
what you do, since things aren't always encoded in utf-8 on non-OSX unix even
when
STINNER Victor victor.stin...@haypocalc.com added the comment:
Currently when running Python on a non-OSX posix environment
under either the C locale, or with an invalid or missing locale,
it's not possible to operate using unicode filenames outside
the ascii range.
It was already
STINNER Victor victor.stin...@haypocalc.com added the comment:
under either the C locale, or with an invalid or missing locale
The right fix is to fix your locale, not Python.
--
___
Python tracker rep...@bugs.python.org
Martin gzl...@googlemail.com added the comment:
I'm not sure why having a locale set to C or something invalid should be
considered a Python bug. You have to handle un-decodable filenames no
matter what you do, since things aren't always encoded in utf-8 on non-OSX
unix even when that is
Martin gzl...@googlemail.com added the comment:
It was already discussed: using a different encoding for filenames and for
other things is really not a good idea. The main problem is the interaction
with other programs.
Yes, for many programs, a change like this will mean they create the
Roger Serwy roger.se...@gmail.com added the comment:
I went through the changes in idlelib20101012_From_r32a3.patch.
A lot of the changes are for using relative imports. Those changes aside, here
is a list of issues that this patch covers. Most of these issues already have
patches that are
Roger Serwy roger.se...@gmail.com added the comment:
minor mistake - issue3559 Pasted \n not same as typed \n
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10079
___
Ned Deily n...@acm.org added the comment:
Thanks, Roger. It would also be helpful if you ascertain for the overlaps
which of the two versions is newer, the individual issue/path or the large
feature diff. The relative import changes should not be applied in the
standard library; they were
David Butler croe...@gmail.com added the comment:
I have 10 identical test machines running this this code ( operating systems
are cloned ). I am not usning valgrind in these tests, it was causing various
issues...
(gdb) info sharedlibrary
FromTo Syms Read Shared Object
David Butler croe...@gmail.com added the comment:
This also looks familiar:
http://bytes.com/topic/python/answers/36901-fatal-error-gc-object-already-tracked
semi-randomly locks somewhere outside my C-code (after returning to
python), and semi-randomly issues a Fatal error: GC object already
David Butler croe...@gmail.com added the comment:
I think I have found the problem! I took a closer look at the Fatal error core:
#0 0xb76fe424 in __kernel_vsyscall ()
#1 0xb740ccb1 in *__GI_raise (sig=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#2 0xb740e3f2 in *__GI_abort () at
Amaury Forgeot d'Arc amaur...@gmail.com added the comment:
Hey, you found it!
PySide::DynamicSlotDataV2::callback() calls PyMethod_New() without getting the
GIL. The Python allocator is not thread-safe, operations are supposed to be
serialized by this Global Interpreter Lock.
I suggest to
David Butler croe...@gmail.com added the comment:
resolved as wont fix, because its not python's fault :)
--
resolution: - wont fix
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13616
Martin Pool m...@sourcefrog.net added the comment:
I'm not sure why having a locale set to C or something invalid should be
considered a Python bug.
Programs like bzr that hit these problems can tell their users, either in the
docs or an error message, change your locale to a UTF-8 one.
STINNER Victor victor.stin...@haypocalc.com added the comment:
If there was a separate LC_FILENAMES then Python could respect
that and insist people set it, but there isn't.
During 1 month, we had PYTHONFSENCODING environment variable. It was not a good
idea. Again: please read the
Marco Scataglini atlant...@gmx.com added the comment:
Well I checked 'SearchBar' IDLE extension and is not bad... has some minor
bugs, nothing major just very very minor quirky behavior, but nothing that
seems to impair functionality AFAIK.
It should be cleaned up and added to release in place
STINNER Victor victor.stin...@haypocalc.com added the comment:
There are two problems with this: one is just the practical
one that it scales poorly to have to tell every user to do this
and to take them through working out how to set this in a way
that covers cron jobs, daemons, things run
Martin Pool m...@sourcefrog.net added the comment:
On 21 December 2011 11:01, STINNER Victor rep...@bugs.python.org wrote:
Again: please read the discussion (in closed issues) explaing why we removed
it (and which problems it introduced).
There's a lot of history, so I'm not sure exactly
Martin Pool m...@sourcefrog.net added the comment:
On 21 December 2011 11:26, STINNER Victor rep...@bugs.python.org wrote:
I never checked which locale is used by default for programs called by cron.
So I checked: on Fedora 16, programs start with a very few environment
variables, and LANG
STINNER Victor victor.stin...@haypocalc.com added the comment:
The main problem I see being discussed is that
changing the encoding after Python starts would
be dangerous, which I agree with, but we're not
proposing to do that.
Not after Python start. Using two encodings at the same would
Roger Serwy roger.se...@gmail.com added the comment:
I checked the submitted patches from the issues against the large patch by eye.
Guilherme's patches in these separate issues have the same contents:
issue1207589, issue1612262, issue1721083, issue6699, issue3359.
The large patch updates
STINNER Victor victor.stin...@haypocalc.com added the comment:
I would be possible to implement incremental decoder with mbsrtowcs() and
incremental encoder with wcsrtombs(), by serializing mbstate_t to a long
integer (TextIOWrapper.tell() does something like that). The problem is that
STINNER Victor victor.stin...@haypocalc.com added the comment:
I should not write comments so late :-p
Not after Python start. Using two encodings at the same would just ...
at the same time
... because I would like to inconsistency.
because it would lead to inconsistencies
--
Martin gzl...@googlemail.com added the comment:
During 1 month, we had PYTHONFSENCODING environment variable. It was not a
good idea.
I strongly agree. There is no sense in having a separate configurable value,
anyone who would think about using a PYTHONFSENCODING should just change their
Antoine Pitrou pit...@free.fr added the comment:
So, you're complaining about something which works, kind of:
$ touch héhé
$ LANG=C python3 -c import os; print(os.listdir())
['h\udcc3\udca9h\udcc3\udca9']
This makes robustly working with non-ascii filenames on different
platforms needlessly
Martin Pool m...@sourcefrog.net added the comment:
Thanks for the example.
Like you say, realistically, all data exchanged with other programs
and with the system needs to be in the same encoding. (User document
content may be in something else.)
On modern systems, this problem is solved by
Martin Pool m...@sourcefrog.net added the comment:
On 21 December 2011 12:16, Antoine Pitrou rep...@bugs.python.org wrote:
Antoine Pitrou pit...@free.fr added the comment:
So, you're complaining about something which works, kind of:
$ touch héhé
$ LANG=C python3 -c import os;
Antoine Pitrou pit...@free.fr added the comment:
The standard encoding is UTF-8.
How so? I don't know of any Linux or Unix spec which says so. If you get
the Linux heads to standardize this then I'll certainly be very happy
(and countless others will, too). But AFAIK this it not the case and I
Changes by Meador Inge mead...@gmail.com:
--
nosy: +meador.inge
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13607
___
___
Python-bugs-list
Meador Inge mead...@gmail.com added the comment:
With the new patch I see no benefits on the same micro-benchmarks you posted
(it is even slower for the smaller case) on a quad-core 64-bit F15 box:
BEFORE:
$ ./python -mtimeit def y(n): for x in range(n): yield x
sum(y(10))
100
Nick Coghlan ncogh...@gmail.com added the comment:
The thing that most appeals to me with this concept is moving closer to making
it possible to experiment with generator-style functionality in *extension*
modules (albeit extension modules that are coupled to private CPython APIs).
So, for
Changes by Jesús Cea Avión j...@jcea.es:
--
nosy: +jcea
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8098
___
___
Python-bugs-list mailing list
Changes by Eric Snow ericsnowcurren...@gmail.com:
--
nosy: +eric.snow
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8098
___
___
Python-bugs-list
Meador Inge mead...@gmail.com added the comment:
ECC is *not* available in the OpenSSL package provided on RedHat systems.
RedHat intentionally strips it due to patent concerns
(http://en.wikipedia.org/wiki/ECC_patents). Therefore committing this work
made it much more difficult to build
New submission from maniram maniram maniandra...@gmail.com:
When you run the following code, Python 3 (not Python 2) crashes.
Interestingly, Python 2.7 doesn't seem to be affected and correctly raises an
error about recursion ( so this must be a regression ).
The code's recursion should be
Changes by maniram maniram maniandra...@gmail.com:
--
title: Python crashes with this code. - Python 3 crashes with this code.
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13644
___
Changes by maniram maniram maniandra...@gmail.com:
--
title: Python 3 crashes with this code. - Python 3 crashes (segfaults) with
this code.
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13644
Benjamin Peterson benja...@python.org added the comment:
Python isn't crashing; it's bailing out of an impossible situation. It's not
clear what the correct behavior is, since you're basically preventing Python
from aborting the recursive behavior.
--
nosy: +benjamin.peterson
maniram maniram maniandra...@gmail.com added the comment:
But Python 2 doesn't crash after running the code.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13644
___
maniram maniram maniandra...@gmail.com added the comment:
Oops, to reproduce this bug after running the code run recurse().
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13644
___
Changes by Ned Deily n...@acm.org:
--
resolution: - duplicate
stage: needs patch - committed/rejected
status: open - closed
superseder: - IDLE/Win Installer: drop -n switch for 2.7/3.1; install 3.1 as
idle3
versions: +Python 2.7, Python 3.1 -Python 2.6
Changes by Ned Deily n...@acm.org:
--
resolution: out of date - duplicate
stage: - committed/rejected
superseder: - IDLE/Win Installer: drop -n switch for 2.7/3.1; install 3.1 as
idle3
___
Python tracker rep...@bugs.python.org
Petri Lehtinen pe...@digip.org added the comment:
What's the status of this issue?
FWIW, this is not only a problem with east asian characters:
ä äää
File stdin, line 1
ä äää
^
SyntaxError: invalid syntax
--
nosy: +petri.lehtinen
versions: +Python 3.2, Python 3.3
Antoine Pitrou pit...@free.fr added the comment:
Perhaps we should make these algorithms build conditional? Are these
patent issues of concern to us?
Well, if RedHat used the standard OPENSSL_NO_ECDH flag, it's easy
enough to fix compilation of the ssl module.
--
Changes by Antoine Pitrou pit...@free.fr:
--
status: closed - open
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13627
___
___
Python-bugs-list
73 matches
Mail list logo
