Changes by Alexander Belopolsky :
--
stage: -> patch review
___
Python tracker
<http://bugs.python.org/issue10947>
___
___
Python-bugs-list mailing list
Un
Changes by Alexander Belopolsky :
--
nosy: +belopolsky
___
Python tracker
<http://bugs.python.org/issue10952>
___
___
Python-bugs-list mailing list
Unsubscribe:
Alexander Belopolsky added the comment:
This proposal makes sense because it would make
import µTorrent
behave the same as
µTorrent = __import__('µTorrent')
However, I think this is a feature request and a language change because the
current grammar is
import_stmt ::= "
Alexander Belopolsky added the comment:
On Wed, Jan 19, 2011 at 9:21 PM, STINNER Victor wrote:
..
> New problem: if the parser doesn't normalize module names on import, it does
> still
> normalize module names on other instructions.
>
> Example: "import \xB5Torrent; d
Alexander Belopolsky added the comment:
Victor> Ok, I think that it is possible.
While it is possible, I am not sure it is a good idea. For example, if a
filesystem uses encoding that is capable of distinguishing between
"\xB5Torrent.py" and "\u03BCTorrent.py", sho
Changes by Alexander Belopolsky :
--
nosy: +belopolsky
___
Python tracker
<http://bugs.python.org/issue3080>
___
___
Python-bugs-list mailing list
Unsubscribe:
Alexander Belopolsky added the comment:
> rather than serialize python dicts & list to json ...
> its more efficient to just serialize w/ repr() & then use eval()
Do you have benchmarks that support this claim?
--
nosy: +belopolsky
versions
Alexander Belopolsky added the comment:
On Thu, Jan 20, 2011 at 1:19 AM, Martin v. Löwis wrote:
..
> I'd like to request that PEP 3131 is followed as it stands: identifier lookup
> uses NFKC,
> period. This gives two issues: a) how can users make sure that they name the
>
Alexander Belopolsky added the comment:
On Thu, Jan 20, 2011 at 8:06 AM, STINNER Victor wrote:
..
>> There is also issue c) what if the filesystem encoding can only
>> represent a compatibility character, say U+00B5, but not its NFKC
>> equivalent, U+03BC?
>
> It is t
Alexander Belopolsky added the comment:
Misc/cheatsheet has been removed in r88127. Should this be closed?
--
___
Python tracker
<http://bugs.python.org/issue4
Alexander Belopolsky added the comment:
FWIW, I updated the first couple of pages. If anyone finds my changes useful,
here they are in issue4819.diff.
--
keywords: +patch
Added file: http://bugs.python.org/file20476/issue4819.diff
___
Python
Alexander Belopolsky added the comment:
Works for me:
>>> from timeit import Timer
>>> class A(Timer): pass
...
(Tested with Python 3.1 and 3.2 on OSX.)
--
nosy: +belopolsky
___
Python tracker
<http://bugs.
Alexander Belopolsky added the comment:
On Thu, Jan 20, 2011 at 10:08 PM, R. David Murray
wrote:
..
> (*) The asymetry in the names of these two functions is already a wart.
Not to mention the use of CamelCase.
--
___
Python tracker
&l
Alexander Belopolsky added the comment:
Changing the title to reflect broader scope of this issue. Json tests were
moved to Lib/test/json_tests in r86875.
--
title: Move unittest test package to Lib/test -> Move test sub-packages to
Lib/t
Alexander Belopolsky added the comment:
Two nitpicks:
1. To avoid repetition, I would now define Mon2num as
Mon2num = dict(zip(_month_names, range(1, 13)))
2. Please keep lines under 79 characters long.
This does not seem important enough to push to RC2, but if you think otherwise
please
Alexander Belopolsky added the comment:
Also, isn't day supposed to be space- rather than 0- padded?
--
___
Python tracker
<http://bugs.python.org/is
Alexander Belopolsky added the comment:
On Fri, Jan 28, 2011 at 2:44 PM, Alexander Belopolsky
wrote:
..
> Also, isn't day supposed to be space- rather than 0- padded?
To the best of my understanding, rfc 2060 requires space-padded day
(strftime code %e):
"""
date_day_
Alexander Belopolsky added the comment:
I would write the formatting code as follows:
('"%2d-%s-%04d %02d:%02d:%02d %+03d%02d"' %
((tt[2], _month_names[tt[1]], tt[0]) +
tt[3:6] + divmod(zone//60, 60)))
The above also assumes that month names are stored in a 1-based
Changes by Alexander Belopolsky :
--
assignee: belopolsky -> georg.brandl
___
Python tracker
<http://bugs.python.org/issue10939>
___
___
Python-bugs-list mai
Alexander Belopolsky added the comment:
Attached patch fixes the test (hopefully we don't have to support systems with
non-POSIX epoch) and cleans up whitespace.
--
resolution: -> accepted
stage: patch review -> commit review
Added file: http://bugs.python.org/file20604
Changes by Alexander Belopolsky :
Removed file: http://bugs.python.org/file20604/issue10939.diff
___
Python tracker
<http://bugs.python.org/issue10939>
___
___
Python-bug
Changes by Alexander Belopolsky :
Added file: http://bugs.python.org/file20605/issue10939.diff
___
Python tracker
<http://bugs.python.org/issue10939>
___
___
Python-bug
Alexander Belopolsky added the comment:
Committed in revision 88231.
--
___
Python tracker
<http://bugs.python.org/issue10939>
___
___
Python-bugs-list mailin
Alexander Belopolsky added the comment:
Merged to 3.1 in r88233.
--
nosy: +benjamin.peterson
resolution: accepted -> fixed
stage: commit review -> committed/rejected
versions: +Python 3.1
___
Python tracker
<http://bugs.python.org/i
Alexander Belopolsky added the comment:
It looks like my test is not robust enough:
http://www.python.org/dev/buildbot/all/builders/x86%20OpenIndiana%203.1/builds/298
--
___
Python tracker
<http://bugs.python.org/issue10
Alexander Belopolsky added the comment:
Some systems don't like times too close to epoch. Fixed in revision 88239.
--
___
Python tracker
<http://bugs.python.org/is
Changes by Alexander Belopolsky :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue10939>
___
___
Python-bugs-list mailing list
Un
Alexander Belopolsky added the comment:
On Sat, Jan 29, 2011 at 5:48 PM, Joe Peterson wrote:
..
> Note that this also exposes another problem with Time2Internaldate(), since
> it uses
> time.timezone/time.altzone, which are only valid for the current rules, not
> old rules as i
Changes by Alexander Belopolsky :
--
dependencies: +Time zone-capable variant of time.localtime
___
Python tracker
<http://bugs.python.org/issue9527>
___
___
Pytho
Changes by Alexander Belopolsky :
--
dependencies: +No obvious and correct way to get the time zone offset
___
Python tracker
<http://bugs.python.org/issue9
Changes by Alexander Belopolsky :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue1667546>
___
___
Python-bugs-list mailing list
Un
Changes by Alexander Belopolsky :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue1647654>
___
___
Python-bugs-list mailing list
Un
Alexander Belopolsky added the comment:
On Sat, Jan 29, 2011 at 4:45 PM, Joe Peterson wrote:
..
> I have added code that sets the TZ to one that works, and then reverts the
> temporary
> TZ change after the test.
>
Your test will not restore TZ if it fails. This is not nice.
Alexander Belopolsky added the comment:
On Sat, Jan 29, 2011 at 11:56 PM, Raymond Hettinger
wrote:
..
> Also, I question whether the proposed API is correct. ISTM that any code
> that sets the *dst*
> parameter is guaranteed to be wrong (hardwiring-in a value that will change
&g
Alexander Belopolsky added the comment:
It would be nice to add a unit test to this patch. I don't think messing with
read-only filesystems is feasible in regrtest, but it seems from reading
_ctypes_alloc_callback() source that similar behavior can be triggered by
passing a fa
Alexander Belopolsky added the comment:
Please consider mentioning that several modules can now be called with -m:
pickle, pickletools and tkinter.
--
nosy: +belopolsky
___
Python tracker
<http://bugs.python.org/issue11
Alexander Belopolsky added the comment:
The proposed patch looks fine to me, but it is attached to the wrong issue. It
belongs to #8973 or better yet to follow RC2 rules pedantically, it should be
posted in a separate issue.
This is important, because this issue is limited to docstrings and
Alexander Belopolsky added the comment:
Wait, #8973 *is* this issue. But r81947 is clearly not about docstrings. We
definitely need a saparate issue. This is too confusing.
--
___
Python tracker
<http://bugs.python.org/issue8
Changes by Alexander Belopolsky :
--
Removed message: http://bugs.python.org/msg127607
___
Python tracker
<http://bugs.python.org/issue8973>
___
___
Python-bug
Alexander Belopolsky added the comment:
Wait, #8973 *is* this issue. But r81947 is clearly not only about docstrings.
We definitely need a separate issue. This is too confusing.
--
___
Python tracker
<http://bugs.python.org/issue8
Changes by Alexander Belopolsky :
--
nosy: +PythonInTheGrass -BreamoreBoy
resolution: wont fix ->
status: closed -> open
___
Python tracker
<http://bugs.python.org/iss
Alexander Belopolsky added the comment:
One possible solution was presented in issue1252236: move tkinter event loop
into Python main loop. However, to consider this report a bug, we need an
example code that shows the behavior that you consider incorrect. Even then,
it is likely that
Alexander Belopolsky added the comment:
+1. This is a fairly common mistake. Usually benign, but as issue 8973 shows,
may highlight a visible error.
--
nosy: +belopolsky
___
Python tracker
<http://bugs.python.org/issue11
Alexander Belopolsky added the comment:
On Mon, Jan 31, 2011 at 12:09 PM, R. David Murray
wrote:
..
> On linux, the dups are putenv and unsetenv. And yes, deeper investigation of
> why
> os.py is adding them is required to fix this :)
Too bad __all__ cannot be specified
Alexander Belopolsky added the comment:
I would say if anything can go in after rc2 at all, this should be accepted.
George?
I ran a few sanity checks with the patch applied:
>>> set(struct.__all__) - set(dir(struct))
set()
>>> set(dir(struct)) - set(struct.__all__)
{'
Changes by Alexander Belopolsky :
--
dependencies: +from struct import * misses pack_into
___
Python tracker
<http://bugs.python.org/issue11078>
___
___
Python-bug
Changes by Alexander Belopolsky :
--
stage: -> commit review
___
Python tracker
<http://bugs.python.org/issue11081>
___
___
Python-bugs-list mailing list
Un
Changes by Alexander Belopolsky :
Removed file: http://bugs.python.org/file16584/unnamed
___
Python tracker
<http://bugs.python.org/issue8176>
___
___
Python-bugs-list m
Changes by Alexander Belopolsky :
Removed file: http://bugs.python.org/file16615/unnamed
___
Python tracker
<http://bugs.python.org/issue8176>
___
___
Python-bugs-list m
Alexander Belopolsky added the comment:
It looks like the bug cannot be reproduced anymore. Since it was discovered
using a python instance with third-party extension modules, it may not even be
a python bug to begin with.
--
assignee: -> belopolsky
nosy: +belopol
Alexander Belopolsky added the comment:
Ryan,
Do you still have the setup that can reproduce this error? If so, can you try
running it with pickle rather than cPickle? If it works with pickle, please
see if you can reproduce the error by unpickling the result of pickle and
repickling it
Changes by Alexander Belopolsky :
Removed file: http://bugs.python.org/file17899/unnamed
___
Python tracker
<http://bugs.python.org/issue9197>
___
___
Python-bugs-list m
Alexander Belopolsky added the comment:
Amaury,
Can you post your Linux code reproducing the issue? I would like to take a
look, but don't want to dig through an XCode project.
--
assignee: -> belopolsky
nosy: +belopolsky
title: Crash when importer an extension after Py_In
Alexander Belopolsky added the comment:
Victor,
I was thinking about pointing the OP to your faulthandler module, but decided
not to because in the failing thread python has already finished execution and
most of finalization. It is very unlikely that faulthandler will be helpful in
this
Alexander Belopolsky added the comment:
Hmm, either my hand is too slow or my laptop is too fast, but I cannot
reproduce the crash. Can you create a non-interactive script? Maybe start a
separate thread generating "launch" events?
What do you mean by "crash"? Do you ge
Alexander Belopolsky added the comment:
I converted TkinterCrash2.py to 3.x using 2to3 (result attached as
TkinterCrash3.py) and it works with 3.2rc2 just fine.
--
Added file: http://bugs.python.org/file20632/TkinterCrash3.py
___
Python tracker
Alexander Belopolsky added the comment:
Committed in revision 88280.
--
resolution: -> fixed
stage: commit review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Alexander Belopolsky added the comment:
It is unfortunate that the cute name for the tool is not valid as a module
name. How about renaming "lib2to3" to "to3". The offending leading digit is
strictly redundant (there is no 1to3 after all).
Alexander Belopolsky added the comment:
The consensus is that this is not a crash (and not even a bug). I am not sure
what is the proper type for doc enhancement, but is certainly should not show
up in a search for crashers.
--
components: -Interpreter Core
nosy: +belopolsky
type
Changes by Alexander Belopolsky :
--
stage: unit test needed -> needs patch
title: WinPython 2.3.3 crashes using popen2 to spawn lots of child -> popen2 on
Windows does not check _fdopen return value
___
Python tracker
<http://bugs.p
Alexander Belopolsky added the comment:
I can reproduce the crash on OSX. After ~ 100 keystrokes, I get the following
diagnostics:
Exception in Tkinter callback
Traceback (most recent call last):
File "/Users/sasha/Work/python-svn/py3k-commit/Lib/tkinter/__init__.py", line
Alexander Belopolsky added the comment:
This looks like a duplicate of issue11029. It is not safe to call graphic
primitives in event callbacks. A workaround is described at
<http://effbot.org/zone/tkinter-threads.htm>.
--
resolution: -> duplicate
stage: -> commit
Changes by Alexander Belopolsky :
--
components: +Unicode
nosy: +haypo
___
Python tracker
<http://bugs.python.org/issue7330>
___
___
Python-bugs-list mailin
Alexander Belopolsky added the comment:
Documentation part of this issue will be addressed in #10435.
--
nosy: +belopolsky
resolution: -> duplicate
stage: needs patch -> committed/rejected
superseder: -> PyUnicode_FromFormat segfault
_
Alexander Belopolsky added the comment:
This works in 3.x:
Python 3.2rc2+ (py3k:88279:88280, Feb 1 2011, 00:01:52)
..
>>> from xml.etree import ElementTree
>>> ElementTree.fromstring('诗')
In 2.x you need to encode unicode strings before passing them to
El
Alexander Belopolsky added the comment:
On Wed, Feb 2, 2011 at 11:10 AM, STINNER Victor wrote:
..
> We can explain in ElementTree documentation how to pass non-ASCII unicode
> strings: using
> explicit encoding to UTF-8.
ElementTree.fromstring() ultimately calls ElementTree.XMLPa
Alexander Belopolsky added the comment:
I don't see an actual crash reported. An unexpected exception is not a crash.
Changing the type to "behavior".
--
nosy: +belopolsky
type: crash -> behavior
___
Python tracker
<h
Changes by Alexander Belopolsky :
--
components: +Extension Modules, Windows -Library (Lib)
___
Python tracker
<http://bugs.python.org/issue10762>
___
___
Pytho
Alexander Belopolsky added the comment:
Unexpected exception is not a crash. Changing the type to "behavior."
--
nosy: +belopolsky
type: crash -> behavior
___
Python tracker
<http://bugs.pytho
Alexander Belopolsky added the comment:
Not applicable to 3.x because the frame object does not have f_exc_traceback
attribute anymore:
>>> import sys;sys._getframe(0).f_exc_traceback = 23
Traceback (most recent call last):
File "", line 1, in
AttributeError: &#
Alexander Belopolsky added the comment:
The issue is not Windows specific, so I am changing the title to reflect that.
On OSX, for example, I get
$ PYTHONIOENCODING=xyz ./python.exe
Fatal Python error: Py_Initialize: can't initialize sys standard streams
LookupError: unknown encoding
Alexander Belopolsky added the comment:
> If we want to allow for closed {stdin, stdout, stderr}, I'm not sure
> what the semantics should be. Should sys.std{in, out, err} be None? Or a
> file object which always throws an error?
I would say it should be a *pseudo*-file objec
Alexander Belopolsky added the comment:
On the second thought, as long as python used fd 2 as the "message stream of
last resort", we should probably not allow it to run with fd 2 closed. The
problem is that in this case fd 2 may become associated with a very important
file content
Changes by Alexander Belopolsky :
--
type: crash -> behavior
___
Python tracker
<http://bugs.python.org/issue9592>
___
___
Python-bugs-list mailing list
Un
Alexander Belopolsky added the comment:
Looks like a stack overflow caused by an infinite recursion. I am not sure if
it is possible to add cycle detection code without sacrificing performance or
setting some arbitrary limits.
I wonder: Why ast nodes need to be mutable?
--
nosy
Alexander Belopolsky added the comment:
On Thu, Feb 3, 2011 at 12:08 PM, Benjamin Peterson
wrote:
..
>> I wonder: Why ast nodes need to be mutable?
>
> So people can change them.
Well, they are hashable, so this needs to be done carefully. Is this
necessary for AST-based optimiza
Alexander Belopolsky added the comment:
Similar idea has been rejected in issue2268 because the win was too small to
justify the number of changes that had to be made.
--
nosy: +belopolsky
___
Python tracker
<http://bugs.python.org/issue11
Alexander Belopolsky added the comment:
On Thu, Feb 3, 2011 at 2:44 PM, Antoine Pitrou wrote:
..
>> Do you know of places where we use fd 2 instead of sys.stderr?
>
> We normally don't. One reason is that buffering inside sys.stderr can
> make ordering of output incor
Alexander Belopolsky added the comment:
> On Thu, Feb 3, 2011 at 2:44 PM, Antoine Pitrou wrote:
> ..
>> Do you know of places where we use fd 2 instead of sys.stderr?
>
> We normally don't.
Hmm, grep "fprintf(stderr," returned 122 hits in the py3k branch.
Changes by Alexander Belopolsky :
--
components: +Build
type: crash -> behavior
___
Python tracker
<http://bugs.python.org/issue9045>
___
___
Python-bugs-lis
Alexander Belopolsky added the comment:
On Thu, Feb 3, 2011 at 7:09 PM, Éric Araujo wrote:
>
> Éric Araujo added the comment:
>
> Is there a standard documenting MANPAGER somewhere?
>
Not really a standard, but man page for man on my OSX laptop says:
"
Alexander Belopolsky added the comment:
I don't have a working valgrind or purify, but I was able to reproduce the
problem using a poor man's solution of adding
assert(0xcbcbcbcbcbcbcbcb != tok->line_start);
before
if (a >= tok->line_start)
With th
Alexander Belopolsky added the comment:
George,
This is not really important enough to get into the 3.2 release, but
uninitialized variable bugs tend to be nasty when they bite you, so I'll ask
your opinion before bumping the version.
--
assignee: -> georg.bra
Alexander Belopolsky added the comment:
On Thu, Feb 3, 2011 at 7:39 PM, Éric Araujo wrote:
..
> Justin: what exactly is a pager that does not support man pages?
I may know the answer to this one. A common PAGER setting is "less
-rs" which makes less skip whitespace lines and p
Alexander Belopolsky added the comment:
Spam.
--
nosy: +belopolsky -renben
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue1>
___
_
Alexander Belopolsky added the comment:
It may be clearer and match Python coding style better to fix it as follows:
Index: Modules/_sqlite/module.c
===
--- Modules/_sqlite/module.c(revision 88320)
+++ Modules/_sqlite
Changes by Alexander Belopolsky :
--
type: crash -> behavior
___
Python tracker
<http://bugs.python.org/issue10419>
___
___
Python-bugs-list mailing list
Un
Changes by Alexander Belopolsky :
--
type: crash -> behavior
___
Python tracker
<http://bugs.python.org/issue2437>
___
___
Python-bugs-list mailing list
Un
Changes by Alexander Belopolsky :
--
type: crash -> behavior
___
Python tracker
<http://bugs.python.org/issue7100>
___
___
Python-bugs-list mailing list
Un
Alexander Belopolsky added the comment:
Here is a somewhat more straightforward way to reproduce the problem:
>>> class X:
...__class__ = int
...
[55910 refs]
>>> isinstance(X(), int)
True
[55914 refs]
>>> int.bit_length(X())
Assertion failed: (PyLong_Check(v)
Changes by Alexander Belopolsky :
--
type: crash -> behavior
versions: -Python 3.2
___
Python tracker
<http://bugs.python.org/issue10042>
___
___
Python-
Alexander Belopolsky added the comment:
On Fri, Feb 4, 2011 at 11:35 AM, Georg Brandl wrote:
>.. But seeing the history of this case, I don't want to play around here
>before 3.2 final.
Here is my understanding of the history of this case: tmp1.patch was
applied in r65539 and
Changes by Alexander Belopolsky :
--
assignee: georg.brandl -> belopolsky
___
Python tracker
<http://bugs.python.org/issue3367>
___
___
Python-bugs-list mai
Changes by Alexander Belopolsky :
--
nosy: +haypo
___
Python tracker
<http://bugs.python.org/issue11188>
___
___
Python-bugs-list mailing list
Unsubscribe:
Alexander Belopolsky added the comment:
I have come across the following post:
http://code.google.com/p/y2038/wiki/AmazingDiscoveries
I think some of the findings there may be relevant as we push the
boundaries of supported time values
Alexander Belopolsky added the comment:
Sébastien,
Can you tell us what time.localtime(t) produces for t in (-2, -1, 0, 1)?
Apparently time.mktime() fails on values produced by time.localtime() and this
sounds like a platform bug. It is OK to restrict time_t to positive values,
but in
Alexander Belopolsky added the comment:
It looks like different standards have different requirements for
localtime() error handling compare:
http://pubs.opengroup.org/onlinepubs/009695399/functions/localtime.html
and
http://pubs.opengroup.org/onlinepubs/7990989775/xsh/localtime.html
The
Alexander Belopolsky added the comment:
2011/2/15 Sébastien Sablé :
..
>>>> for t in (-2, -1, 0, 1):
> ... print(time.localtime(t))
> ...
> time.struct_time(tm_year=1970, tm_mon=1, tm_mday=1, tm_hour=0, tm_min=59,
> tm_sec=58, tm_wday=3, tm_yday=1, tm_isdst=0)
..
Alexander Belopolsky added the comment:
Backported in r88425 (3.1) and r88427 (2.7).
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue1
Alexander Belopolsky added the comment:
Victor,
I don't see your patch. Did you remove it?
--
type: -> behavior
___
Python tracker
<http://bugs.python.or
901 - 1000 of 3596 matches
Mail list logo
