Changes by Serhiy Storchaka storch...@gmail.com:
--
nosy: +storchaka
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8912
___
___
Python-bugs-list
New submission from Walid Shaari:
In the code below the time stamp 1341183050 should be 01 July 2012. however
datetime is converting it back to 7 July 2012, the reverse too is wrong, is
that just the way i am using the code?
[g_geadm@plcig2 ~]$ ipython
Python 2.6.5 (r265:79063, Jul 14 2010,
Walid Shaari added the comment:
the issue i believe is in datetime module
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15563
___
___
Pierre Le Marre added the comment:
By the way, this issue does not appear with Python 3.2.2.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15545
___
Martin v. Löwis added the comment:
It's a timezone issue. Try
datetime.datetime.utcfromtimestamp(1341183050)
--
nosy: +loewis
resolution: - invalid
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15563
Changes by Tshepang Lekhonkhobe tshep...@gmail.com:
--
nosy: +tshepang
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15509
___
___
Changes by Tshepang Lekhonkhobe tshep...@gmail.com:
--
nosy: +pitrou
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15523
___
___
Python-bugs-list
Changes by Tshepang Lekhonkhobe tshep...@gmail.com:
--
nosy: +tshepang
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15520
___
___
Changes by Tshepang Lekhonkhobe tshep...@gmail.com:
--
nosy: +tshepang
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15506
___
___
Changes by Tshepang Lekhonkhobe tshep...@gmail.com:
--
nosy: +tshepang
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15504
___
___
Changes by Tshepang Lekhonkhobe tshep...@gmail.com:
--
nosy: +tshepang
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15501
___
___
Stefan Krah added the comment:
STINNER Victor rep...@bugs.python.org wrote:
Hum, this issue is a regression from Python 3.2.
Python 3.2.3+ (3.2:243ad1a6f638+, Aug 4 2012, 01:36:41)
[GCC 4.6.3 20120306 (Red Hat 4.6.3-2)] on linux2
import array
a=array.array('u', 'xyz')
Stefan Krah added the comment:
Also, it was suggested that 'u' should be deprecated:
http://mail.python.org/pipermail/python-dev/2012-March/117392.html
Personally, I don't have an opinion on that; I don't use the 'u'
format code.
Nick, could you have a look at msg167545 and see if any
New submission from patrick vrijlandt:
.mht is an archive format created by Microsoft IE 8 when saving a webpage. It
is essentially a mime multipart message.
My problem occurred when I uploaded such a file to a cgi-based server. The
posted data would be fed to cgi.FieldStorage. (I can't post
Stefan Krah added the comment:
Of course, if two formats *are* the same, it is possible to use
memcmp(). I'll work on a patch.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13072
___
Nick Coghlan added the comment:
Perhaps if memoryview doesn't understand the format code, it can fall back on
memcmp() if strcmp() indicates the format codes are the same?
Otherwise we're at risk of breaking backwards compatibility with more than just
array('u').
Also, if it isn't already,
New submission from Paul:
In Python 2.6, pdb doesn't show exception strings properly:
#somecode.py
import pdb
pdb.set_trace()
raise Exception('This is a message that contains a lot of characters and is
very long indeed.')
#terminal
somecode.py
- raise Exception('This is a message that
STINNER Victor added the comment:
memoryview is not aware of the 'u' format code, since it's not part of
the struct syntax and the PEP-3118 proposition 'u' - UCS2, 'w' - UCS4
wasn't considered useful.
Did you see attached patch array_unicode_format.patch? It uses struct
format H or I
Attila Nagy added the comment:
I don't think this should be done by default as it will break people's
expectations and, perhaps worse, compatibility.
I won't mind another thread naming API, if somebody does this. :)
But personally I expected python to name my threads (and if the OS supports it,
New submission from Sebastian Ramacher:
tarfile.TarInfo.frombuf has gained two more parameters: encoding and errors.
The documentation of frombuf claims that the only parameter is buf, which is
not true anymore.
--
assignee: docs@python
components: Documentation
messages: 167553
nosy:
New submission from Stefan Behnel:
Line 912 of threading.py, Py2.7, reads:
self.queue = deque()
deque hasn't been imported.
--
components: Library (Lib)
messages: 167554
nosy: scoder
priority: normal
severity: normal
status: open
title: threading.py contains undefined name
Changes by Serhiy Storchaka storch...@gmail.com:
--
nosy: +storchaka
versions: +Python 3.3 -Python 3.1
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10182
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Library (Lib)
stage: - needs patch
type: - behavior
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10182
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
keywords: +easy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10182
___
___
Python-bugs-list
Thiébaud Weksteen added the comment:
When I wrote this patch, I was focusing on a particular usage and the buffer
was the only parameter that interested me. But you're right, the other
parameters should be included. Which brings the following questions:
* write_p looks like a boolean, would
Richard Oudkerk added the comment:
In _make_callback, I still think the default error reporting mechanism
should be kept. It can be improved separately.
New patch. This time I have got rid of _make_callback, and just given __call__
an ignored optional argument.
--
Added file:
R. David Murray added the comment:
Ah, I read too quickly before. But that expression when a delimiter string
*sep* is given is hard to wrap ones head around in this context. I think the
problem really is that 'split' has such radically different behavior when given
an argument as opposed
Changes by R. David Murray rdmur...@bitdance.com:
--
Removed message: http://bugs.python.org/msg167557
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15554
___
R. David Murray added the comment:
Ah, I read too quickly before. But that expression when a delimiter string
*sep* is given is hard to wrap ones head around in this context. I think the
problem really is that 'split' has such radically different behavior when given
an argument as opposed
R. David Murray added the comment:
It is indeed the compatibility that is the worse issue. The problem is what
people have gotten used to and may have coded their applications to expect/deal
with. what people have gotten used to. I agree with you that most people would
*not* find it
Changes by R. David Murray rdmur...@bitdance.com:
--
Removed message: http://bugs.python.org/msg167559
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15500
___
R. David Murray added the comment:
It is indeed the compatibility that is the worse issue. The problem is what
people have gotten used to and may have coded their applications to expect/deal
with. I agree with you that most people would *not* find it surprising to see
the name reflected in
Stefan Krah added the comment:
Did you see attached patch array_unicode_format.patch? It uses struct
format H or I depending on the size of wchar_t.
I totally overlooked that. Given that memoryview can be fixed to
compare buffers with unknown formats, I don't have a strong opinion
on whether
Changes by R. David Murray rdmur...@bitdance.com:
--
nosy: +r.david.murray
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15564
___
___
R. David Murray added the comment:
As far as I can see it has been. In both 2.7 and 3.3 I get:
rdmurray@hey:~/python/p33./python somecode.py
/home/rdmurray/python/p33/somecode.py(3)module()
- raise Exception('This is a message that contains a lot of characters and is
very long indeed.')
Roundup Robot added the comment:
New changeset 8282e4846e43 by Ned Deily in branch 'default':
Issue #15037: Build OS X installers with local copy of ncurses 5.9 libraries
http://hg.python.org/cpython/rev/8282e4846e43
--
nosy: +python-dev
___
Python
Ned Deily added the comment:
I've updated the OS X installers to build and link with a local copy of ncurses
5.9 rather than older Apple-supplied ones, thus avoiding the library bug.
test_curses now passes for them.
--
___
Python tracker
Ned Deily added the comment:
P.P.S. I've updated the OS X installers as of 3.3.0b2 to build and link with a
local copy of ncurses 5.9 rather than older Apple-supplied ones. test_curses
now passes.
--
___
Python tracker rep...@bugs.python.org
Nick Coghlan added the comment:
I think Victor's patch is a good solution to killing the 'u' and 'w' exports in
3.4, but we need to restore some tolerance for unknown format codes to
memoryview in 3.3 regardless.
--
___
Python tracker
Éric Araujo added the comment:
Now I have hardware issues, so no.
--
assignee: eric.araujo -
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15163
___
Ronald Oussoren added the comment:
The test passes fine on OSX 10.8 (even when running the threading test in a
loop). This might be because a platform bug is fixed in OSX 10.8, or because
the crash happens due to a race condition of some sort (either in Python itself
or the system).
This
Chris Jerdonek added the comment:
I think the problem really is that 'split' has such radically different
behavior when given an argument as opposed to when it isn't.
Yep, the split() documentation is much more involved because of that.
Please move the keeplines discussion back up into the
R. David Murray added the comment:
Good point. Difference paragraph after the example would be best, I think.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15554
___
Stefan Krah added the comment:
I have a patch already for the unknown format codes in memoryview.
Currently fighting (as usual) with the case explosions in the tests.
I think I can have a full patch by next weekend.
--
___
Python tracker
Chris Jerdonek added the comment:
Here you go. Thanks again.
--
Added file: http://bugs.python.org/file26709/issue-15554-4.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15554
___
Karen KarenL added the comment:
I just run into this problem. I am running python 3.2, but I do have python 26
and python 27 install on the same computer.
--
nosy: +Karen.KarenL
status: pending - open
___
Python tracker rep...@bugs.python.org
Roundup Robot added the comment:
New changeset 768b188262e7 by R David Murray in branch '3.2':
#15554: clarify splitlines/split differences.
http://hg.python.org/cpython/rev/768b188262e7
New changeset 0d6eea2330d0 by R David Murray in branch 'default':
Merge #15554: clarify splitlines/split
R. David Murray added the comment:
Thanks for sticking with it.
--
resolution: - fixed
stage: patch review - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15554
Roger Serwy added the comment:
What are the precise steps you are taking to cause this error?
What version of Windows are you using? Is it 32-bit?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9890
Brett Cannon added the comment:
Georg, is it okay if I commit this on Eric's behalf for 3.3?
--
assignee: - georg.brandl
nosy: +georg.brandl
priority: low - release blocker
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15163
Roundup Robot added the comment:
New changeset 4240282a9f4a by Brett Cannon in branch 'default':
Issue #15471: Don't use mutable object as default values for the
http://hg.python.org/cpython/rev/4240282a9f4a
--
nosy: +python-dev
___
Python tracker
Changes by Brett Cannon br...@python.org:
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15471
___
Peter Otten added the comment:
Here's a minimal fix that modifies the sql in sqlite3.dump._iterdump() to sort
the tables by name. It is then no longer necessary to sort the resultset in
Python for the unit tests to pass.
--
keywords: +patch
nosy: +peter.otten
Added file:
Georg Brandl added the comment:
Great to review such patches, where I have to take out a notepad and write the
names down to check a 1-item addition./grumble
But it seems it does what's on the label, so go ahead.
--
___
Python tracker
Karen KarenL added the comment:
Additional info on error in python 3.2
I am using 32 bit Win 7 enterprise SP1. I download and installed python-3.2.msi
from python.org I than start python pythonw from window menu just like any
other program. Running python command line also failed, and this is
Brett Cannon added the comment:
I will alphabetize as part of the patch (I had the same issue myself of
verifying the change).
--
assignee: georg.brandl - brett.cannon
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15163
Éric Araujo added the comment:
Sorry for the annoyance. I changed the order (and did not choose to
alphabetize) because I thought it was easier to read with names grouped by
topic, as I said in an earlier message, but please do as you think best.
--
Chris Jerdonek added the comment:
Victor, would you be able to take a look at this minor documentation patch? It
incorporates the change that you suggested we make on python-dev.
--
___
Python tracker rep...@bugs.python.org
Roundup Robot added the comment:
New changeset 6a27b9f37b05 by Brett Cannon in branch 'default':
Issue #15163: Pydoc shouldn't show __loader__ as a part of a module's
http://hg.python.org/cpython/rev/6a27b9f37b05
--
nosy: +python-dev
___
Python
Brett Cannon added the comment:
Don't worry about it, Eric. while the idea of grouping by concept is laudable,
when the list is that long it's best to just alphabetize to make diffs easier
to read.
--
resolution: - fixed
stage: commit review - committed/rejected
status: open - closed
Barry A. Warsaw added the comment:
On Aug 05, 2012, at 11:50 PM, Brett Cannon wrote:
I went with Barry's approach but made it compatible with PEP 8 (bad, FLUFL;
no unneeded parens!).
I actually think I picked that up from the big guy himself, but I could be
misremembering. ;)
--
Chris Jerdonek added the comment:
Is this issue awaiting feedback from anyone else before it can proceed further?
(Just this issue and not issue 15439 to make any adjustments to the docs.)
I am attaching an updated diff after generating the script output again against
the tip (modified to
Chris Jerdonek added the comment:
For completeness, I am attaching the modified version of the script that was
used to generate the latest output.
--
Added file: http://bugs.python.org/file26712/merge-acks-2.py
___
Python tracker
Ludwig Hähne added the comment:
Serhiy, the tests now explicitly check the base size of the array.
I'm not sure if I got the base size compution right (only checked on 32bit
Linux). Could you check that the struct definition in the test makes sense and
matches the C arrayobject definition?
New submission from Dino Viehland:
When implementing an iterable object by hand, and raising StopIteration with a
value, the value is not provided as the result of the yield from expression.
This differs from the behavior in the Formal Semantics section. Here's an
example of how it differs
Changes by Alex Gaynor alex.gay...@gmail.com:
--
nosy: +alex
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15568
___
___
Python-bugs-list mailing
Changes by Meador Inge mead...@gmail.com:
--
nosy: +meador.inge
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15568
___
___
Python-bugs-list
Chris Jerdonek added the comment:
Updating patch to current tip.
--
Added file: http://bugs.python.org/file26714/issue-15543-2.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15543
___
Roundup Robot added the comment:
New changeset ee55f8e4fb50 by Benjamin Peterson in branch 'default':
fix yield from return value on custom iterators (closes #15568)
http://hg.python.org/cpython/rev/ee55f8e4fb50
--
nosy: +python-dev
resolution: - fixed
stage: - committed/rejected
Changes by INADA Naoki songofaca...@gmail.com:
--
nosy: +naoki
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15216
___
___
Python-bugs-list
New submission from Chris Jerdonek:
After the section describing roles that create cross-references to C-language
constructs, the Dev Guide says this, The following roles don’t do anything
special except formatting the text in a different style.
Meador Inge added the comment:
Raymond, Stephen's analysis seems correct. Are we missing something or can
this issue be closed?
--
nosy: +meador.inge
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14182
Meador Inge added the comment:
I left some commits in Rietveld. Otherwise, looks OK.
--
assignee: - meador.inge
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15424
___
Changes by Meador Inge mead...@gmail.com:
--
stage: - needs patch
type: - behavior
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15566
___
___
STINNER Victor added the comment:
Here is a Python implementation of TextIOWrapper.set_encoding().
The main limitation is that it is not possible to set the encoding on a
non-seekable stream after the first read (if the read buffer is not empty, ie.
if there are pending decoded characters).
STINNER Victor added the comment:
That will be fragile. A bit of prematurate input or output
(for whatever reason) and your program breaks.
I agree that it is not the most pure solution, but sometimes practicality beats
purity (rule #9) ;-) We can add an ugly big red warning in the doc ;-)
STINNER Victor added the comment:
My implementation permits to change both (encoding, errors, encoding and
errors).
We may also add a set_errors() method:
def set_errors(self, errors):
self.set_encoding(self.encoding, errors)
--
___
Python
Roger Serwy added the comment:
Karen, thank you for your reply and your cooperation. This issue may
take some time to resolve.
It looks like the error you are receiving has been addressed in
issue11288. Can you check it out?
--
___
Python tracker
Petri Lehtinen added the comment:
Thinking about this again, I guess the original design rationale was not to
prepare for crashes, but for the ease of implementation. It's not generally
possible to rewrite the mailbox fully in-place, because the messages are not
loaded into memory. If the
New submission from Dmitry Dvoinikov:
The following script
---
import email.header
print(email.header.decode_header(foo =?windows-1251?Q?bar?=))
---
produces
[(b'foo', None), (b'bar', 'windows-1251')]
in Python 3.2 but
[(b'foo ', None), (b'bar', 'windows-1251')]
in Python 3.3.0b1
--
New submission from Nick Coghlan:
In discussing #15216, I noticed that the write_through parameter is completely
unused in the Python implementation of TextIOWrapper.
That also means we have a hole in the test coverage: there is no test that is
run on both the C and Python versions to ensure
Nick Coghlan added the comment:
The reason I marked this as a release blocker for 3.4 is because it's a key
piece of functionality for writing command line apps which accept an encoding
argument. I'll use high instead.
An interesting proposal was posted to the python-dev thread [1]: using
82 matches
Mail list logo
