Ronald Oussoren added the comment:
I agree that there's probably no good solution here.
Catching TypeError would require emitting a lot more byte code, and would
change the semantics of augmented assignment, in particular it wouldn't really
be an assignment statement anymore (and hides some
Changes by Tillmann Karras til...@gmail.com:
--
nosy: +Tilka
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17140
___
___
Python-bugs-list mailing
Roundup Robot added the comment:
New changeset c0f2b038fc12 by Charles-François Natali in branch 'default':
Issue #17683: socket module: return AF_UNIX addresses in Linux abstract
http://hg.python.org/cpython/rev/c0f2b038fc12
--
nosy: +python-dev
___
Charles-François Natali added the comment:
Antoine, I need your help :-)
http://buildbot.python.org/all/builders/x86 Gentoo Non-Debug
3.x/builds/4311/steps/test/logs/stdio
==
ERROR: testLinuxAbstractNamespace
Anselm Kruis added the comment:
I take it you have more than 16GB of RAM?
I used a system with 16GB Ram.
What happens if you replace sys.maxint with sys.maxsize in test_overflow?
The test passes. Both mul and imul raise MemoryError.
--
___
Python
New submission from Bohuslav Slavek Kabrda:
Hi,
I'm getting these warnings with -fstrict-aliasing, compiling Python 3.3.2
(compiling with gcc 4.4.7):
/builddir/build/BUILD/Python-3.3.2/Python/ceval.c: In function
'PyEval_EvalFrameEx':
/builddir/build/BUILD/Python-3.3.2/Python/ceval.c:1006:
Charles-François Natali added the comment:
Hum, IIUC, basically what happens is that the user could - and still
can - pass arbitrary bytes as address (which is legtit), but depending
on the encoding, getsockaddr() and friends might blow up when decoding
it.
If that's correct, that's bad, and
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13146
___
Arfrever Frehtes Taifersar Arahesis added the comment:
Your Python/ceval.c has custom patches applied. Line 1006 is a comment in
unmodified Python/ceval.c in Python 3.3.2. This bug might be caused by your
patches.
Alternatively it is a bug in GCC 4.4.7.
I get 0 warnings for unmodified
Mark Lawrence added the comment:
Is this still a problem given that both Python and Solaris have moved on?
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6299
___
Guilherme Simões added the comment:
Now I can apply the patch successfully and everything seems to be working.
Thanks, Terry.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15392
___
Bohuslav Slavek Kabrda added the comment:
Hmm, you're probably right. The problem seems to be in downstream redefinition
of READ_TIMESTAMP. Sorry for the fuzz, closing.
--
status: open - closed
___
Python tracker rep...@bugs.python.org
Changes by Charles-François Natali cf.nat...@gmail.com:
--
resolution: - fixed
stage: patch review - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17917
Changes by Charles-François Natali cf.nat...@gmail.com:
--
stage: needs patch - patch review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17914
___
Anselm Kruis added the comment:
Just for the records: the patch works as expected.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18015
___
___
Changes by Ralf Schmitt python-b...@systemexit.de:
--
nosy: +schmir
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18015
___
___
Python-bugs-list
Tshepang Lekhonkhobe added the comment:
@antoine
I don't understand This is a lot of code churn, but it touches code that is
unlikely to be modified otherwise, so I guess it's ok.. What does it mean it's
okay when it touches on code that's unlikely to be modified?
--
nosy: +tshepang
Roundup Robot added the comment:
New changeset 56f25569ba86 by Serhiy Storchaka in branch 'default':
Issue #17900: Allowed pickling of recursive OrderedDicts. Decreased pickled
http://hg.python.org/cpython/rev/56f25569ba86
--
nosy: +python-dev
___
Charles-François Natali added the comment:
I don't understand This is a lot of code churn, but it touches code that is
unlikely to be modified otherwise, so I guess it's ok.. What does it mean
it's okay when it touches on code that's unlikely to be modified?
The problem with refactoring is
Changes by Serhiy Storchaka storch...@gmail.com:
--
resolution: - fixed
stage: patch review - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17900
Bohuslav Slavek Kabrda added the comment:
Actually, this appears on vanilla Python 3.3 with -DWITH_TSC:
Python/ceval.c: In function ‘PyEval_EvalFrameEx’:
Python/ceval.c:986:5: warning: dereferencing type-punned pointer will break
strict-aliasing rules [-Wstrict-aliasing]
Serhiy Storchaka added the comment:
Not a bad idea.
How about implementation? Here is updated patches for 3.x and 2.7. Note that in
2.7 I split codecs table as in 3.x.
--
Added file: http://bugs.python.org/file30331/doc_codecs_impl.patch
___
Changes by Serhiy Storchaka storch...@gmail.com:
Added file: http://bugs.python.org/file30332/doc_codecs_impl-2.7.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17844
___
Changes by Serhiy Storchaka storch...@gmail.com:
Removed file: http://bugs.python.org/file30013/doc_codecs_impl.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17844
___
Antoine Pitrou added the comment:
Hum, IIUC, basically what happens is that the user could - and still
can - pass arbitrary bytes as address (which is legtit), but depending
on the encoding, getsockaddr() and friends might blow up when decoding
it.
Shouldn't the surrogateescape error
Richard Oudkerk added the comment:
Given that the change could only be made to 3.4, and we already have
concurrent.futures.ThreadPoolExecutor, I am not sure there is much point to
such a change now.
--
nosy: +sbt
___
Python tracker
Nick Coghlan added the comment:
I like the idea of splitting the table in 2.7 rather than using a result type
column. However, the two intro paragraphs need a bit of work. How does the
following sound:
1. Create a new subheading at the same level as the current Standard
Encodings heading:
Nick Coghlan added the comment:
Thread Pools can be handy when you want to do explicit message passing, rather
than the call-and-response model favoured by the futures module.
--
___
Python tracker rep...@bugs.python.org
Changes by Paul Moore p.f.mo...@gmail.com:
--
nosy: +pmoore
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12641
___
___
Python-bugs-list mailing
Richard Oudkerk added the comment:
I don't understand what you mean by explicit message passing and
call-and-response model.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17140
___
Nick Coghlan added the comment:
Future are explicitly about kicking off a concurrent call and waiting for a
reply. They're great for master/slave and client/server models, but not
particularly good for actors and other forms of peer-to-peer message passing.
For the latter, explicit pools and
Changes by Łukasz Langa luk...@langa.pl:
--
resolution: - works for me
stage: - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17453
___
Serhiy Storchaka added the comment:
However, the two intro paragraphs need a bit of work.
Yes, it's a help which I needed. Thank you.
However your wording is not entirely correct. In 2.7 binary-to-binary codecs
and rot-13 works with Unicode strings (only ascii-compatible) as with bytes
Changes by Ken Giusti kgiu...@gmail.com:
--
nosy: +Ken.Giusti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8240
___
___
Python-bugs-list mailing
Oscar Benjamin added the comment:
I'd really like to get a resolution on this issue so I've tried to gather some
more information about this problem by asking some questions in the mingw-users
mailing list. The resulting thread can be found here:
Nick Coghlan added the comment:
While the Python 2 text model was almost certainly a necessary transition step
to full unicode support, it is things like this that highlight how
fundamentally broken implicit conversion turned out to be at a conceptual level
:P
Perhaps the following would
Łukasz Langa added the comment:
For the record, my class-based approach from 2010 still available here:
https://bitbucket.org/ambv/nattyprint
--
versions: +Python 3.4 -Python 3.3
___
Python tracker rep...@bugs.python.org
Changes by Łukasz Langa luk...@langa.pl:
--
Removed message: http://bugs.python.org/msg138819
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7434
___
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7434
___
___
Python-bugs-list mailing
Richard Oudkerk added the comment:
As far as I can see they are mostly equivalent. For instance, ApplyResult (the
type returned by Pool.apply_async()) is virtually the same as a Future.
When you say explicit message passing, do you mean creating a queue and
making the worker tasks put
Nick Coghlan added the comment:
Armin pointed out in
http://lucumr.pocoo.org/2013/5/21/porting-to-python-3-redux/ that one nasty
consequence of the remaining part of this bug and issue 8743 is making it much
harder than it should be to use the ItemsView, KeysView and ValuesView from
Nick Coghlan added the comment:
Armin pointed out in
http://lucumr.pocoo.org/2013/5/21/porting-to-python-3-redux/ that one nasty
consequence of the remaining part of issue 2226 and this bug is making it much
harder than it should be to use the ItemsView, KeysView and ValuesView from
Senthil Kumaran added the comment:
Hello zhaoqifa,
Your suggestion for the solution looks good to me. Instead of cd-ing to each
dir, you cd to target dir when ftp url is accessed.
Two things to consider.
1) Will the above change have any security implications. It does not seem to
me. But I
Nick Coghlan added the comment:
No, I mean implementing communicating sequential processes with independent
state machines passing messages to each other. There aren't necessarily any
fixed request/reply pairs. Each actor has a mailbox, which is a queue that
you dump its messages into. If you
Paul Moore added the comment:
+1 for Oscar's proposed fix. It sounds like a sensible approach.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12641
___
Charles-François Natali added the comment:
Nevermind, it seems changing regen is not necessary. Patch is in attachment.
Go ahead!
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17996
___
David Cuddihy added the comment:
I apologize for not posting the strace output - I didn't see the request until
today.
Libc getcwd() is indeed failing - when I run a c program which calls getcwd()
and prints the output, the call to getcwd() fails - errno is ENOENT and the
buffer is null.
Richard Oudkerk added the comment:
It's a very different architecture from that assumed by futures,
so you need to drop down to the pool layer rather than using the
executor model.
AIUI an ThreadPoolExecutor object (which must be explicitly created)
represents a thread/process pool, and it
Charles-François Natali added the comment:
Martin, do you think your latest patch can be committed?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13483
___
Serhiy Storchaka added the comment:
Thank you Nick. Here is an updated patch for 2.7.
--
Added file: http://bugs.python.org/file30333/doc_codecs_impl-2.7_2.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17844
Changes by Florent Xicluna florent.xicl...@gmail.com:
--
nosy: +flox
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17844
___
___
Python-bugs-list
Changes by Serhiy Storchaka storch...@gmail.com:
Removed file: http://bugs.python.org/file30332/doc_codecs_impl-2.7.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17844
___
New submission from Donal Duane:
Hi,
We have 2 Python 3.2 builds - one on x86 (Solaris 10), and one on SPARC
(Solaris 10).
The x86 build works fine for SSL, but the SPARC build was either built without
SSL support pecified, or, there was an issue with the build.
$ bash $ .
Antoine Pitrou added the comment:
I'm thinking that perhaps we should simply enable
SSL_MODE_ACCEPT_MOVING_WRITE_BUFFER by default. Ben, what do you think? Does
the current behaviour allow to catch bugs?
--
type: behavior - enhancement
versions: +Python 3.4 -Python 3.3
Roundup Robot added the comment:
New changeset 6ab88d6527f1 by R David Murray in branch '3.3':
#17973: fix technical inaccuracy in faq entry (it now passes doctest).
http://hg.python.org/cpython/rev/6ab88d6527f1
New changeset 26588b6a39d9 by R David Murray in branch 'default':
merge #17973: fix
Pascal Chambon added the comment:
Well, since it's a tough decision to make (erasing all children modules when
rolling back parent, or instead reconnecting with children on 2nd import of
parent), I guess it should be discussed on python-dev first, shouldn't it ?
--
Antoine Pitrou added the comment:
Do you build Python yourself? If so, check for any errors pertaining to the ssl
module in the make output. _ssl_failed.so implies the module was built, but
the resulting file failed to be imported dynamically by the interpreter, and
thus was renamed to
Martin v. Löwis added the comment:
Donal, please understand that this tracker is primarily to report bugs, not to
get support, so help on possible work-arounds is out of scope.
That said, if you want to investigate further, please rename _ssl_failed.so
back to _ssl.so, and then re-perform the
Antoine Pitrou added the comment:
I will probably wait for PEP 442 adoption before finalizing this issue.
--
dependencies: -Generator cleanup without tp_del
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17934
Pete Forman added the comment:
Another +1 for Oscar. I've just done an install of Python 2.7.5 and had to hack
cygwinccompiler.py again. I'm using mingw with gcc 4.6.2 on Windows 7.
--
nosy: +Pete.Forman
___
Python tracker rep...@bugs.python.org
Martin v. Löwis added the comment:
Oscar: I agree with your analysis, but it is incomplete. There is a group
C: Users who have only cygwin gcc 4.x installed
For those, the current setup will produce an error message, essentially telling
them that the need to fix something (specifically: edit
Martin v. Löwis added the comment:
Antoine's request for benchmarks still stands. I continue to think that it
should be applied even in absence of benchmarks. In the absence of third
opinions on this specific aspect, I don't think it can be applied.
--
Tshepang Lekhonkhobe added the comment:
Ok, I thought so. Just wanted to make sure.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17917
___
___
W. Owen Parry added the comment:
I suggest that this is a documentation issue.
I have seen three classes of functions is os and os.path
i - those which operate on path names only (os.path.join, os.path.dirname, etc)
and do not depend on the state of the file system. Since these are string
Simon Nicolussi added the comment:
Requests 1.2.1 has been released to address this issue. An origin_req_host
property has been added to the request object as a workaround.
The original problem of mismatched documentation and behaviour still persists.
--
R. David Murray added the comment:
regrtest now works for me, as does running test_idle.py directly and the simple
minded unittest call:
./python -m unittest test.test_idle
However, running an individual test doesn't. I don't see this as a
show-stopper for committing this, but rather
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11959
___
___
Python-bugs-list mailing
Giampaolo Rodola' added the comment:
Looking back at this I think that allowing a map argument to be passed to
SMTPChannel in order to allow running handlers in separate threads can be
reasonable after all.
I don't understand why create_socket() signature needs to be changed though.
Roundup Robot added the comment:
New changeset 155e6fb309f5 by Giampaolo Rodola' in branch 'default':
Fix issue #17996: expose socket.AF_LINK constant on BSD and OSX.
http://hg.python.org/cpython/rev/155e6fb309f5
--
nosy: +python-dev
___
Python
Changes by Giampaolo Rodola' g.rod...@gmail.com:
--
assignee: - giampaolo.rodola
resolution: - fixed
stage: - committed/rejected
status: open - closed
type: - enhancement
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17996
Vinay Sajip added the comment:
I wasn't suggesting changing the signature of create_socket, I just thought
that it needed to be reimplemented because it didn't pass a map to set_socket.
I've had a look at it again, and a reimplementation of create_socket doesn't
seem to be needed, after all,
Mark Lawrence added the comment:
Slipped under the radar?
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2449
___
___
Roundup Robot added the comment:
New changeset 8408eed151eb by Serhiy Storchaka in branch '2.7':
Issue #17979: Fixed the re module in build with --disable-unicode.
http://hg.python.org/cpython/rev/8408eed151eb
--
nosy: +python-dev
___
Python tracker
Serhiy Storchaka added the comment:
The re module with --disable-unicode is still broken on platform with
sizeof(int) 4, but totally portable fix requires more code.
--
resolution: - fixed
stage: patch review - committed/rejected
status: open - closed
Mark Lawrence added the comment:
Even if the original patch is valid it will need reworking as xmlrpclib isn't
in Python 3, the code is now in xmlrpc/client. It also looks as if dump_string
has been renamed dump_unicode.
--
nosy: +BreamoreBoy
___
Mark Lawrence added the comment:
Could someone answer the question posed in msg98154 please.
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6461
___
Mark Lawrence added the comment:
Would someone like to propose a documentation patch that clarifies this
situation.
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7760
Amaury Forgeot d'Arc added the comment:
The patch goes in the right direction: consistently reject non-8bit encodings
which the current implementation does not support.
- please add a unit test
- remove usage of PyUnicodeObject and the Stupid to access directly comment,
they are outdated.
Oscar Benjamin added the comment:
On 21 May 2013 17:21, Martin v. Löwis rep...@bugs.python.org wrote:
C: Users who have only cygwin gcc 4.x installed
For those, the current setup will produce an error message, essentially
telling them that the need to fix something (specifically: edit
Changes by Richard Oudkerk shibt...@gmail.com:
--
nosy: +sbt
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6461
___
___
Python-bugs-list mailing
Terry J. Reedy added the comment:
It works when one uses the right dotted name ;-)
D:\Python\dev\py33\PCbuildpython_d -m unittest -v
idlelib.idle_test.test_calltips.Test_get_entity.test_bad_entity
test_bad_entity (idlelib.idle_test.test_calltips.Test_get_entity) ... ok
New submission from Marc:
Using TkInter as gui, running a module that worked in 3.0 (I believe).
It is trying to print a warning message about
RuntimeWarning: overflow encountered in double_scalars
and stops my process (running eval) returning this error
File
Ben Darnell added the comment:
I vote for enabling SSL_MODE_ACCEPT_MOVING_WRITE_BUFFER by default. It can
catch mistakes (i.e. failure to check the return value of send) in Python just
as easily as in C, but I don't think those mistakes are common enough to be
worth the headache of this
Terry J. Reedy added the comment:
Attached file tests framework by running idle_tests 6 different ways. Run with
the executable that you want to run the tests with as is uses sys.executable. I
plan to move it into idle_tests.
--
Added file:
New submission from Carlos Nepomuceno:
It[1] says:
Since str.format() is quite new, a lot of Python code still uses the %
operator. However, because this old style of formatting will eventually be
removed from the language, str.format() should generally be used.
[1]
85 matches
Mail list logo
