[issue24755] asyncio.wrap_future undocumented

Changes by Andrej A Antonov : -- nosy: +polymorphm ___ Python tracker <http://bugs.python.org/issue24755> ___ ___ Python-bugs-list mailing list Unsubscribe:

Re: [issue22798] time.mktime doesn't update time.tzname

> varies among platforms. tzname is set when the module is being loaded and not updated afterwards (unless you call tzset()). I can't really see why you would expect a module global in Python to follow the semantics of a C global, unless this is explicitly documented. Note: The fact tha

[issue22032] Use __qualname__ together with __module__

Barry A. Warsaw added the comment: I'm not expecting a change either, I was also just documenting observed breakages. Given that I've ported a *ton* of code to 3.5 and only seen a handful of failures related to this issue, I agree that it's better just to provide information a

[issue25222] 3.5.0 regression - Fatal Python error: Cannot recover from stack overflow

Changes by A. Jesse Jiryu Davis : -- nosy: +emptysquare ___ Python tracker <http://bugs.python.org/issue25222> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue25154] Drop the pyvenv script

Barry A. Warsaw added the comment: I have a patch which will at least improve the error message when `python3 -m venv` fails because python3-venv isn't installed on Debian/Ubuntu. I will work with Doko on this. -- ___ Python tracker

[issue25159] Import time regression

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <http://bugs.python.org/issue25159> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue25154] Drop the pyvenv script

Changes by Barry A. Warsaw : -- nosy: +doko ___ Python tracker <http://bugs.python.org/issue25154> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue25154] Drop the pyvenv script

Barry A. Warsaw added the comment: I'm sympathetic, given that in Debian/Ubuntu (and maybe other distros) where we have both Python 3.4 and 3.5, we have to install /usr/bin/pyvenv-3.4 and pyvenv-3.5, and then use symlinks to provide the default ve

[issue25154] Drop the pyvenv script

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <http://bugs.python.org/issue25154> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue25061] Add native enum support for argparse

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <http://bugs.python.org/issue25061> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue24965] Implement PEP 498: Literal String Formatting

Barry A. Warsaw added the comment: On Sep 09, 2015, at 11:57 PM, Eric V. Smith wrote: >There's one nit where I accept 'f' and 'F', but the PEP just says 'f'. I'm >not sure if we should accept the upper case version. I'd think not, but all >

[issue25008] Deprecate smtpd

Barry A. Warsaw added the comment: On Sep 07, 2015, at 02:26 PM, STINNER Victor wrote: >Can we modify the issue title to "Rewrite smtpd with asyncio"? Sure, although I'm currently thinking it's best to go third party until the API and imp

[issue25002] Deprecate asyncore/asynchat

Barry A. Warsaw added the comment: On Sep 04, 2015, at 08:55 PM, STINNER Victor wrote: >Maybe it can be fun to rewrite the module using asyncio, but I'm not >convinced that a SMTP server in the Python stdlib is super useful. As I mentioned in issue25008, removing smtpd would be a h

[issue25014] Add contextlib.itercm()

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <http://bugs.python.org/issue25014> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue25008] Deprecate smtpd

Barry A. Warsaw added the comment: Removing smtpd would definitely be a hardship for me right now, probably for obvious reasons. I use it in testing frameworks, and even wrote a library called lazr.smtptest that is built around smtpd. In Mailman, we have an LMTP server built on smtpd that

[issue24997] mock.call_args compares as equal and not equal

New submission from A Kaptur: mock.call_args can be both equal to and not equal to another object: >>> m = Mock() >>> m(1,2) >>> m.call_args call(1, 2) >>> m.call_args == call(1,2) True >>> m.call_args != call(1,2) True This appears to be a recen

[issue24857] mock: Crash on comparing call_args with long strings

A Kaptur added the comment: Here's a simple patch + test for the original bug. I'll file the __ne__ question separately. -- keywords: +patch stage: needs patch -> patch review Added file: http://bugs.python.org/file40348/issue24857.patch _

[issue24857] mock: Crash on comparing call_args with long strings

A Kaptur added the comment: It looks like there's a related bug in call_args around __ne__: >>> m = Mock() >>> m(1,2) >>> m.call_args call(1, 2) >>> m.call_args == call(1,2) True >>> m.call_args != call(1,2) True Any reason not to define __ne

[issue7175] Define a standard location and API for configuration files

Barry A. Warsaw added the comment: On Sep 01, 2015, at 07:15 PM, Glyph Lefkowitz wrote: >There are other advantages to following the XDG spec. If we follow it >correctly (and not, like Barry suggested, start adding random other >directories like ~/.python) I was really just suggestin

[issue7175] Define a standard location and API for configuration files

Barry A. Warsaw added the comment: I'm of mixed opinion. I personally don't like cluttering up my $HOME with a jillion dotfiles so I appreciate the organization XDG_CONFIG_HOME offers. But that also makes things less discoverable. Looking in XDG_CONFIG_HOME first with a fallbac

[issue24965] Implement PEP 498: Literal String Formatting

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <http://bugs.python.org/issue24965> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue24941] classproperty

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <http://bugs.python.org/issue24941> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue24383] consider implementing __await__ on concurrent.futures.Future

Changes by A. Jesse Jiryu Davis : -- nosy: +emptysquare ___ Python tracker <http://bugs.python.org/issue24383> ___ ___ Python-bugs-list mailing list Unsubscribe:

Re: [issue24872] Add /NODEFAULTLIB:MSVCRT to _msvccompiler

On 15.08.2015 22:41, Steve Dower wrote: > > Marc-Andre: there are a few concerns with including DLLs that aren't new with > any of the 3.5 changes. > > * depending on another CRT version is fine *if* it is available (users may > have to be told/helped to install the red

[issue23812] asyncio.Queue.put_nowait(), followed get() task cancellation leads to item being lost

Gustavo J. A. M. Carneiro added the comment: I am not using hg anymore, since asyncio migrated to git. Here's a github PR, does that help? https://github.com/python/asyncio/pull/260 -- ___ Python tracker <http://bugs.python.org/is

[issue23812] asyncio.Queue.put_nowait(), followed get() task cancellation leads to item being lost

Gustavo J. A. M. Carneiro added the comment: I was wrong, there still needs to be some cleanup in cancellation, even with the new approach. But it does solve the out-of-order problem. I don't know if it should be applied to rc1. I wish I had more time to test. Up to you

[issue23812] asyncio.Queue.put_nowait(), followed get() task cancellation leads to item being lost

Gustavo J. A. M. Carneiro added the comment: Sure, just give me a couple of days. -- ___ Python tracker <http://bugs.python.org/issue23812> ___ ___ Python-bug

[issue23812] asyncio.Queue.put_nowait(), followed get() task cancellation leads to item being lost

Gustavo J. A. M. Carneiro added the comment: I don't think the order for multiple concurrent getters matters that much. With analogy with the threading case, if multiple threads are blocked get()ing an item from the same queue, I would not presume to expect anything about the ordering

[issue23812] asyncio.Queue.put_nowait(), followed get() task cancellation leads to item being lost

Gustavo J. A. M. Carneiro added the comment: Don't know if it helps, but I made a github pull request for this: https://github.com/python/asyncio/pull/256 -- ___ Python tracker <http://bugs.python.org/is

[issue15014] smtplib: add support for arbitrary auth methods

Changes by Barry A. Warsaw : -- assignee: -> barry status: open -> closed ___ Python tracker <http://bugs.python.org/issue15014> ___ ___ Python-bugs-list

[issue15014] smtplib: add support for arbitrary auth methods

Barry A. Warsaw added the comment: Thanks! -- ___ Python tracker <http://bugs.python.org/issue15014> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue15014] smtplib: add support for arbitrary auth methods

Barry A. Warsaw added the comment: On Jul 07, 2015, at 05:59 PM, R. David Murray wrote: >I don't see any need to add the is_initial_auth_ok flag. Either the auth >method returns something that is not None (initial auth is OK), or it doesn't >(initial auth is not OK). I

[issue15014] smtplib: add support for arbitrary auth methods

Barry A. Warsaw added the comment: Attached patch includes test, documentation, and implementation. While this is technically a new feature, it fixes a regression in Python 3.5 w.r.t. 3.4. I'll email python-dev with a request for beta exemption. -- Added file: http://bugs.pytho

[issue15014] smtplib: add support for arbitrary auth methods

Barry A. Warsaw added the comment: I have a patch to support initial-response, which I'll be posting here after a bit of clean up and a full (local) test run, with documentation. I ended up adding a keyword argument `initial_response_ok=True` to .login() and .auth(). The reason for th

Re: [issue24534] disable executing code in .pth files

On 01.07.2015 00:16, Min RK wrote: > >> Just because a feature can be misused doesn't make it a bad feature. > > That's fair. I'm just not aware of any uses of this feature that aren't > misuses, hence the patch. I don't remember the details of why t

[issue22508] Remove __version__ string from email

Barry A. Warsaw added the comment: When I ported Mailman 3 to Python 3.5 I had to remove the check on email.__version__ :) -- ___ Python tracker <http://bugs.python.org/issue22

[issue22032] Use __qualname__ together with __module__

Barry A. Warsaw added the comment: FWIW, this broke the zope.testing doctests: https://bugs.launchpad.net/zope.testing/+bug/1467644 I submitted a patch, which was reasonable given the normalization that zope.testing does for doctest output, but people should be aware that this can break

[issue21935] Implement AUTH command in smtpd.

Barry A. Warsaw added the comment: Martin says: "I cannot see any particular circumstances where unencrypted passwords for smtpd would be acceptable, given that there are perfectly established technologies. So I remain -1 on this patch." Here's a use case: a testing SMTP

[issue15014] smtplib: add support for arbitrary auth methods

Barry A. Warsaw added the comment: On Jun 22, 2015, at 10:00 PM, R. David Murray wrote: >We change the authobj signature to challenge=None, then the first thing we do >in auth is 'initial_response = authobj()'. The return value can be the empty >string or a real initial val

[issue15014] smtplib: add support for arbitrary auth methods

Barry A. Warsaw added the comment: Also, smtpd is not compatible with auth challenges because found_terminator() doesn't know that the response its getting isn't a command but instead a challenge response. So really we need another bug to track fixes to smtpd.py to handle challenge

[issue15014] smtplib: add support for arbitrary auth methods

Barry A. Warsaw added the comment: Here's a rough thought for a fix. Some auth_*() methods require a challenge, but some don't, e.g. auth_plain(). Let's allow authobject() to be called with challenge=None. If they allow an initial-response, then they can just return the resp

[issue15014] smtplib: add support for arbitrary auth methods

Barry A. Warsaw added the comment: I believe this change broke RFC 4954's AUTH command when the optional initial-response is expected. $4 "The AUTH Command" says: AUTH mechanism [initial-response] ... initial-response: An optional initial client response. If present,

[issue19995] %c, %o, %x, %X accept non-integer values instead of raising an exception

Barry A. Warsaw added the comment: Fix: >>> '%.32x' % uuid4().int -- ___ Python tracker <http://bugs.python.org/issue19995> ___ ___ Pyth

[issue19995] %c, %o, %x, %X accept non-integer values instead of raising an exception

Barry A. Warsaw added the comment: Found my first 3.5 breakage which I think is due to this. >>> from uuid import uuid4 >>> '%.32x' % uuid4() -- nosy: +barry ___ Python tracker <ht

[issue24454] Improve the usability of the match object named group API

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <http://bugs.python.org/issue24454> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue24351] string.Template documentation incorrectly references "identifiers"

Changes by Barry A. Warsaw : -- resolution: -> fixed status: open -> closed ___ Python tracker <http://bugs.python.org/issue24351> ___ ___ Python-bugs-list

[issue24412] setUpClass equivalent for addCleanup

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <http://bugs.python.org/issue24412> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue24351] string.Template documentation incorrectly references "identifiers"

Barry A. Warsaw added the comment: Rather than change the code, which strives to keep the "Simple" in PEP 292's title, I'd rather just update the documentation to define what "identifier" means here. E.g. " * ``$identifier`` names a substitution pl

[issue24168] Unittest discover fails with namespace package if the path contains the string same as the module name

Barry A. Warsaw added the comment: If you need a test case, try https://gitlab.com/warsaw/flufl.lock -- ___ Python tracker <http://bugs.python.org/issue24

[issue24168] Unittest discover fails with namespace package if the path contains the string same as the module name

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <http://bugs.python.org/issue24168> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue19699] Update zipimport for PEP 451

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <http://bugs.python.org/issue19699> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue23968] rename the platform directory from plat-$(MACHDEP) to plat-$(PLATFORM_TRIPLET)

Barry A. Warsaw added the comment: I don't know what problems I might have run into previously, but it's working now and seems fine to me. +1 -- nosy: +barry ___ Python tracker <http://bugs.python.o

[issue24309] string.Template should be using str.format and/or deprecated

Barry A. Warsaw added the comment: So yeah, we don't want to deprecate string.Template. It has a very specific use case that's used a lot, i.e. making strings dead simple to translate. %(foo)s was very problematic. {foo} is a little better, but looks too weird for most translat

[issue24305] The new import system makes it impossible to correctly issue a deprecation warning for a module

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <http://bugs.python.org/issue24305> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue6598] calling email.utils.make_msgid frequently has a non-trivial probability of generating colliding ids

Barry A. Warsaw added the comment: On May 19, 2015, at 07:23 AM, Serhiy Storchaka wrote: >Now there is a question. Is it worth to use base16 (hexadecimal) to compact >message id to 34 characters or base32 to compact it to 27 characters? Using >base16 is pretty easy: just replace %

[issue6598] calling email.utils.make_msgid frequently has a non-trivial probability of generating colliding ids

Barry A. Warsaw added the comment: An increase of 13 characters doesn't seem so bad. -- ___ Python tracker <http://bugs.python.org/issue6598> ___ ___ Pytho

[issue23699] Add a macro to ease writing rich comparisons

Barry A. Warsaw added the comment: @rhettinger: OTOH, a macro can provide uniformity and correctness. If (as appears evident from the patch) those "10 lines of boilerplate" are actually implemented subtly differently each time, bugs can be easily introduced. So a well written and

[issue10544] yield expression inside generator expression does nothing

Changes by A. Jesse Jiryu Davis : -- nosy: +emptysquare ___ Python tracker <http://bugs.python.org/issue10544> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue24077] man page says -I implies -S. code says -s.

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <http://bugs.python.org/issue24077> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue23058] argparse silently ignores arguments

Barry A. Warsaw added the comment: > Wouldn't it be safer all around if the subparsers took different arguments, > or at least different namespace 'dest', than the main parser? IMHO, yes. I agree that the semantics of what the original code is trying to do is quite

[issue23058] argparse silently ignores arguments

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <http://bugs.python.org/issue23058> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue23699] Add a macro to ease writing rich comparisons

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <http://bugs.python.org/issue23699> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue24029] Surprising name binding behavior of submodule imports needs documenting

Changes by Barry A. Warsaw : -- resolution: -> fixed status: open -> closed ___ Python tracker <http://bugs.python.org/issue24029> ___ ___ Python-bugs-list

[issue24029] Surprising name binding behavior of submodule imports needs documenting

Barry A. Warsaw added the comment: Cool, thanks! I'll commit it and we can always clean it up/add to it later if needed. -- ___ Python tracker <http://bugs.python.org/is

[issue24029] Surprising name binding behavior of submodule imports needs documenting

Barry A. Warsaw added the comment: Here's some new text for the Language Reference. -- Added file: http://bugs.python.org/file39175/issue24029-1.txt ___ Python tracker <http://bugs.python.org/is

[issue24029] Surprising name binding behavior of submodule imports needs documenting

Barry A. Warsaw added the comment: More rationale from the thread: > The surprising part is that it also happens for explicit relative > imports. I'm guessing that part was unintentional and simply not > noticed when PEP 328 was implemented. > No, that must also have

[issue24029] Surprising name binding behavior of submodule imports needs documenting

Barry A. Warsaw added the comment: >From Guido: It's definitely intentional, and it's fundamental to the package import design. We've had many implementations of package import (remember "ni.py"? last seen as "knee.py") and it was always there, because this

[issue24029] Surprising name binding behavior of submodule imports needs documenting

New submission from Barry A. Warsaw: As described here: http://news.gmane.org/find-root.php?message_id=20150422115959.1ff2ee58%40limelight.wooz.org Importing a submodule binds the submodule's name in the parent module's namespace. This is surprising, but it seems intentional and i

[issue18128] pygettext: non-standard timestamp format in POT-Creation-Date

Barry A. Warsaw added the comment: @rdm: I'm pretty sure you're right about nobody noticing. :) Make it so! -- ___ Python tracker <http://bugs.python.o

[issue22652] Add suggestion about keyword arguments to this error message: "builtins.TypeError: my_func() takes 1 positional argument but 2 were given"

A. Jesse Jiryu Davis added the comment: Attached patch adds "and N keyword-only argument(s)" to the TypeError message if a function takes keyword-only arguments and the wrong number of positional arguments is provided. -- keywords: +patch nosy: +emptysquare Added

[issue23915] traceback set with BaseException.with_traceback() overwritten on raise

A. Jesse Jiryu Davis added the comment: I've had a very hard time adding to the doc in a way that elucidates rather than further obfuscating; see if you like this patch. -- keywords: +patch nosy: +emptysquare Added file: http://bugs.python.org/file38916/issue23915.

[issue23464] Remove or deprecate JoinableQueue in asyncio docs

Changes by A. Jesse Jiryu Davis : -- keywords: +patch Added file: http://bugs.python.org/file38906/issue23464.diff ___ Python tracker <http://bugs.python.org/issue23

[issue23915] traceback set with BaseException.with_traceback() overwritten on raise

Travis A. Everett added the comment: Thanks, Martin--I should've thought to check to see if it'd just been pushed back in the list. I was just focusing on a workaround for another problem and did a double-take when the traceback value didn't match what was set. This resolutio

[issue23915] traceback set with BaseException.with_traceback() overwritten on raise

New submission from Travis A. Everett: When BaseException.with_traceback(tb) is used, the __traceback__ property is properly set, but the property gets overwritten when the exception is raised. The attached file demonstrates the issue by raising exception a, which doesn't use with_trac

[issue23910] C implementation of namedtuple (WIP)

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <http://bugs.python.org/issue23910> ___ ___ Python-bugs-list mailing list Unsubscribe:

Re: [issue23857] Make default HTTPS certificate verification setting configurable via global ini file

On 05.04.2015 22:49, Donald Stufft wrote: > > Donald Stufft added the comment: > >> I don't consider monkey patching a proper way to configure a Python >> installation. > > The point is that that TLS validation on/off isn't conceptually a Python level >

Re: [issue23857] Make default HTTPS certificate verification setting configurable via global ini file

FWIW: I just ran into a situation where the new approach resulted in pip, setuptools and zc.buildout not working anymore. This was on an AIX system which did come with CA root certificates at all. Now, I knew how to fix this, but the solution was not an obvious one. I had to use truss to figure

[issue23857] Make default HTTPS certificate verification setting configurable via global ini file

Barry A. Warsaw added the comment: +1 for keyed by site There have been a number of issues over the years for which a configuration file (or files) would have been useful. I think a discussion over on python-ideas is the right way to move forward on this point

[issue23842] SystemError: ../Objects/longobject.c:998: bad argument to internal function

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <http://bugs.python.org/issue23842> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue23812] asyncio.Queue.put_nowait(), followed get() task cancellation leads to item being lost

Gustavo J. A. M. Carneiro added the comment: So I uploaded a new patch version fixing a similar problem in put(). -- ___ Python tracker <http://bugs.python.org/issue23

[issue23812] asyncio.Queue.put_nowait(), followed get() task cancellation leads to item being lost

Gustavo J. A. M. Carneiro added the comment: > - Are there other places where a cancellation can have a similar effect? > Maybe the same logic in put()? Hm.. I didn't look, but yes, it does look like it might be affected by the same issue. I'll try to create a test for

[issue23812] asyncio.Queue.put_nowait(), followed get() task cancellation leads to item being lost

Gustavo J. A. M. Carneiro added the comment: I created a codereview issue: https://codereview.appspot.com/222930043 -- ___ Python tracker <http://bugs.python.org/issue23

[issue23812] asyncio.Queue.put_nowait(), followed get() task cancellation leads to item being lost

Changes by Gustavo J. A. M. Carneiro : Added file: http://bugs.python.org/file38741/Issue23812.diff ___ Python tracker <http://bugs.python.org/issue23812> ___ ___ Pytho

[issue23812] asyncio.Queue.put_nowait(), followed get() task cancellation leads to item being lost

New submission from Gustavo J. A. M. Carneiro: I have a pattern where I read from a queue with a timeout, generally like this: while True: reader = asyncio.async(wait_for(queue.get(), 0.1)) try: item = (yield from reader) except asyncio.TimeoutError: reader.cancel() continue

[issue23731] Implement PEP 488

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <http://bugs.python.org/issue23731> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue23486] Enum member lookup is 20x slower than normal class attribute lookup

Barry A. Warsaw added the comment: Poor performance could fall under the category of bug fixes, so for an in-maintenance mode release, a fix that does not in any way change user visible behavior could be acceptable. It would probably be fine for 3.4 but I'm just +0 on it. Larry&#

[issue23592] SIGSEGV on interpreter shutdown, with daemon threads running wild

A. Skrobov added the comment: That's right; and working around this issue, by taming the daemon threads a bit, wasn't too difficult. Still, if the daemon threads are part of the language, they shouldn't crash the interpreter pro

[issue23592] SIGSEGV on interpreter shutdown, with daemon threads running wild

New submission from A. Skrobov: I'm observing that this line of code: https://hg.python.org/cpython/file/ec9bffc35cad/Python/ceval.c#l3010 -- causes a SIGSEGV on interpreter shutdown, after running some really convoluted Python code with daemon threads running wild. At the time of the

[issue19035] tokenize.generate_tokens treat '\f' symbol as the end of file (when reading in unicode)

Barry A. Warsaw added the comment: Ha! Apparently this bug broke coverage for the Mailman 3 source code: https://bitbucket.org/ned/coveragepy/issue/360/html-reports-get-confused-by-l-in-the-code -- ___ Python tracker <http://bugs.python.

[issue19035] tokenize.generate_tokens treat '\f' symbol as the end of file (when reading in unicode)

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <http://bugs.python.org/issue19035> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue12782] Multiple context expressions do not support parentheses for continuation across lines

Changes by Barry A. Warsaw : -- resolution: -> wont fix status: open -> closed ___ Python tracker <http://bugs.python.org/issue12782> ___ ___ Python-bugs-

[issue12782] Multiple context expressions do not support parentheses for continuation across lines

Barry A. Warsaw added the comment: Let's just Won't Fix this. Use a contextlib.ExitStack. -- ___ Python tracker <http://bugs.python.org/issue12782> ___ ___

[issue23464] Remove or deprecate JoinableQueue in asyncio docs

New submission from A. Jesse Jiryu Davis: asyncio.JoinableQueue was once a distinct subclass of asyncio.Queue, now it's just a deprecated alias. Once this is merged into CPython: https://code.google.com/p/tulip/issues/detail?id=220 ...then remove or deprecate JoinableQueue in asyncio-syn

[issue23399] venv should create relative symlinks where possible

Changes by Barry A. Warsaw : -- resolution: -> fixed status: open -> closed ___ Python tracker <http://bugs.python.org/issue23399> ___ ___ Python-bugs-list

[issue23399] venv should create relative symlinks where possible

New submission from Barry A. Warsaw: There is a subtle behavior difference between virtualenv and pyvenv. When you create a venv with virtualenv, the symbolic links files /bin are relative, while they are absolute with pyvenv. This means that virtual environments created with virtualenv can

[issue23342] run() - unified high-level interface for subprocess

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <http://bugs.python.org/issue23342> ___ ___ Python-bugs-list mailing list Unsubscribe:

Re: [issue13881] Stream encoder for zlib_codec doesn't use the incremental encoder

te(self, object): +self.stream.write(self._encoder.encode(object)) + +def reset(self): +self.stream.write(self._encoder.encode(final=True)) + Note that the doc-string mentions a non-existing attribute and there are doc-string missing for the other methods. The purpose appears to be a Strea

Re: [issue14014] codecs.StreamWriter.reset contract not fulfilled

Adding a note to the documentation is fine. The .reset() method doesn't have anything to do with the underlying stream. It's only meant to work at the codec level and needed for codecs that keep internal state. -- Marc-Andre Lemburg

[issue23228] Crashes when tarfile contains a symlink and unpack directory contain it too

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <http://bugs.python.org/issue23228> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue23189] Set docstrings to empty string when optimizing with -OO.

Barry A. Warsaw added the comment: That's a backward compatibility break since existing code may be expecting None. At least it needs to be carefully considered, and should have no possibility of be applied to anything before Python 3.5. -- nosy: +barry versions: -Python 2.7, P

<    6   7   8   9   10   11   12   13   14   15   >