Mark Dickinson dicki...@gmail.com added the comment:
Dino: I think Clark already did this:
http://ironpython.codeplex.com/WorkItem/View.aspx?WorkItemId=27186
Sorry; I checked that there was an IronPython issue open before I closed this
one, but forgot to mention it here.
--
Marc-Andre Lemburg m...@egenix.com added the comment:
STINNER Victor wrote:
New submission from STINNER Victor victor.stin...@haypocalc.com:
readbuffer_encode() and charbuffer_encode() are not really encoder nor
related to encodings: they are related to PyBuffer. readbuffer_encode() uses
Marc-Andre Lemburg m...@egenix.com added the comment:
STINNER Victor wrote:
New submission from STINNER Victor victor.stin...@haypocalc.com:
t# format was introduced by r11803 (11 years ago): Implement new format
character 't#'. This is like s#, accepting an object that implements the
Marc-Andre Lemburg m...@egenix.com added the comment:
STINNER Victor wrote:
STINNER Victor victor.stin...@haypocalc.com added the comment:
Patch to remove t#:
- Update c-api/arg.rst documentation
- Replace t# format by y# in codecs.charbuffer_encode()
- Add a note in
STINNER Victor victor.stin...@haypocalc.com added the comment:
Given that y# is not (yet) in wide-spread use, ...
t# is only used once (in codecs.charbuffer_encode()), whereas y# is used by
ossaudiodev, socket and mmap modules (there are 8 functions using y#). There
are 46 functions using y*
STINNER Victor victor.stin...@haypocalc.com added the comment:
Those two encoder functions were meant to be used by Python codec
implementations which want to use the readbuffer and charbuffer
interfaces available in Python via s# and t# to access input
object data.
Ah ok.
They are not
STINNER Victor victor.stin...@haypocalc.com added the comment:
There is another error:
test test_ssl failed -- Traceback (most recent call last):
File
/scratch/pybot-buildarea/trunk.klose-ubuntu-i386/build/Lib/test/test_ssl.py,
line 261, in test_algorithms
s.connect(remote)
File
New submission from Marko Kohtala marko.koht...@gmail.com:
The Windows builds seem to come with SQLite library version 3.5.9, as seen from
sqlite3.sqlite_version. This is from 2008-May-12.
I've been using the sqlite3 module, but keep running into bugs on Windows.
Replacing the
Marc-Andre Lemburg m...@egenix.com added the comment:
STINNER Victor wrote:
STINNER Victor victor.stin...@haypocalc.com added the comment:
Given that y# is not (yet) in wide-spread use, ...
t# is only used once (in codecs.charbuffer_encode()), whereas y# is used by
ossaudiodev, socket
New submission from Andrew Nelis andrew.ne...@gmail.com:
When using Digest authentication to authenticate with a web server, according
to rfc2617 (section 3.2.2.5) the uri in the Authorization header MUST match the
request URI.
urllib2.AbstractDigestAuthHandler doesn't honour this when we
Marc-Andre Lemburg m...@egenix.com added the comment:
STINNER Victor wrote:
STINNER Victor victor.stin...@haypocalc.com added the comment:
Those two encoder functions were meant to be used by Python codec
implementations which want to use the readbuffer and charbuffer
interfaces
Amaury Forgeot d'Arc amaur...@gmail.com added the comment:
I don't like the import errno while printing an exception...
It would be much more robust to store errorcode_dict in a static variable when
python starts, and reuse it directly.
--
nosy: +amaury.forgeotdarc
STINNER Victor victor.stin...@haypocalc.com added the comment:
Le vendredi 28 mai 2010 13:30:22, vous avez écrit :
Looking at the implementation again, I found that y# rejects
Unicode, while s# returns the default encoded version like
t# does in Python2.
Oh, I didn't noticed that.
So I
Antoine Pitrou pit...@free.fr added the comment:
Any Python object can expose a buffer interface and the above
functions then allow accessing these interfaces from within
Python.
What's the point? The codecs functions already support objects exposing the
buffer interface:
b = b\xe9
Antoine Pitrou pit...@free.fr added the comment:
Agreed with Amaury. Module import could fail for various reasons (perhaps the
same ones which led to the exception being raised!), or could deadlock if the
import lock is being held. Also, having __str__ fail is usually very annoying
for users
Alexander Belopolsky alexander.belopol...@gmail.com added the comment:
The patch already checks for failed import and falls back to printing
numerical error code. However, I don't like the import either. I will
think about the alternatives.
On May 28, 2010, at 8:27 AM, Antoine Pitrou
Marc-Andre Lemburg m...@egenix.com added the comment:
Antoine Pitrou wrote:
Antoine Pitrou pit...@free.fr added the comment:
Any Python object can expose a buffer interface and the above
functions then allow accessing these interfaces from within
Python.
What's the point? The codecs
Éric Araujo mer...@netwok.org added the comment:
I’d be grateful if someone could post links to discussion about the removal of
codecs like hex and rot13 and about their coming back. It may be useful for a
NEWS entry too, not just for my personal curiosity ;) I’ll try to find them
next week
Antoine Pitrou pit...@free.fr added the comment:
class BinaryDataCodec(codecs.Codec):
# Note: Binding these as C functions will result in the class not
# converting them to methods. This is intended.
encode = codecs.readbuffer_encode
decode = codecs.latin_1_decode
What's
STINNER Victor victor.stin...@haypocalc.com added the comment:
I’d be grateful if someone could post links to discussion
about the removal of codecs like hex and rot13
r55932 (~3 years ago):
Rip out all codecs that can't work in a unicode/bytes world:
base64, uu, zlib, rot_13, hex, quopri,
Éric Araujo mer...@netwok.org added the comment:
Thanks for the link. Do you have a pointer to the PEP or ML thread
discussing that change?
“Which coming back?”
Martin said these codecs are coming back in 3.2.
--
title: Remove codecs.readbuffer_encode()and
Changes by Antoine Pitrou pit...@free.fr:
--
assignee: - orsenthil
nosy: +orsenthil
stage: - patch review
versions: +Python 2.6, Python 3.1, Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8843
Changes by Antoine Pitrou pit...@free.fr:
--
nosy: +loewis
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8839
___
___
Python-bugs-list mailing
STINNER Victor victor.stin...@haypocalc.com added the comment:
Martin said these codecs are coming back in 3.2.
Oh, there is the issue #7485 where Martin wrote:
* 2009-12-10 23:15: It was a mistake that they were integrated
* 2009-12-12 19:25: I would still be opposed to such a change (...)
Changes by STINNER Victor victor.stin...@haypocalc.com:
--
nosy: +haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7475
___
___
Walter Dörwald wal...@livinglogic.de added the comment:
I’d be grateful if someone could post links to discussion
about the removal of codecs like hex and rot13
r55932 (~3 years ago):
That was my commit. ;)
Thanks for the link. Do you have a pointer to the PEP or ML thread
discussing
Marc-Andre Lemburg m...@egenix.com added the comment:
Antoine Pitrou wrote:
Antoine Pitrou pit...@free.fr added the comment:
class BinaryDataCodec(codecs.Codec):
# Note: Binding these as C functions will result in the class not
# converting them to methods. This is intended.
STINNER Victor victor.stin...@haypocalc.com added the comment:
Oh, there is the issue #7485 where Martin wrote:
Copy/paste failure: issue #7475.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8838
Marc-Andre Lemburg m...@egenix.com added the comment:
STINNER Victor wrote:
Martin said these codecs are coming back in 3.2.
I said that and it was discussed on the python-dev mailing list
a while back.
We'll also add .transform() methods on bytes and str objects
to access same-type codecs.
STINNER Victor victor.stin...@haypocalc.com added the comment:
readbuffer_encode() and charbuffer_encode() are not really encoder
nor related to encodings: they are related to PyBuffer
That was the initial problem: codecs is specific to encodings (in Python3),
encodes str to bytes, and
Antoine Pitrou pit...@free.fr added the comment:
And all this doesn't address the fact that these functions have never
been documented, and don't seem used in the outside world
(understandably so, since there's no way to know about their existence,
and their intended use).
That's a
Brian Curtin cur...@acm.org added the comment:
SQLite was upgraded to 3.6.21 about 4 months ago for 2.7 and 3.2.
--
nosy: +brian.curtin
resolution: - out of date
status: open - closed
___
Python tracker rep...@bugs.python.org
STINNER Victor victor.stin...@haypocalc.com added the comment:
I agree with Martin: codecs choosed the wrong direction in Python2, and it's
fixed in Python3. The codecs module is related to charsets (encodings), should
encode str to bytes, and should decode bytes (or any read buffer) to str.
STINNER Victor victor.stin...@haypocalc.com added the comment:
Explanation the change in Python3 by Guido:
We are adopting a slightly different approach to codecs: while in Python 2,
codecs can accept either Unicode or 8-bits as input and produce either as
output, in Py3k, encoding is always
Per pybugs.pho...@safersignup.com added the comment:
On POSIX the interpreter will be read from the first line of a file.
On Windows the interpreter will be read from the Registry
HKEY_CLASSES_ROOT\.file-extension .
So the correct way to associate a interpreter to a file is to invent a
Éric Araujo mer...@netwok.org added the comment:
I don't like readbuffer_*encode* and *charbuffer_encode*
function names, because there are different than other codecs
“transform” as hinted by MvL seems perfect.
Thanks everyone for the pointers here and in #7475! I’ll search the missing one
Éric Araujo mer...@netwok.org added the comment:
Related to #870479 (should we make that one a meta-bug?)
--
nosy: +merwok
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4015
___
Marc-Andre Lemburg m...@egenix.com added the comment:
STINNER Victor wrote:
STINNER Victor victor.stin...@haypocalc.com added the comment:
I agree with Martin: codecs choosed the wrong direction in Python2, and it's
fixed in Python3. The codecs module is related to charsets (encodings),
Changes by Éric Araujo mer...@netwok.org:
--
nosy: +merwok
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7475
___
___
Python-bugs-list mailing
Martin v. Löwis mar...@v.loewis.de added the comment:
Thanks for the patch. Committed as r81582 and r81583.
Antoine was right: subsequent references to Solaris needed to be removed also.
--
resolution: - accepted
status: open - closed
___
Python
Changes by Ryan Coyner rcoy...@gmail.com:
--
nosy: +rcoyner
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1100562
___
___
Python-bugs-list mailing
Changes by Ryan Coyner rcoy...@gmail.com:
--
nosy: +rcoyner
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8713
___
___
Python-bugs-list mailing
Brian Curtin cur...@acm.org added the comment:
Committed to trunk in r81584 and py3k in r81585.
--
resolution: - fixed
stage: patch review - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
STINNER Victor victor.stin...@haypocalc.com added the comment:
Committed to trunk in r81584 and py3k in r81585
sparc solaris10 gcc trunk buildbot slave doesn't compile anymore. I'm not
sure that it's related, so I prefer to not reopen the issue :-)
New submission from Mike Hobbs mho...@alvenda.com:
Condition.wait() without a timeout will never raise a KeyboardInterrupt:
cond = threading.Condition()
cond.acquire()
cond.wait()
*** Pressing Ctrl-C now does nothing ***
If you pass a timeout to Condition.wait(), however, it does behave as
anatoly techtonik techto...@gmail.com added the comment:
This issue is so old and I do not have time to reread it fully, unfortunately.
I believe I wanted to install packages using easy_install, pip or whatever
I have and get Scripts/something.bat for my version of Python. This version is
Antoine Pitrou pit...@free.fr added the comment:
In 3.2, even using a timeout doesn't make the call interruptible.
The solution would be to fix the internal locking APIs so that they handle
incoming signals properly, and are able to return an error status.
--
nosy: +gregory.p.smith,
Brett Cannon br...@python.org added the comment:
LGTM as well.
--
nosy: +brett.cannon
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8834
___
___
Antoine Pitrou pit...@free.fr added the comment:
I commited the patch as r81571 in trunk.
Apparently it's ok.
--
assignee: - haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8835
___
New submission from R. David Murray rdmur...@bitdance.com:
I have a use case where I'd like to be able to check whether or not there is an
uncommitted transaction. The use case is a REPL database editor. If the user
issues the 'save' command a commit is done. When they quit the application,
Changes by Shashwat Anand anand.shash...@gmail.com:
--
nosy: +l0nwlf
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8845
___
___
Python-bugs-list
David Watson bai...@users.sourceforge.net added the comment:
Here is a new version of the patch; I've added some tests which
use the RFC 3542 interface (IPv6 advanced API) and am now quite
happy with it generally.
As well as Linux, I've tested it on an old (unsupported) FreeBSD
5.3
Antoine Pitrou pit...@free.fr added the comment:
3.2 is interesting in that it introduces a new internal API:
PyThread_acquire_lock_timed(). We can therefore change that API again before
release without risking any compatibility breakage. Reid, would you want to
work on this?
--
Changes by Antoine Pitrou pit...@free.fr:
--
nosy: +haypo
stage: - patch review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6560
___
___
Shashwat Anand anand.shash...@gmail.com added the comment:
Tested this patch, works perfectly fine. Also it suits for the particular use
case which David mentioned where there is no better alternate approach.
--
Added file: http://bugs.python.org/file17484/dbapi.patch
Jean-Paul Calderone exar...@twistedmatrix.com added the comment:
If the user issues the 'save' command a commit is done. When they quit the
application, I'd like to be able to prompt them with a 'save or discard' if
and only if they have made changes since the last save.
Isn't this the
Changes by Shashwat Anand anand.shash...@gmail.com:
Removed file: http://bugs.python.org/file17484/dbapi.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8845
___
Shashwat Anand anand.shash...@gmail.com added the comment:
conn = sqlite3.connect('dbdump.sqlite')
c = conn.cursor()
conn.in_transaction
False
c.execute('CREATE TABLE foo (id integer, name text)')
sqlite3.Cursor object at 0x1004a7730
conn.in_transaction
False
It gives True for Insert and
R. David Murray rdmur...@bitdance.com added the comment:
@exarkun: yes, but since the module is already tracking that information, it
seems silly to duplicate it in my code, especially since that duplication could
include data-losing bugs.
@l0nwlf: its behaviour is in accord with the module
Changes by Shashwat Anand anand.shash...@gmail.com:
Removed file: http://bugs.python.org/file17485/dbapi.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8845
___
Shashwat Anand anand.shash...@gmail.com added the comment:
Ok then.
Uploading unit-test which takes value of in_transaction as False after issuing
a Create statement. It passes with the patch applied.
--
Added file: http://bugs.python.org/file17486/dbapi.patch
New submission from Andre Wobst wob...@users.sourceforge.net:
There are serious bugs in carriage return and newline handling at the end of a
multipart cgi input. The enclosed patch extends the test_cgi.py (and actually
reverts two wrong tests to what they had been for python2.x). Additionally,
Changes by Andre Wobst wob...@users.sourceforge.net:
--
type: - behavior
versions: +Python 3.1 -Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8846
___
STINNER Victor victor.stin...@haypocalc.com added the comment:
Commited: r81588 (py3k), blocked in 3.1 (r81589).
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8837
Martin v. Löwis mar...@v.loewis.de added the comment:
Martin said these codecs are coming back in 3.2.
I think you are confusing me with MAL. I remain opposed to adding them
back. Users ought to use the modules that provide these these
conversions as functions.
--
title: Remove
Martin v. Löwis mar...@v.loewis.de added the comment:
The patch lacks documentation. Otherwise, I think it's fine.
--
nosy: +loewis
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8845
___
New submission from benrg benrud...@gmail.com:
c:\python
Python 3.1.2 (r312:79149, Mar 21 2010, 00:41:52) [MSC v.1500 32 bit (Intel)]
on win32
Type help, copyright, credits or license for more information.
from collections import namedtuple
foo = namedtuple('foo', '')
[1] + foo()
Terry J. Reedy tjre...@udel.edu added the comment:
This should not have been closed yet.
The announced policy is that bugfix releases should not add or change APIs. I
think this hidden change (there is no What' New in 3.1.2 doc) should be
reverted in 3.1.3. I will post on py-dev for other
Changes by Chris Leary christopher.le...@cornell.edu:
--
nosy: +cdleary
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7593
___
___
STINNER Victor victor.stin...@haypocalc.com added the comment:
Patch to cleanup getbuffer() and convertbuffer():
- getbuffer() doesn't call convertbuffer() if pb-bf_getbuffer==NULL. If
pb-bf_getbuffer==NULL, PyObject_GetBuffer() fails and so the call to
convertbuffer() is useless.
-
New submission from STINNER Victor victor.stin...@haypocalc.com:
U and U# formats were introduced by r55433 (Python3). At this same, s and
U formats were different: s called PyString_FromStringAndSize() and U
called PyUnicode_FromStringAndSize(). Two months later,
PyString_FromStringAndSize()
Changes by Rodrigo Bernardo Pimentel r...@isnomore.net:
--
nosy: +rbp
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2516
___
___
Python-bugs-list
New submission from STINNER Victor victor.stin...@haypocalc.com:
w format is dangerous because it doesn't give the size of the buffer: the
caller may write outside the buffer (buffer overflow).
w* and w# formats are fine.
It looks like w format is not used in trunk nor py3k (only w# and w*).
STINNER Victor victor.stin...@haypocalc.com added the comment:
Patch to update the documenation, especially input types for PyArg_ParseTuple()
and output types for Py_BuildValue():
- add bytes and/or bytearray when buffer compatible object is accepted to be
more explicit
- es, et, es#, et#
STINNER Victor victor.stin...@haypocalc.com added the comment:
Less extreme patch: set 'U' as an alias to 's' (and 'U#' as an alias to 's#').
Replace usage of 'U' by 's'.
Note: 'z' is also an alias to 's', and 'z#' an alias to 's#'.
--
keywords: +patch
Added file:
Changes by STINNER Victor victor.stin...@haypocalc.com:
--
title: Remove U and U# formats of Py_BuildValue() - Deprecate or remove
U and U# formats of Py_BuildValue()
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8848
Reid Kleckner r...@mit.edu added the comment:
I'd like to fix it, but I don't know if I'll be able to in time. It was
something that bugged me while running the threading tests while working on
Unladen.
I'm imagining (for POSIX platforms) adding some kind of check for signals when
the
Nick Coghlan ncogh...@gmail.com added the comment:
For the record, Guido's decision to change 3.1:
http://mail.python.org/pipermail/python-dev/2009-September/092247.html
--
nosy: +ncoghlan
___
Python tracker rep...@bugs.python.org
Nick Coghlan ncogh...@gmail.com added the comment:
To avoid any confusion in the future, it should be noted that Antoine did not
unilaterally make the decision to commit this change to a maintenance branch.
This change was discussed on python-dev, with the ultimate decision to update
the 3.1
New submission from MATSUI Tetsushi m...@users.sourceforge.net:
The library reference of pkgutil is only sparsely marked up.
The attached patch is against 2.6 version, because I'm currently working with
2.6. Since a part of markups (namely :pep:'s) has already been done for 3.2
version, the
Changes by Eric Smith e...@trueblade.com:
--
nosy: +eric.smith
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1724822
___
___
Python-bugs-list
81 matches
Mail list logo
