Changes by Richard Hansen :
Removed file: http://bugs.python.org/file15746/unicode_escape_tests.patch
___
Python tracker
<http://bugs.python.org/issue7615>
___
___
Pytho
Richard Hansen added the comment:
Attaching updated unit tests for the unicode_escape codec. I removed the
raw_unicode_escape tests and will attach a separate patch for those.
--
Added file: http://bugs.python.org/file15774/unicode_escape_tests.patch
Richard Hansen added the comment:
Attaching updated unit tests for the raw_unicode_escape codec.
--
Added file: http://bugs.python.org/file15775/raw_unicode_escape_tests.patch
___
Python tracker
<http://bugs.python.org/issue7
Richard Hansen added the comment:
> We'll need a patch that implements single and double quote escaping
> for unicode_escape and a \u style escaping of quotes for the
> raw_unicode_escape encoder.
OK, I'll remove unicode_escape_single_quotes.patch and update
unicode
Changes by Richard Hansen :
Removed file:
http://bugs.python.org/file15716/unicode_escape_single_quotes.patch
___
Python tracker
<http://bugs.python.org/issue7
Changes by Richard Hansen :
Removed file:
http://bugs.python.org/file15729/unicode_escape_single_and_double_quotes.patch
___
Python tracker
<http://bugs.python.org/issue7
Changes by Richard Hansen :
Removed file: http://bugs.python.org/file15771/unicode_escape_reorg.patch
___
Python tracker
<http://bugs.python.org/issue7615>
___
___
Pytho
Changes by Richard Hansen :
Removed file: http://bugs.python.org/file15774/unicode_escape_tests.patch
___
Python tracker
<http://bugs.python.org/issue7615>
___
___
Pytho
Changes by Richard Hansen :
Removed file: http://bugs.python.org/file15775/raw_unicode_escape_tests.patch
___
Python tracker
<http://bugs.python.org/issue7615>
___
___
Richard Hansen added the comment:
Attaching updated unit tests. The tests now check to make sure that single and
double quotes are escaped.
--
Added file: http://bugs.python.org/file15809/unicode_escape_tests.patch
___
Python tracker
<h
Richard Hansen added the comment:
Attaching a minimal patch:
* unicode_escape now backslash-escapes single and double quotes
* raw_unicode_escape now unicode-escapes single and double quotes
* raw_unicode_escape now unicode-escapes backslashes
* removes pickle's escaping workaroun
Richard Hansen added the comment:
Attaching a patch for an issue discovered while looking at the code:
* The UTF-16 decode logic in the Unicode escape encoders no longer reads past
the end of the provided Py_UNICODE buffer if the last character's value is
between 0xD800 and 0xDC00.
Richard Hansen added the comment:
Attaching a patch for another issue discovered while looking at the code:
* The Unicode escape encoders now check to make sure that the provided size
is nonnegative.
* C API documentation updated to make it clear that size must be nonnegative.
This patch
Richard Hansen added the comment:
Attaching a patch that eliminates duplicate code:
* Merge unicodeescape_string(), PyUnicode_EncodeRawUnicodeEscape(), and
modified_EncodeRawUnicodeEscape() into one function called
_PyUnicode_EncodeCustomUnicodeEscape().
This patch is meant to be applied
Richard King added the comment:
ok, thanks.
R. David Murray wrote:
> R. David Murray added the comment:
>
> Since it's been almost a year and the OP hasn't responded with an
> updated patch, I'm closing this as out of date.
>
> --
> nosy: +bit
New submission from Richard Lowe :
The GetoptError exception raised by getopt.getopt() to indicate errors in
provided arguments seems intended to be displayed to the user[1], but is not
localized and doesn't contain enough information, short of interpreting the
error string, for consume
Richard Jones added the comment:
Giampaolo,
I think I can see where you're coming from: assuming that someone else must
have also had to resort to the name-mangling hack to extend the class? In that
case yes, my patch would break their code. I'll look at re-working it to use
Richard Jones added the comment:
After discussing with core devs at the EuroPython sprint I will implement a
different approach: new attributes with the old, private attributes implemented
as properties over the new attributes. The properties responsible for this will
raise
Richard Jones added the comment:
Committed in revision 83125.
--
assignee: -> richard
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
type: -> feature request
___
Python tracker
<http://bugs.py
Richard Urwin added the comment:
I can't produce an automated test, for want of time, but here is a demonstrator.
Grab the example XHTML from
http://docs.python.org/library/xml.etree.elementtree.html#elementtree-objects
or use some tiny ASCII-encoded xml file. Save it as "file.x
Richard Urwin added the comment:
> Execute bug-test.xml
I meant bug-test.py, of course
--
___
Python tracker
<http://bugs.python.org/issue1767933>
___
___
Py
Richard Urwin added the comment:
As an example, here is the first two lines of output when I use Python 2.6.3:
60 63 120 109 108 32 118 101 114 115 105 111 110 61 39 49 46 48 39 32 101 110
99 111 100 105 110 103 61 39 85 84 70 45 49 54 39 63 62 10
60 255 254 104 0 116 0 109 0 108 0 62 255 254
Richard Jones added the comment:
That's odd. I didn't run the refcount tests because I was only adding Python
code. I'll look into compiling a debug build and running the tests locally with
a view to tracking down the problem.
--
___
Richard Jones added the comment:
The patch to test_smtplib.py no longer applies since trunk is now py3k. I'm
looking into it - and seeing whether the mock socket work I implemented for
test_smtpd.py will have any common code. I'm hitting some "fun" areas of
py3k-ness wit
Richard Jones added the comment:
Merged mock socket from test_smtpd.py and committed.
--
resolution: -> accepted
status: open -> closed
___
Python tracker
<http://bugs.python.org/
Richard Jones added the comment:
The smtpd module now has a test suite. Please add your unit tests to
test_smtpd.py
--
nosy: +richard
___
Python tracker
<http://bugs.python.org/issue8
New submission from Martin Richard:
Hi,
I stumbled upon a SEGFAULT while trying Python 3.6.0 on a project using
asyncio. I can't really figure out what's happening, so I reduced the original
code triggering the bug down to a reproducible case (which looks a bit clunky,
sorry). The cas
Martin Richard added the comment:
Thank you all for fixing this so quickly, it's been done amazingly fast!
--
___
Python tracker
<http://bugs.python.org/is
New submission from Richard Prosser:
>From https://hg.python.org/cpython/file/3.5/Lib/configparser.py (for example):
358class Interpolation:
359"""Dummy interpolation that passes the value through with no changes."""
360
361def before_get(self, parser,
Richard Prosser added the comment:
Thanks for the prompt reply. I still don't fully understand yet but there
aren't any errors reported so I presume that it is OK.
There is another related matter however: PyCharm (2016.2.3) indicates that a
get() method signature does not match t
Richard Prosser added the comment:
Ah. Something like self._interpolation.before_get(self, section, option, value,
d) could be better written as self._interpolation.before_get(parser=self, ...)
- but that would require keyword arguments to be used throughout.
I still don't grock the app
New submission from Richard Eames:
I've been porting a project to the latest version of Django, and due to one of
the changes in the Django, caused a recursion error in my code. However, the
error (under certain conditions) then causes the python interpreter to core
dump. I'm not
New submission from Richard Xia:
Here is a very short program to demonstrate what I'm seeing:
>>> import tempfile
>>> import os
>>> with tempfile.NamedTemporaryFile(delete=True) as fp:
... print(fp.name)
... os.system('rm {}'.format(fp.name))
Richard Oudkerk added the comment:
> Perhaps NEWS item needed for this change.
Done.
--
___
Python tracker
<http://bugs.python.org/issue16743>
___
___
Python-
Changes by Richard Oudkerk :
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Richard Oudkerk added the comment:
> Richard, do you still want to push this forward? Otherwise I'd like to
> finalize the patch (in the other sense ;-).
I started to worry a bit about daemon threads. I think they can still run
while atexit functions are being run.* So if a da
Richard Oudkerk added the comment:
On 14/02/2013 3:16pm, Antoine Pitrou wrote:
> Mmmh... thread switching is already blocked at shutdown:
> http://hg.python.org/cpython/file/0f827775f7b7/Python/ceval.c#l434
But in Py_Finalize(), call_py_exitfuncs() is called *before* _Py_Finalizing is
se
Changes by Richard Oudkerk :
--
status: pending -> closed
___
Python tracker
<http://bugs.python.org/issue16246>
___
___
Python-bugs-list mailing list
Unsubscri
Richard Oudkerk added the comment:
> In any case, I think it's just something we'll have to live with. Daemon
> threads are not a terrific idea in general.
I agree.
--
___
Python tracker
<http://bugs.py
Richard Oudkerk added the comment:
I did not realize there was a 'Extension Modules' section. I have been putting
changes to C extensions in the 'Library' section instead. It looks like most
people do the same as me.
--
nosy: +sbt
__
Richard Oudkerk added the comment:
> Was not it be yanked in 1fabff717ef4?
Looks like it was reintroduced by this merge changeset:
http://hg.python.org/cpython/rev/30fc620e240e
--
___
Python tracker
<http://bugs.python.org/issu
New submission from Richard Yao:
The preprocessor definition for uint is only defined when building with
PYMALLOC, which breaks builds without PYMALLOC. There is a Gentoo bug report on
this issue:
https://bugs.gentoo.org/show_bug.cgi?id=458168
I have attached a patch that I wrote that
Richard Oudkerk added the comment:
> Good, except that you have to add a gc.collect() call for the
> non-refcounted implementations.
Better to use test.support.gc_collect().
--
nosy: +sbt
___
Python tracker
<http://bugs.python.org/i
Richard Oudkerk added the comment:
Banning md5 as a matter of policy may be perfectly sensible.
However, I think the way multiprocessing uses hmac authentication is *not*
affected by the collision attacks the advisory talks about. These depend on
the attacker being able to determine for
Changes by Richard Oudkerk :
--
nosy: +sbt
___
Python tracker
<http://bugs.python.org/issue17261>
___
___
Python-bugs-list mailing list
Unsubscribe:
Richard Oudkerk added the comment:
A pool should only be used by the process that created it (unless you use a
managed pool).
If you are creating long lived processes then you could create a new pool on
demand. For example (untested)
pool_pid = (None, None)
def get_pool
Richard Oudkerk added the comment:
> Richard, are you suggesting that we close this, or do you see an
> actionable issue? (a plausible patch to the repository?)
I skimmed the documentation and could not see that this restriction has been
documented.
So I think a documentation patch wo
Changes by Richard Oudkerk :
--
resolution: -> fixed
stage: commit review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Richard Oudkerk added the comment:
The new test seems to be reliably failing on Windows:
==
FAIL: test_issue17223 (__main__.UnicodeTest)
--
Traceback (most
Richard Oudkerk added the comment:
I think this change will potentially make the main module get imported twice
under different names when we transfer pickled data between processes. The
current code (which is rather a mess) goes out of its way to avoid that.
Basically the main process makes
Richard Oudkerk added the comment:
It looks like queues_contention.diff has the line
obj = pickle.dumps(obj)
in both _feed() and put(). Might that be why the third set of benchmarks was
slower than the second?
--
___
Python tracker
<h
Richard Oudkerk added the comment:
On 04/03/2013 8:01pm, Charles-François Natali wrote:
>> It looks like queues_contention.diff has the line
>>
>> obj = pickle.dumps(obj)
>>
>> in both _feed() and put(). Might that be why the third set of benchmarks
>> w
Changes by Richard Oudkerk :
--
nosy: +sbt
___
Python tracker
<http://bugs.python.org/issue17364>
___
___
Python-bugs-list mailing list
Unsubscribe:
Richard Oudkerk added the comment:
The change in your patch is in a Windows-only section -- a few lines before the
chunk you can see _winapi.GetExitCodeProcess().
Since read() on Windows never fails with EINTR there is no need for
_eintr_retry_call().
If you are using Linux then there must
Richard Oudkerk added the comment:
BTW, on threads are only used on Windows. On Unix select() or poll() is used.
--
___
Python tracker
<http://bugs.python.org/issue17
Richard Oudkerk added the comment:
I will close the issue then.
If you track the problem down to a bug in Python then you can open a new one.
--
resolution: -> invalid
stage: -> committed/rejected
status: open -> closed
___
Python track
Richard Oudkerk added the comment:
+1
To use Tools/builbot/*.bat doesn't the current directory have to be the main
directory of the repository? Then I see no point in the "-C" argument: just
set the correct directory automatically.
I think make.bat should also support creati
Richard Oudkerk added the comment:
> What does running 'kill-python before re-building python do? I have not
> seen it mentioned in the in the devguide or pcbuild/readme.
It kills any currently running python(_d).exe processes. This is because
Windows does not allow program or li
Richard Oudkerk added the comment:
LGTM (although the warning is actually harmless).
--
___
Python tracker
<http://bugs.python.org/issue17395>
___
___
Python-bug
Richard Oudkerk added the comment:
> Which does give me a thought - perhaps lru_cache in 3.4 could accept a
> "key" argument that is called as "key(*args, **kwds)" to derive the cache
> key? (that would be a separate issue, of course)
Agreed. I suggeste
Richard Oudkerk added the comment:
> Why > 1? This should be commented.
The manager process will always be included in active_children().
--
___
Python tracker
<http://bugs.python.org/i
Richard Oudkerk added the comment:
Does this happen every time you run the tests? (I don't see these errors.)
--
___
Python tracker
<http://bugs.python.org/is
Richard Oudkerk added the comment:
Could you try the following program:
import socket
import multiprocessing
import multiprocessing.reduction
import multiprocessing.connection
def socketpair():
with socket.socket() as l:
l.bind(('localhost', 0))
l.listen(1)
Richard Oudkerk added the comment:
Now could you try the attached file? (It will not work on 2.7 because a
missing socket.fromfd().)
P.S. It looks like the error for 3.3 is associated with a file
f:\python\mypy\traceback.py which presumably clashes with the one in the
standard library
Richard Oudkerk added the comment:
> Both 3.2 and 3.3 give essentially the same traceback as 3.2 did before,
> both with installed python and yesterdays debug builds.
It looks like on your machine socket handles are not correctly inherited by
child processes -- I had assumed that they
Richard Oudkerk added the comment:
> My original report was for 32 bit debug build on 64 bit Win 7 machine.
> I just re-ran test_multiprocessing with installed 64 bit python with same
> result. Was "I don't see these errors." on different Windows or non-Windows.
On 64
Richard Oudkerk added the comment:
Sorry, I was not very clear.
If you use the O_TEMPORARY flag with open() to get a file handle, then the
share mode used with the underlying CreateFile() function is
X = FILE_SHARE_READ | FILE_SHARE_WRITE | FILE_SHARE_DELETE
whereas, if you don'
Richard Oudkerk added the comment:
Actually, it is not quite the same semantics as Unix.
After you delete the the file you cannot create a file of the same name or
delete the directory which contains it until the handle has been closed.
However, one can work around that by moving the file
Richard Oudkerk added the comment:
On 14/03/2013 1:00pm, Martin v. Löwis wrote:
> That's why I was asking for an actual patch. The proposed change may
> well not be implementable. If os.open continues to create CRT handles,
> a way needs to be found to get a CRT hand
Changes by Richard Oudkerk :
--
nosy: +sbt
___
Python tracker
<http://bugs.python.org/issue17444>
___
___
Python-bugs-list mailing list
Unsubscribe:
Richard Oudkerk added the comment:
On 22/03/2013 3:19pm, Charles-François Natali wrote:
> The _flag is checked without any lock held: although it won't be a
> problem with CPython, a standard memory model (e.g. Java's one)
> doesn't guarantee that reading _flag outside
Richard Oudkerk added the comment:
On 22/03/2013 3:31pm, Charles-François Natali wrote:
>> I was under the impression that dict access (and therefore attribute
>> access for "simple" objects) was guaranteed to be atomic even in
>> alternative implementations like Jyt
Changes by Richard Eames :
--
nosy: +Naddiseo
___
Python tracker
<http://bugs.python.org/issue12920>
___
___
Python-bugs-list mailing list
Unsubscribe:
Richard Oudkerk added the comment:
The old code deleted the obj in the feeder thread as soon as it was sent at
lines 247 and 253 -- see Issue #16284. I think that should be retained.
Apart from that LGTM.
--
___
Python tracker
<h
Richard Oudkerk added the comment:
On 24/03/2013 12:16pm, Charles-François Natali wrote:
> The object is overwritten by the pickled data, so it's not necessary
> anymore, no?
Yes, you are right.
--
___
Python tracker
<http://b
Richard Oudkerk added the comment:
It seems to be a problem with ForkAwareThreadLock. Could you try the attached
patch?
--
Added file: http://bugs.python.org/file29593/forkawarethreadlock.patch
___
Python tracker
<http://bugs.python.org/issue17
Richard Oudkerk added the comment:
_afterfork_registry is not supposed to be cleared. But the problem with
ForkAwareThreadLocal meant that the size of the registry at generation n is
2**n!
--
___
Python tracker
<http://bugs.python.org/issue17
Richard Oudkerk added the comment:
> I *think* we need to keep compatibility with the wire format, but perhaps
> we could use a special length value (-1?) to introduce a longer (64-bit)
> length value.
Yes we could, although that would not help on Windows pipe connections (wh
Richard Oudkerk added the comment:
On 27/03/2013 5:13pm, mrjbq7 wrote:
> On a machine with 256GB of RAM, it makes more sense to send arrays
> of this size than say on a laptop...
I was thinking more of speed than memory consumption.
--
___
Richard Oudkerk added the comment:
On 27/03/2013 5:47pm, Charles-François Natali wrote:
>> multiprocessing currently only allows sharing of such shared arrays
>> using inheritance.
>
> You mean through fork() COW?
Through fork, yes, but "shared" rather than "
Richard Oudkerk added the comment:
On 27/03/2013 7:27pm, Charles-François Natali wrote:
>
> Charles-François Natali added the comment:
>
>> Through fork, yes, but "shared" rather than "copy-on-write".
>
> There's a subtlety: because of refcounting,
Richard Oudkerk added the comment:
On 27/03/2013 8:14pm, Charles-François Natali wrote:
>
> Charles-François Natali added the comment:
>
>> Apart from creating, unlinking and resizing the file I don't think there
>> should be any disk I/O.
>>
>> On Linu
Richard Oudkerk added the comment:
On 27/03/13 21:09, Charles-François Natali wrote:
> I could, but I don't have to: a shared memory won't incur any I/O or
> copy (except if it is swapped). A file-backed mmap will incur a *lot*
> of I/O: really, just try writting a 1GB f
Richard Oudkerk added the comment:
I don't think this is a bug -- processes started with fork() should nearly
always be exited with _exit(). And anyway, using sys.exit() does *not*
guarantee that all deallocators will be called. To be sure of cleanup at exit
you could use (the undocum
Richard Oudkerk added the comment:
Maybe this is related to
http://bugs.python.org/issue13673
which causes PyTraceback_Print() to fail if a signal is received but
PyErr_CheckSignals() has not been called.
Note that wrapping in "try: ... except: raise" makes a traceback appear
Richard Oudkerk added the comment:
Adding PyErr_CheckSignals() after PyOS_Readline() in builtin_input() seems to
fix the problem.
--
Added file: http://bugs.python.org/file29665/input-ctrlc.patch
___
Python tracker
<http://bugs.python.
Changes by Richard Oudkerk :
Removed file: http://bugs.python.org/file29665/input-ctrlc.patch
___
Python tracker
<http://bugs.python.org/issue13673>
___
___
Python-bug
Richard Oudkerk added the comment:
Sorry, last message was for another issue.
--
___
Python tracker
<http://bugs.python.org/issue13673>
___
___
Python-bugs-list m
Richard Oudkerk added the comment:
Adding PyErr_CheckSignals() after PyOS_Readline() in builtin_input() seems to
fix the problem.
--
keywords: +patch
Added file: http://bugs.python.org/file29666/input-ctrlc.patch
___
Python tracker
<h
Richard Oudkerk added the comment:
> Richard - are you in a position to commit / push?
Done.
--
___
Python tracker
<http://bugs.python.org/issue17619>
___
_
Changes by Richard Oudkerk :
--
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Richard Oudkerk added the comment:
This problem also affects processes started by multiprocessing (although it is
fixed in http://hg.python.org/sandbox/sbt#spawn).
As far as I am concerned O_NOINHERIT should really have been applied by default
in Python 3. You only get inheritable fds on
Richard Oudkerk added the comment:
You seem to end your subroutines (or whatever they are called) using "goto end"
rather than "exit /b". Since popd follows the "end" label, does this mean that
you get a popd after calling each subroutine? Is this intended and
Richard Oudkerk added the comment:
I don't see how this is a subprocess problem, or could be fixed in subprocess.
IIUC, SetConsoleTextAttribute() only has an effect if the output is connected
to a console. But that is not the case if you redirect the output to a pipe
(which is presu
Richard Oudkerk added the comment:
On 07/04/2013 7:21pm, R. David Murray wrote:
> Certainly on unix if you write ANSI color codes to stdout and the reader
> doesn't strip them, they will be preserved and can be redisplayed, so
> being able to do something similar on Windows
Richard Oudkerk added the comment:
On 07/04/2013 9:02pm, Caitlin Potter wrote:
> I'm not entirely positive that it would be doable, but looking at the
> subprocess code, it looks like we do have an open handle to the windows
> stdout buffer, including buffer attributes, so it shou
Richard Oudkerk added the comment:
@gjwebber: How exactly are you running the program to get that traceback?
The following lines make it look like you are doing something non-standard (as
opposed to just saving the file and running it from the command line):
File "", li
Richard Oudkerk added the comment:
On 10/04/2013 6:32am, Charles-François Natali wrote:
> Richard, IIRC, you said somewhere that FD passing failures on OS X
> could be made to work by passing a FD at a time, or something like
> that. What do you think of those faiilures?
I think se
Richard Oudkerk added the comment:
> I could mark the new test as cpython only, or add a gc.collect (but I'm
> not sure if the latter is enough, either).
test.support.gc_collect() should work on non-refcounted implementations.
--
Richard Oudkerk added the comment:
Note that in Python 3 you can also do __class__.f() in a staticmethod. Not
sure if that is encouraged though.
--
nosy: +sbt
___
Python tracker
<http://bugs.python.org/issue10
801 - 900 of 1064 matches
Mail list logo
