[issue13290] get vars for object with __slots__
New submission from João Bernardo jbv...@gmail.com:
I just realized the builtin function `vars` can't handle custom objects without
the __dict__ attribute.
It would be nice if it worked with objects that have __slots__ to make them
look more like normal objects and to make debugging easier.
I changed the source of Python/bltinmodule.c to accept this new case, but, as
I'm fairly new to the C API, it may not be much good.
I'm attaching the whole file to this Issue and the `builtin_vars` function was
modified (lines 1859 to 1921) to work with:
__slots__ = ('a', 'b', 'c')
__slots__ = 'single_name'
__slots__ = {'some': 'mapping'}
The output is a dict (just like in the __dict__ case).
#Example
class C:
__slots__ = ['x', 'y']
c = C()
c.x = 123
vars(c)
{'x': 123}
--
components: Interpreter Core
files: bltinmodule.c
messages: 146598
nosy: JBernardo
priority: normal
severity: normal
status: open
title: get vars for object with __slots__
type: feature request
versions: Python 3.2, Python 3.3
Added file: http://bugs.python.org/file23546/bltinmodule.c
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13290
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13289] a spell error in standard lib SocketServer‘s comment
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 8ddd4c618b48 by Ezio Melotti in branch '2.7': #13289: fix typo. http://hg.python.org/cpython/rev/8ddd4c618b48 New changeset fec8fdbccf3b by Ezio Melotti in branch '3.2': #13289: fix typo. http://hg.python.org/cpython/rev/fec8fdbccf3b New changeset 4411a59dc23c by Ezio Melotti in branch 'default': #13289: merge with 3.2. http://hg.python.org/cpython/rev/4411a59dc23c -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13289 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13289] a spell error in standard lib SocketServer‘s comment
Ezio Melotti ezio.melo...@gmail.com added the comment: Fixed, thanks for the report! -- assignee: - ezio.melotti nosy: +ezio.melotti resolution: - fixed stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13289 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue670664] HTMLParser.py - more robust SCRIPT tag parsing
Changes by Ezio Melotti ezio.melo...@gmail.com: -- assignee: - ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue670664 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13281] robotparser.RobotFileParser ignores rules preceeded by a blank line
Petri Lehtinen pe...@digip.org added the comment: Because of the line break, clicking that link gives Server error 404. I don't see a line break, but the comma after the link seems to breaks it. Sorry. The way I read the grammar, 'records' (which start with an agent line) cannot have blank lines and must be separated by blank lines. Ah, true. But it seems to me that having blank lines elsewhere doesn't break the parsing. If other robots.txt parser implementations allow arbitrary blank lines, we could add a strict=False parameter to make the parser non-strict. This would be a new feature of course. Does the parser currently handle blank lines between full records (agentline(s) + ruleline(s)) correctly? I also do not see Crawl-delay and Sitemap (from whitehouse.gov) in the grammar referenced above. So I wonder if de facto practice has evolved. The spec says: Lines with Fields not explicitly specified by this specification may occur in the /robots.txt, allowing for future extension of the format. So these seem to be nonstandard extensions. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13281 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5661] asyncore should catch EPIPE while sending() and receiving()
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset bf1c4984d4e5 by Charles-François Natali in branch 'default': Issue #5661: Add a test for ECONNRESET/EPIPE handling to test_asyncore. Patch http://hg.python.org/cpython/rev/bf1c4984d4e5 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5661 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13238] Add shell command helpers to shutil module
Antoine Pitrou pit...@free.fr added the comment: With the default whitespace escaping (which allows spaces in filenames), wildcard matching still works (thus the list of directories matching the ../py* pattern), but with full quoting it breaks (thus the nothing named '../py*' result). My question is why it would be a good idea to make a difference between whitespace and other characters. If you use a wildcard pattern, generally it won't contain spaces at all, so you don't have to quote it. If you are injecting a normal filename, noticing that whitespace gets quoted may get you a false sense of security until somebody injects a wildcard character that won't get quoted. So what I'm saying is that a middleground between quoting and no quoting is dangerous and not very useful. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13238 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13265] IDLE crashes when printing some unprintable characters.
Changes by maniram maniram maniandra...@gmail.com: -- versions: -Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13265 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5661] asyncore should catch EPIPE while sending() and receiving()
Charles-François Natali neolo...@free.fr added the comment: The test fails on OS X: == ERROR: test_handle_close_after_conn_broken (test.test_asyncore.TestAPI_UseIPv4Poll) -- Traceback (most recent call last): File /Users/buildbot/buildarea/3.x.parc-snowleopard-1/build/Lib/test/test_asyncore.py, line 661, in test_handle_close_after_conn_broken self.loop_waiting_for_flag(client) File /Users/buildbot/buildarea/3.x.parc-snowleopard-1/build/Lib/test/test_asyncore.py, line 523, in loop_waiting_for_flag asyncore.loop(timeout=0.01, count=1, use_poll=self.use_poll) File /Users/buildbot/buildarea/3.x.parc-snowleopard-1/build/Lib/asyncore.py, line 215, in loop poll_fun(timeout, map) File /Users/buildbot/buildarea/3.x.parc-snowleopard-1/build/Lib/asyncore.py, line 196, in poll2 readwrite(obj, flags) File /Users/buildbot/buildarea/3.x.parc-snowleopard-1/build/Lib/asyncore.py, line 123, in readwrite obj.handle_error() File /Users/buildbot/buildarea/3.x.parc-snowleopard-1/build/Lib/asyncore.py, line 112, in readwrite obj.handle_expt_event() File /Users/buildbot/buildarea/3.x.parc-snowleopard-1/build/Lib/asyncore.py, line 476, in handle_expt_event self.handle_expt() File /Users/buildbot/buildarea/3.x.parc-snowleopard-1/build/Lib/test/test_asyncore.py, line 470, in handle_expt raise Exception(handle_expt not supposed to be called) Exception: handle_expt not supposed to be called Looks like the FD is returned in the exception set on OS X... -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5661 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5661] asyncore should catch EPIPE while sending() and receiving()
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 507dfb0ceb3b by Charles-François Natali in branch 'default': Issue #5661: on EPIPE/ECONNRESET, OS X returns the FD with the POLLPRI flag... http://hg.python.org/cpython/rev/507dfb0ceb3b -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5661 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5661] asyncore should catch EPIPE while sending() and receiving()
Xavier de Gaye xdeg...@gmail.com added the comment: The test fails when use_poll is True. The difference between using poll() and poll2(): poll: All the read events are processed before the write events, so the close after the first recv by TestHandler will be followed by a send by TestClient within the same call to poll(). The test is deterministic. poll2: The order in which events are received is os dependent. So it is possible that the first recv by TestHandler is the last event in the 'r' list, so that after the close, a new call to poll2() is done and the first event in this new 'r' list, is not the expected write event for TestClient. What about forcing self.use_poll to False, before calling loop_waiting_for_flag() ? The drawback being that the test will be run twice with the same environment. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5661 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5661] asyncore should catch EPIPE while sending() and receiving()
Charles-François Natali neolo...@free.fr added the comment: The test fails when use_poll is True. The difference between using poll() and poll2(): poll uses select(2), while poll2 uses poll(2) (duh, that's confusing). It seems that on OS X Snow Leopard, poll(2) sets the POLLPRI flag upon EPIPE (and probably doesn't return the FD in the exception set for select(2)...). Not sure whether it's legal, but it's the only OS to do that (POLLPRI usually used for OOB data). Also, note that Tiger doesn't behave that way. OS X often offers such surprises :-) What about forcing self.use_poll to False, before calling loop_waiting_for_flag() ? The drawback being that the test will be run twice with the same environment. I just added an handle_expt() handler, and it works fine. Closing, thanks for the patch! -- assignee: josiahcarlson - resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5661 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13288] SSL module doesn't allow access to cert issuer information
Antoine Pitrou pit...@free.fr added the comment:
It's available in 3.3:
ctx = ssl.SSLContext(ssl.PROTOCOL_TLSv1)
ctx.verify_mode = ssl.CERT_REQUIRED
ctx.set_default_verify_paths()
with ctx.wrap_socket(socket.socket()) as sock:
... sock.connect((svn.python.org, 443))
... cert = sock.getpeercert()
...
pprint.pprint(cert)
{'issuer': ((('organizationName', 'Root CA'),),
(('organizationalUnitName', 'http://www.cacert.org'),),
(('commonName', 'CA Cert Signing Authority'),),
(('emailAddress', 'supp...@cacert.org'),)),
'notAfter': 'Jan 9 20:50:13 2012 GMT',
'notBefore': 'Jan 9 20:50:13 2010 GMT',
'serialNumber': '0806E3',
'subject': ((('commonName', 'svn.python.org'),),),
'subjectAltName': (('DNS', 'svn.python.org'), ('othername', 'unsupported')),
'version': 3}
--
nosy: +pitrou
resolution: - out of date
stage: - committed/rejected
status: open - closed
type: - feature request
versions: -Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.4
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13288
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13238] Add shell command helpers to shutil module
Nick Coghlan ncogh...@gmail.com added the comment: Yeah, I was thinking about this a bit more and realised that I'd rejected the quote everything by default approach before I had the idea of providing a custom conversion specifier to disable the implicit string conversion and quoting. So perhaps a better alternative would be: default - str + shlex.quote !u - unquoted (i.e. normal str.format default behaviour) When you have a concise way to explicitly bypass it, making the default behaviour as safe as possible seems like a good way to go. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13238 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10363] Embedded python, handle (memory) leak
Antoine Pitrou pit...@free.fr added the comment: If the handle leaks are restricted to the windows implementation of cpython, could it not be justified to allow C++ in a patch, I can't think of a C only compiler for windows? Well, I think that would be rather clumsy. I'm not a Windows user myself, perhaps other people can share opinions. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10363 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12905] multiple errors in test_socket on OpenBSD
Charles-François Natali neolo...@free.fr added the comment: Rémi, do you want to submit a patch to skip those tests on OpenBSD? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12905 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12797] io.FileIO and io.open should support openat
Charles-François Natali neolo...@free.fr added the comment: Thanks. Although, on second thought, I'm not sure whether Amaury's idea (allowing a custom opener) is not better... Thoughts? +1. This would also address issues #12760 and #12105. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12797 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12105] open() does not able to set flags, such as O_CLOEXEC
Changes by Charles-François Natali neolo...@free.fr: -- status: open - closed superseder: - io.FileIO and io.open should support openat ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12105 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12760] Add create mode to open()
Changes by Charles-François Natali neolo...@free.fr: -- resolution: - duplicate status: open - closed superseder: - io.FileIO and io.open should support openat ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12760 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12797] io.FileIO and io.open should support openat
Ross Lagerwall rosslagerw...@gmail.com added the comment: What would you envisage the API for the custom opener to look like? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12797 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12797] io.FileIO and io.open should support openat
Antoine Pitrou pit...@free.fr added the comment: What would you envisage the API for the custom opener to look like? The same as os.open(), I would say. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12797 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12797] io.FileIO and io.open should support openat
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com: -- nosy: +Arfrever ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12797 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10363] Embedded python, handle (memory) leak
Martin v. Löwis mar...@v.loewis.de added the comment: As a policy, we will not rely on C++ destructors for cleanup. There are really two issues here: global locks, and module-specific locks. The global locks can and should be released in Py_Finalize, with no API change. Antoine's patch looks good to me. For module-level locks, PEP-3121-style module finalization should be used. Patches are welcome. Martin: Please understand that there are *MANY* more issues with reloading Python in the same process, as a really large number of stuff doesn't get cleanup up on shutdown. Also expect that fixing these will take 10 years or more, unless somebody puts a huge effort into it. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10363 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13284] email.utils.formatdate function does not handle timezones correctly.
Changes by Petri Lehtinen pe...@digip.org: -- nosy: +petri.lehtinen type: - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13284 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13285] signal module ignores external signal changes
Changes by Petri Lehtinen pe...@digip.org: -- nosy: +petri.lehtinen ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13285 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12797] io.FileIO and io.open should support openat
Ross Lagerwall rosslagerw...@gmail.com added the comment: Before I implement it properly, is this the kind of api that's desired? import os import io class MyOpener: def __init__(self, dirname): self.dirfd = os.open(dirname, os.O_RDONLY) def open(self, path, flags, mode): return os.openat(self.dirfd, path, flags, mode) myop = MyOpener(/tmp) f = open(testfile, w, opener=myop.open) f.write(hello) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12797 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10519] setobject.c no-op typo
Changes by Petri Lehtinen pe...@digip.org: -- nosy: +petri.lehtinen ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10519 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12761] Typo in Doc/license.rst
Changes by Petri Lehtinen pe...@digip.org: -- resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12761 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6650] sre_parse contains a confusing generic error message
Changes by Petri Lehtinen pe...@digip.org: -- nosy: +petri.lehtinen ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6650 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12797] io.FileIO and io.open should support openat
Antoine Pitrou pit...@free.fr added the comment: Before I implement it properly, is this the kind of api that's desired? Yes, although I think most people would use a closure instead of a dedicated class. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12797 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12498] asyncore.dispatcher_with_send, disconnection problem + miss-conception
Xavier de Gaye xdeg...@gmail.com added the comment: Actually the class asyncore.dispatcher_with_send do not handle properly disconnection. When the endpoint shutdown his sending part of the socket, but keep the socket open in reading, the current implementation of dispatcher_with_send will close the socket without sending pending data. Adding this method to the class fix the problem: def handle_close(self): if not self.writable(): dispatcher.close() This does not seem to work. The attached Python 3.2 script 'asyncore_12498.py' goes into an infinite loop of calls to handle_read/handle_close when handle_close is defined as above. In this script the Writer sends a 4096 bytes message when connected, the Reader reads only 64 bytes and closes the connection afterwards. Then follows the sequence: select() returns a read event handled by handle_read() handle_read() calls recv() socket.recv() returns 0 to indicate a closed connection recv() calls handle_close This sequence is repeated forever in asyncore.loop() since out_buffer is never empty. Note that after the first 'handle_close' has been printed, there are no 'handle_write' printed, which indicates that the operating system (here linux) states that the socket is not writable. -- nosy: +xdegaye Added file: http://bugs.python.org/file23547/asyncore_12498.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12498 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13280] argparse should use the new Formatter class
Changes by Raymond Hettinger raymond.hettin...@gmail.com: -- resolution: - invalid status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13280 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13281] robotparser.RobotFileParser ignores rules preceeded by a blank line
Terry J. Reedy tjre...@udel.edu added the comment: Sorry, the visual linebreak depends on font size. It *is* the comma that caused the problem. You missed my question about the current test suite. Senthil, you are the listed expert for urllib, which includes robotparser. Any opinions on what to do? -- nosy: +orsenthil ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13281 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13173] Default values for string.Template
Raymond Hettinger raymond.hettin...@gmail.com added the comment: Barry, any thoughts? -- assignee: rhettinger - barry nosy: +barry ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13173 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13274] heapq pure python version uses islice without guarding for negative counts
Ronny Pfannschmidt ronny.pfannschm...@gmail.com added the comment: however some basic consistency between the cpython and pure python versions within the stdlib would be nice since it basically implicitly breaks unaware code on non cpython -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13274 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10519] setobject.c no-op typo
Changes by Armin Rigo ar...@users.sourceforge.net: -- assignee: arigo - ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10519 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13291] latent NameError in xmlrpc package
New submission from Florent Xicluna florent.xicl...@gmail.com: There's two names which should be fixed in xmlrpc package: --- a/Lib/xmlrpc/client.py -elif isinstance(other, (str, unicode)): --- a/Lib/xmlrpc/server.py -response = xmlrpclib.dumps( -xmlrpclib.Fault(1, %s:%s % (exc_type, exc_value)), We may extend test coverage too. -- components: Library (Lib), XML messages: 146622 nosy: flox priority: normal severity: normal stage: test needed status: open title: latent NameError in xmlrpc package type: behavior versions: Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13291 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11638] python setup.py sdist crashes if version is unicode
David Barnett davidbarne...@gmail.com added the comment: Here's a test for the bug. -- keywords: +patch Added file: http://bugs.python.org/file23548/test_unicode_sdist.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11638 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11638] python setup.py sdist crashes if version is unicode
David Barnett davidbarne...@gmail.com added the comment:
One way to fix the symptom (maybe not the correct way) would be to edit
tarfile._Stream._init_write_gz and change the line that reads
self.__write(self.name + NUL)
to something like
self.__write(self.name.encode('utf-8') + NUL)
tarfile is building up an encoded stream of bytes, and whatever self.name is it
needs to be encoded before being inserted into the stream. I'm not positive
UTF-8 is right, and maybe it should only convert if isinstance(self.name,
unicode).
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11638
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13291] latent NameError in xmlrpc package
Florent Xicluna florent.xicl...@gmail.com added the comment: Proposed fix, with some tests. -- keywords: +patch stage: test needed - patch review Added file: http://bugs.python.org/file23549/issue13291_xmlrpc.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13291 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13274] heapq pure python version uses islice without guarding for negative counts
Changes by Alex Gaynor alex.gay...@gmail.com: -- nosy: +alex ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13274 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13274] heapq pure python version uses islice without guarding for negative counts
Changes by Raymond Hettinger raymond.hettin...@gmail.com: -- resolution: - invalid status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13274 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12797] io.FileIO and io.open should support openat
Ross Lagerwall rosslagerw...@gmail.com added the comment: The attached patch adds the opener keyword + tests. -- Added file: http://bugs.python.org/file23550/opener.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12797 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
