[issue26426] email examples: incorrect use of email.headerregistry.Address

Changes by Barry A. Warsaw <ba...@python.org>: -- nosy: +barry ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26426> ___ __

[issue26176] EmailMessage example doesn't work

Changes by Barry A. Warsaw <ba...@python.org>: -- nosy: +barry ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26176> ___ __

[issue26408] pep-8 requires a few corrections

Barry A. Warsaw added the comment: On Feb 22, 2016, at 02:20 PM, Georg Brandl wrote: >Georg Brandl added the comment: > >-Consistency within one module or function is most important. >+Consistency within one module or function is the most important. > >You left out &quo

[issue26408] pep-8 requires a few corrections

Barry A. Warsaw added the comment: Thanks! I like some of the changes, and may tweak a few others. Thanks for the contribution. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i

[issue26408] pep-8 requires a few corrections

Changes by Barry A. Warsaw <ba...@python.org>: -- assignee: docs@python -> barry ___ Python tracker <rep...@bugs.python.org> <http://bugs.pyt

[issue26408] pep-8 requires a few corrections

Changes by Barry A. Warsaw <ba...@python.org>: -- nosy: +barry ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26408> ___ __

[issue25698] The copy_reg module becomes unexpectedly empty in test_cpickle

Barry A. Warsaw added the comment: Thanks for digging deeply and fixing this! -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i

[issue22995] Restrict default pickleability

Barry A. Warsaw added the comment: I've verified that backing out the typeobject.c change allows kivy and pysam to build. s3ql still fails but for other reasons, though its build does get past the cython failure. This clinches it for me. I am going to remove the typeobject.c clause from

[issue22995] Restrict default pickleability

Barry A. Warsaw added the comment: On Jan 11, 2016, at 05:50 PM, Serhiy Storchaka wrote: > >Therefore my guess was true. There is a bug in Cython. It creates classes >that can't be correctly unpickled or copied. I don't think that's necessarily true. Clearly the classes *can*

[issue22995] Restrict default pickleability

Barry A. Warsaw added the comment: On Jan 11, 2016, at 07:20 PM, Serhiy Storchaka wrote: >I think we have to left this restriction in 3.6 (and Cython should fix its >bug by providing either __getnewargs__/ __getnewargs_ex__, __getstate__ or >__reduce__/__reduce_ex__). But in 2.7 a

[issue22995] Restrict default pickleability

Barry A. Warsaw added the comment: BTW Serhiy, can you please file a bug with upstream Cython? I think you're the right person to do it since you added this restriction. With reverting this in 2.7 and 3.5 it's not urgent, but we don't want to have to reopen this when 3.6 is out

[issue22995] Restrict default pickleability

Barry A. Warsaw added the comment: So yeah, I guess Cython is doing something magical to boost the instance's type's basicsize, but I can't tell what from the Python prompt. It also clearly doesn't affect the un/picklability of the instance, so I think the entire check is probably misguided

[issue26036] Unnecessary arguments on smtpd.SMTPServer

Changes by Barry A. Warsaw <ba...@python.org>: -- nosy: +barry ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26036> ___ __

[issue22995] Restrict default pickleability

Barry A. Warsaw added the comment: Your explanation still doesn't entirely make sense to me yet because the crash is happening in what seems to be a Cython implementation class, not a generated class based on a .pyx in some other project using Cython. I tried to search the Cython Trac

[issue22995] Restrict default pickleability

Barry A. Warsaw added the comment: You asked what reductor(4) returns in Python 3.5.0: > /usr/lib/python3.5/copy.py(176)deepcopy() -> rv = reductor(4) (Pdb) reductor(4) (, (,), None, None, None) And this is completely reasonable: (Pdb) p rv (, (,), None, None, None) (Pdb) p rv[0]

[issue22995] Restrict default pickleability

Barry A. Warsaw added the comment: I added some debugging to the if(required) clause. This is interesting: basicsize 16 slotnames 0 basicsize 16 tp_basicsize 80 basicsize 16 tp_basicsize comes in at 16 bytes. tp_dictoffset and tp_weaklistoffset must both be 0, and while slotnames

[issue22995] Restrict default pickleability

Barry A. Warsaw added the comment: On Jan 06, 2016, at 10:13 PM, Serhiy Storchaka wrote: >What return __reduce_ex__(4) for the NameAssignment instance in 3.5.0? I'm not sure yet (it takes some time to set up the right environment to test this), but I do know which TypeError is gett

[issue22995] Restrict default pickleability

Barry A. Warsaw added the comment: I'm reopening this issue because we're starting to see a bunch of regressions in Debian and Ubuntu we think is caused by the changes here. We've definitely started seeing them with 3.5.1, where packages that use Cython built just fine in 3.5.0 but now fail

[issue25833] pyvenv: venvs cannot be moved because activate scripts hard-code paths

Changes by Barry A. Warsaw <ba...@python.org>: -- nosy: +barry ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25833> ___ __

[issue25698] The copy_reg module becomes unexpectedly empty in test_cpickle

Barry A. Warsaw added the comment: On Dec 05, 2015, at 07:03 AM, Benjamin Peterson wrote: >The underlying issue is classic: PyDict_SetItem returns NULL if the stack is >too deep. This confuses import. Thanks for digging into this Benjamin. I'm not able to investigate further atm, but

[issue25698] The copy_reg module becomes unexpectedly empty in test_cpickle

Barry A. Warsaw added the comment: At the problematic breakpoint mentioned in msg255630, copy_reg is nearly empty. (Pdb) sys.modules['copy_reg'] (Pdb) dir(sys.modules['copy_reg']) ['__builtins__', '__doc__', '__file__', '__name__', '__package__'] (Pdb) sys.modules['copy_reg'].__file__ '/build

[issue25698] The copy_reg module becomes unexpectedly empty in test_cpickle

Barry A. Warsaw added the comment: Well, one thing I noticed is that init_stuff() in cPickle.c can leak the copy_reg module object, if any of the subsequent PyObject_GetAttr*() calls fail. They return -1 without decref'ing copyreg. Probably not a horrible leak since it's probably rare

[issue25698] The copy_reg module becomes unexpectedly empty in test_cpickle

Barry A. Warsaw added the comment: On Dec 01, 2015, at 06:26 PM, Barry A. Warsaw wrote: >I'll note one other thing. Doko mentioned that in our build environment, >cPickle is built in, not an extension. Which may be relevant because in a from-hg-head build of Python 2.7, this problem d

[issue25698] The copy_reg module becomes unexpectedly empty in test_cpickle

Barry A. Warsaw added the comment: This just gets weirder. I've narrowed it down to running this command: build-static/python Lib/test/regrtest.py test_doctest test_cpickle fails every time. What's even weirder is that I hacked regrtest to print some useful information before and after each

[issue25698] The copy_reg module becomes unexpectedly empty in test_cpickle

Barry A. Warsaw added the comment: On Dec 01, 2015, at 06:47 PM, Serhiy Storchaka wrote: >Thanks Barry. Running test_cpickle after test_doctest I now can reproduce the >problem in a from-hg-head build of Python 2.7. That's interesting because I can't! (Neither from the 2.7.11rc1 t

[issue25698] The copy_reg module becomes unexpectedly empty in test_cpickle

Barry A. Warsaw added the comment: I added cPickle to Modules/Setup.local and rebuilt from hg. cPickle's a built-in but I still can't reproduce the problem. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i

[issue25601] test_cpickle failure on the ware-gentoo-x86 buildbot

Barry A. Warsaw added the comment: I'm duping this one to issue25698 because while it came later, it has a lot more information. They are clearly the same bug. -- nosy: +barry superseder: -> The copy_reg module becomes unexpectedly empty in test_cpic

[issue25698] test regressions introduced with the fix for #22995

Barry A. Warsaw added the comment: I set a breakpoint where the error occurs. I'm in test_cpickle.py dumps(). Doing cPickle.dumps(arg) in the bp, I get the error. arg is: (Pdb) arg {<__main__.H object at 0x7ff8e2a870d0>: None} (Pdb) type(arg) Look again at the AttributeError:

[issue25698] test regressions introduced with the fix for #22995

Barry A. Warsaw added the comment: This seems entirely reproducible in a local Xenial sbuild using the source packages in https://launchpad.net/~doko/+archive/ubuntu/toolchain/+packages Interestingly, inspection of the built artifacts in the schroot after all is done yields: # find . -name

[issue25698] test regressions introduced with the fix for #22995

Barry A. Warsaw added the comment: But if I just run test_cpickle.py, it succeeds! -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i

[issue25698] test regressions introduced with the fix for #22995

Barry A. Warsaw added the comment: First failure in test run afaict: == ERROR: test_recursive_dict_subclass_and_inst (test.test_cpickle.cStringIOCPicklerFastTests

[issue25698] test regressions introduced with the fix for #22995

Changes by Barry A. Warsaw <ba...@python.org>: -- nosy: +barry ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25698> ___ __

[issue25649] Come up with a good way to handle module aliasing

Barry A. Warsaw added the comment: Another example is the six.moves module, though I haven't looked at its implementation approach. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i

[issue25649] Come up with a good way to handle module aliasing

Changes by Barry A. Warsaw <ba...@python.org>: -- nosy: +barry ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25649> ___ __

[issue25515] Always use os.urandom for generating uuid4s

Barry A. Warsaw added the comment: On Oct 29, 2015, at 10:30 PM, Alex Gaynor wrote: >Right now uuid4 can be implemented one of 3 ways: If you're hacking on the uuid module, keep in mind issue22807 -- nosy: +barry ___ Python tracker &

[issue25008] Deprecate smtpd (based on deprecated asyncore/asynchat): write a new smtp server with asyncio

Barry A. Warsaw added the comment: This has come along pretty well. The project is managed here: https://gitlab.com/python-smtpd-hackers/aiosmtpd and documentation here: http://aiosmtpd.readthedocs.org/en/latest/ -- ___ Python tracker <

[issue23857] Make default HTTPS certificate verification setting configurable

Barry A. Warsaw added the comment: On Oct 14, 2015, at 03:20 PM, Nick Coghlan wrote: >The rationale behind "platform_default" relates to what we put in the default >config file in the RPM. If enable/disable are the only options, then as soon >as the first version

[issue23857] Make default HTTPS certificate verification setting configurable

Barry A. Warsaw added the comment: Re: platform_default - I'm not sure that's a good idea. It hides what's actually happening in some hard to discover place (the code). Probably EIBTI and just go with 'enable' and 'disable'. -- ___ Python tracker

[issue21159] configparser.InterpolationMissingOptionError is not very intuitive

Barry A. Warsaw added the comment: The failure is in the configglue test suite, but apparently also kazan and qutebrowser are also affected by this change. In the Launchpad bug there's a link to a librarian build log result. The problem is that doing the .get() requires that subclasses

[issue21159] configparser.InterpolationMissingOptionError is not very intuitive

Barry A. Warsaw added the comment: Reopening because we're starting to see regressions caused by the fix for this bug, e.g.: https://bugs.launchpad.net/configglue/+bug/1504288 -- keywords: +3.4regression, 3.5regression -patch status: closed -> o

[issue21159] configparser.InterpolationMissingOptionError is not very intuitive

Changes by Barry A. Warsaw <ba...@python.org>: -- nosy: +barry ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue21159> ___ __

[issue25328] ValueError in smtpd.py __init__() is not raised

Barry A. Warsaw added the comment: On Oct 08, 2015, at 08:44 PM, Mauro S. M. Rodrigues wrote: >Python 3.5.0+ (3.5:1e99ba6b7c98, Oct 8 2015, 17:12:06) >[GCC 4.8.4] on linux >Type "help", "copyright", "credits" or "license" for more inf

[issue25328] ValueError in smtpd.py __init__() is not raised

New submission from Barry A. Warsaw: In Python 3.5, SMTPChannel.__init__() ensures that enable_SMTPUTF8 and decode_data arguments are not both true. This even seems to be tested in test_smtpd.py. But it's clearly bogus because the exception is never raised! It just creates and throws away

[issue25008] Deprecate smtpd (based on deprecated asyncore/asynchat): write a new smtp server with asyncio

Barry A. Warsaw added the comment: I'm liking RDM's port of smtpd.py. I've done some clean ups, bug fixes, and added some debugging. See this branch over on gitlab: https://gitlab.com/python-smtpd-hackers/aiosmtpd/tree/issue25508 Try `python3 server.py` then run client.py in another

[issue25296] Simple End-of-life guide covering all unsupported versions

Changes by Barry A. Warsaw <ba...@python.org>: -- nosy: +barry ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25296> ___ __

[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 and let packages

[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 <

[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 version

[issue25154] Drop the pyvenv script

Changes by Barry A. Warsaw <ba...@python.org>: -- nosy: +barry ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25154> ___ __

[issue25154] Drop the pyvenv script

Changes by Barry A. Warsaw <ba...@python.org>: -- nosy: +doko ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25154> ___ __

[issue25061] Add native enum support for argparse

Changes by Barry A. Warsaw <ba...@python.org>: -- nosy: +barry ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25061> ___ __

[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 >of the other ones (b, r, and u) do. I think

[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 ha

[issue25014] Add contextlib.itercm()

Changes by Barry A. Warsaw <ba...@python.org>: -- nosy: +barry ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25014> ___ __

[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 implementatio

[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

[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 fallback to $HOME

[issue24965] Implement PEP 498: Literal String Formatting

Changes by Barry A. Warsaw ba...@python.org: -- nosy: +barry ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24965 ___ ___ Python-bugs-list mailing

[issue24941] classproperty

Changes by Barry A. Warsaw ba...@python.org: -- nosy: +barry ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24941 ___ ___ Python-bugs-list mailing

[issue15014] smtplib: add support for arbitrary auth methods

Changes by Barry A. Warsaw ba...@python.org: -- assignee: - barry status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15014

[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.python.org

[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 added this because

[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

[issue15014] smtplib: add support for arbitrary auth methods

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

[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

[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 rep...@bugs.python.org http://bugs.python.org/issue22508

[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, this response

[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 response bytes

[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 responses

[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 server

[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 rep...@bugs.python.org http://bugs.python.org/issue19995

[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 rep...@bugs.python.org http://bugs.python.org/issue19995 ___ ___ Python-bugs-list

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

Changes by Barry A. Warsaw ba...@python.org: -- nosy: +barry ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24454 ___ ___ Python-bugs-list mailing

[issue24351] string.Template documentation incorrectly references identifiers

Changes by Barry A. Warsaw ba...@python.org: -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24351

[issue24412] setUpClass equivalent for addCleanup

Changes by Barry A. Warsaw ba...@python.org: -- nosy: +barry ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24412 ___ ___ Python-bugs-list mailing

[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 placeholder matching a mapping key

[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 rep...@bugs.python.org http://bugs.python.org/issue24168

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

Changes by Barry A. Warsaw ba...@python.org: -- nosy: +barry ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24168 ___ ___ Python-bugs-list mailing

[issue19699] Update zipimport for PEP 451

Changes by Barry A. Warsaw ba...@python.org: -- nosy: +barry ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19699 ___ ___ Python-bugs-list mailing

[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 rep...@bugs.python.org http://bugs.python.org/issue23968

[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 translators. $foo

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

Changes by Barry A. Warsaw ba...@python.org: -- nosy: +barry ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24305 ___ ___ Python-bugs-list mailing

[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 %d with %x. Using

[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 rep...@bugs.python.org http://bugs.python.org/issue6598

[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 documented

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

Changes by Barry A. Warsaw ba...@python.org: -- nosy: +barry ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24077 ___ ___ Python-bugs-list mailing

[issue23058] argparse silently ignores arguments

Changes by Barry A. Warsaw ba...@python.org: -- nosy: +barry ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23058 ___ ___ Python-bugs-list mailing

[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 ambiguous. Since

[issue23699] Add a macro to ease writing rich comparisons

Changes by Barry A. Warsaw ba...@python.org: -- nosy: +barry ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23699 ___ ___ Python-bugs-list mailing

[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 been intentional, because

[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 it's relied

[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 is done as part of *submodule loading

[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 rep...@bugs.python.org http://bugs.python.org/issue24029

[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 rep...@bugs.python.org http://bugs.python.org/issue24029

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

Changes by Barry A. Warsaw ba...@python.org: -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24029

[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 rep...@bugs.python.org http://bugs.python.org/issue18128

[issue23910] C implementation of namedtuple (WIP)

Changes by Barry A. Warsaw ba...@python.org: -- nosy: +barry ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23910 ___ ___ Python-bugs-list mailing

[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 ba...@python.org: -- nosy: +barry ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23842 ___ ___ Python-bugs-list mailing

<    4   5   6   7   8   9   10   11   12   13   >