[issue1515] deepcopy doesn't copy instance methods

Barry A. Warsaw added the comment: Guido - agreed! Versions updated. -- versions: +Python 3.2 -Python 2.6 ___ Python tracker <http://bugs.python.org/issue1

[issue6895] locale._parse_localename fails when localename does not contain encoding information

Changes by Barry A. Warsaw : -- versions: +Python 2.6, Python 2.7, Python 3.2 ___ Python tracker <http://bugs.python.org/issue6895> ___ ___ Python-bugs-list mailin

[issue7513] many source files contaminated with form feed (\f) characters

Barry A. Warsaw added the comment: Emacs navigation command forward-page and backward-page. Python treats them as whitespace, so what's the problem? :) -- priority: -> low resolution: -> wont fix status: open -> closed ___ Python

[issue7490] IGNORE_EXCEPTION_DETAIL should ignore the module name

Barry A. Warsaw added the comment: @Lennart: yes, I do think you should add a test for that case. I haven't yet decided whether this should go into 2.6. -- nosy: +barry ___ Python tracker <http://bugs.python.org/i

[issue1818] Add named tuple reader to CSV module

Barry A. Warsaw added the comment: I think it would be useful to have. ___ Python tracker <http://bugs.python.org/issue1818> ___ ___ Python-bugs-list mailing list Unsub

[issue4773] HTTPMessage not documented and has inconsistent API across 2.6/3.0

Barry A. Warsaw added the comment: I propose that you only document the getitem header access API. I.e. the thing that info() gives you can be used to access the message headers via message['content-type']. That's an API common to both rfc822.Messages (the ultimat

[issue1974] email.MIMEText.MIMEText.as_string incorrectly folding long subject header

Barry A. Warsaw added the comment: So astoundingly, this change has deep implications. The upshot is that it's difficult to fix this so that headers look nice for e.g. Subject headers, but so that splitting and wrapping work as expected for e.g. machine readability of Received headers.

[issue1645148] MIME renderer: wrong header line break with long subject?

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

[issue5610] email feedparser.py CRLFLF bug: $ vs \Z

Changes by Barry A. Warsaw : -- assignee: -> barry versions: +Python 3.1 ___ Python tracker <http://bugs.python.org/issue5610> ___ ___ Python-bugs-list mai

[issue5610] email feedparser.py CRLFLF bug: $ vs \Z

Barry A. Warsaw added the comment: I think this is a good idea. Does the existing test suite still pass with this change? For a long time, email's philosophy was to use native line endings and never expected mixed eol, and it definitely never expected mixed line endings, so we'

[issue2703] SimpleXMLRPCDispatcher.__init__ is not python2.4-backward-compatible

Barry A. Warsaw added the comment: I'm -0, but if the tests pass and Matthias wants to commit this to 2.6 and 2.7, it's fine with me. -- assignee: -> doko nosy: +barry resolution: -> accepted versions: +Python 2.7 -Python 2.5 __

[issue5724] 2.6.2c1 fails to pass test_cmath on Solaris10

Barry A. Warsaw added the comment: I'll mark this as a release blocker for 2.6.2 for now, until Mark weighs in. -- priority: -> release blocker ___ Python tracker <http://bugs.python.or

[issue5724] 2.6.2c1 fails to pass test_cmath on Solaris10

Barry A. Warsaw added the comment: We'll omit this for 2.6.2. Mark, please feel free to apply it once 2.6.2 is released so that it makes it into 2.6.3. -- priority: release blocker -> high ___ Python tracker <http://bugs.python.or

[issue5724] 2.6.2c1 fails to pass test_cmath on Solaris10

Barry A. Warsaw added the comment: Accepted for 2.6.3. -- resolution: -> accepted ___ Python tracker <http://bugs.python.org/issue5724> ___ ___ Python-

[issue5728] Support telling TestResult objects a test run has finished

Barry A. Warsaw added the comment: The patch looks fine to me, except that it's missing documentation updates. The feature and names are fine too. -- nosy: +barry ___ Python tracker <http://bugs.python.org/i

[issue5728] Support telling TestResult objects a test run has finished

Barry A. Warsaw added the comment: On Apr 15, 2009, at 7:43 PM, Robert Collins wrote: > Robert Collins added the comment: > > On Wed, 2009-04-15 at 23:19 +0000, Barry A. Warsaw wrote: >> Barry A. Warsaw added the comment: >> >> The patch looks fine to m

[issue5903] strftime fails in non UTF-8 locale

New submission from Barry Alan Scott : On Mac OS X 10.5 $ LC_ALL=ru_RU.koi8-r python3.0 -c 'import time;print( time.strftime("%A"))' Traceback (most recent call last): File "", line 1, in UnicodeDecodeError: 'utf8' codec can't decode bytes in posi

[issue5904] strftime docs do not explain locale affect on result string

New submission from Barry Alan Scott : The result of time.strftime seems to be in the locale encoding but this is not pointed out in the documentation. Ideally an example like this would be in the docs to show how to deal with strftime output: import locale import time locale_encoded_time

[issue3244] multipart/form-data encoding

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

[issue5970] sys.exc_info leaks into a generator

Barry A. Warsaw added the comment: I agree with Antoine. -- versions: -Python 2.6 ___ Python tracker <http://bugs.python.org/issue5970> ___ ___ Python-bug

[issue6177] unittest.main testRunner default argument changed from None

Barry A. Warsaw added the comment: Feel free to apply this to 2.6. -- nosy: +barry resolution: -> accepted ___ Python tracker <http://bugs.python.org/iss

[issue4661] email.parser: impossible to read messages encoded in a different encoding

Barry A. Warsaw added the comment: dato: We've started some branches that try to address this, by exposing both a read-a-buncha-bytes interface and a read-a-string interface. rdm: As it turns out, yes. There are use cases for reading a string containing only ascii bytes. In general, th

[issue2622] Import errors in email.message.py

Barry A. Warsaw added the comment: The patch looks pretty good, except that you should not change test_email.py. It specifically tests the old names, while test_email_renamed.py tests the new names. There's no point in fixing Python 2.5 since there won't be another maintenance relea

[issue2622] Import errors in email.message.py

Barry A. Warsaw added the comment: Looks good; feel free to commit. -- versions: -Python 2.5 ___ Python tracker <http://bugs.python.org/issue2622> ___ ___ Pytho

[issue8739] Update to smtpd.py to RFC 5321

Changes by Barry A. Warsaw : -- versions: -Python 3.1 ___ Python tracker <http://bugs.python.org/issue8739> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue2456] Make sysmodule.c compatible with Bazaar

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

[issue8727] test_import failure

Barry A. Warsaw added the comment: I cannot reproduce this on Ubuntu 10.04 with current py3k (r81268), even using the boiled down example given by Antoine. What platform are you on? -- ___ Python tracker <http://bugs.python.org/issue8

[issue8727] test_import failure

Barry A. Warsaw added the comment: Thanks, Antoine filled me in on IRC just before my 'net connection went down for many hours. The good news is that I have a fix for this and will commit it in a little while. -- ___ Python tracker

[issue8727] test_import failure

Barry A. Warsaw added the comment: r81290 -- assignee: brett.cannon -> barry resolution: -> fixed status: open -> closed ___ Python tracker <http://bugs.python.o

[issue8324] add a distutils test command

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

[issue9193] Versioned .so files

New submission from Barry A. Warsaw : As described in the thread started here: http://mail.python.org/pipermail/python-dev/2010-June/100998.html this bug requests that a new configure option called --with-so-abi-tag be added to Python 3.2 to support sharing of .so files for different versions

[issue9193] Versioned .so files

Changes by Barry A. Warsaw : -- stage: -> patch review ___ Python tracker <http://bugs.python.org/issue9193> ___ ___ Python-bugs-list mailing list Unsubscri

[issue9193] Versioned .so files

Barry A. Warsaw added the comment: Attaching patch from live branch living here: https://code.edge.launchpad.net/~barry/python/sovers -- Added file: http://bugs.python.org/file17895/preview.diff ___ Python tracker <http://bugs.python.org/issue9

[issue9193] Versioned .so files

Barry A. Warsaw added the comment: Actually, the changes to distutils are not strictly necessary for PEP 3149 implementation (what the PEP-in-progress will be numbered). Once PEP 384 is implemented, it might be useful, but OTOH there might be a better way to support that. In any case

[issue9193] Versioned .so files

Barry A. Warsaw added the comment: Updated patch. -- Added file: http://bugs.python.org/file18125/diff.txt ___ Python tracker <http://bugs.python.org/issue9

[issue9193] Versioned .so files

Barry A. Warsaw added the comment: I'd love it if Windows was also supported, but right now I don't have the cycles to make and test the changes, or the expertise to understand any related Windows issues. I've mentioned this in PEP 3149, and I'd happily accept code

[issue9264] trace.py documentation is incomplete

Barry A. Warsaw added the comment: If the changes are to the documentation only, you've confirmed that the docs build in 2.6.6, and you get the changes in before 2.6.6rc1, then you can go ahead and commit them. I don't need to review them too closely - I trust you - but if you wan

[issue9438] Clarify __debug__ restrictions

New submission from Barry A. Warsaw : On http://docs.python.org/library/constants.html?highlight=__debug__#__debug__ * Be more explicit that assigments to None and __debug__ are illegal even when used as attributes. IOW it's not just assignment to the built-in names that are il

[issue9264] trace.py documentation is incomplete

Barry A. Warsaw added the comment: You have about 5 hours as of this writing to apply the doc patch for Python 2.6.6 rc1 and then it will be too late to get it into Python 2.6.6 (though I might make an exception for doc-only patches like this, for post rc1). While I haven't built the do

[issue9264] trace.py documentation is incomplete

Changes by Barry A. Warsaw : -- priority: release blocker -> high ___ Python tracker <http://bugs.python.org/issue9264> ___ ___ Python-bugs-list mailing list Un

[issue2986] difflib.SequenceMatcher not matching long sequences

Barry A. Warsaw added the comment: Georg committed this patch to the 2.6 tree, and besides, this is doesn't seem like a blocking issue, so I'm kicking 2.6 off the list and knocking the priority down. -- priority: release blocker -> high versions:

[issue9061] cgi.escape Can Lead To XSS Vulnerabilities

Barry A. Warsaw added the comment: Unless someone can upload a specific patch to review in the next couple of hours, I'm going to reduce the priority for 2.6.6rc1. -- nosy: +barry ___ Python tracker <http://bugs.python.org/i

[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled

Barry A. Warsaw added the comment: Hi Ezio, what's the status on this issue for 2.6.6rc1? -- ___ Python tracker <http://bugs.python.org/issue7092> ___ ___

[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled

Barry A. Warsaw added the comment: I am removing this as a release blocker given all of Ezio's great work to get the test suite clean with -3. I will leave it up to him to actually close the issue once the work is complete. It no longer needs to block 2.6.6. -- priority: re

[issue8433] buildbot: test_curses failure, getmouse() returned ERR

Barry A. Warsaw added the comment: This also affects 2.6 but I've only been able to verify it on Debian squeeze and Ubuntu maverick, both of which are unreleased. On Ubuntu lucid (stable), this error does not occur. I'm testing Debian stable now... -- no

[issue8433] buildbot: test_curses failure, getmouse() returned ERR

Changes by Barry A. Warsaw : -- versions: +Python 2.6 ___ Python tracker <http://bugs.python.org/issue8433> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue8433] buildbot: test_curses failure, getmouse() returned ERR

Barry A. Warsaw added the comment: Confirmed on Ubuntu: Lucid, libncurses5 5.7+20090803-2ubuntu3 passes Maverick, libncurses5 5.7+20100626-0ubuntu1 fails -- ___ Python tracker <http://bugs.python.org/issue8

[issue8433] buildbot: test_curses failure, getmouse() returned ERR

Barry A. Warsaw added the comment: Confirmed on Debian squeeze, ncurses 5.7+20100313-2 failed lenny, ncurses 5.7+20081213-1 succeeds So clearly something about the curses module is not compatible with the newer versions of ncurses. -- ___ Python

[issue5798] test_asynchat fails on Mac OSX

Barry A. Warsaw added the comment: Thanks Mark, go ahead and apply this, then close this issue. -- resolution: -> accepted ___ Python tracker <http://bugs.python.org/iss

[issue5713] smtplib gets out of sync if server returns a 421 status

Barry A. Warsaw added the comment: The latest relevant RFC is 5321: http://www.faqs.org/rfcs/rfc5321.html smtplib should be reviewed for compliance with this updated spec. -- ___ Python tracker <http://bugs.python.org/issue5

[issue7567] Messed up terminal after calling curses.initscr() twice.

Barry A. Warsaw added the comment: Doko asks in IRC to apply this for 2.6.6. Approved. -- nosy: +barry status: pending -> open ___ Python tracker <http://bugs.python.org/iss

[issue28833] cross compilation of third-party extension modules

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

[issue28937] str.split(): remove empty strings when sep is not None

New submission from Barry A. Warsaw: This has finally bugged me enough to file an issue, although I wouldn't be able to use it until Python 3.7. There's a subtle but documented difference in str.split() when sep=None: >>> help(''.split) Help on built-in function

[issue28937] str.split(): remove empty strings when sep is not None

Barry A. Warsaw added the comment: On Dec 11, 2016, at 03:32 PM, Serhiy Storchaka wrote: >Current behavior is consistent with str.count(): > >len(string.split(sep)) == string.count(sep) + 1 > >and re.split(): > >re.split(re.escape(sep), string) == string.split(sep)

[issue28937] str.split(): remove empty strings when sep is not None

Barry A. Warsaw added the comment: On Dec 11, 2016, at 03:57 PM, Serhiy Storchaka wrote: >I meant adding boolean argument that changes the behavior when sep is None, >not when it is not None. Ah, I understand now, thanks. However, I'm not sure that addresses my particular use

[issue28937] str.split(): remove empty strings when sep is not None

Barry A. Warsaw added the comment: I really appreciate all the feedback. Here are some thoughts. I'm well aware of the filter(), re, and other options, and certainly those can be made to work, but they're non-obvious. The reason I suggested an enhancement to str.split() is because

[issue28937] str.split(): remove empty strings when sep is not None

Barry A. Warsaw added the comment: On Dec 12, 2016, at 04:16 PM, Guido van Rossum wrote: >So the proposal would be: prune=False -> empty strings stay, prune=True, >empty strings are dropped, prune=None (default) use True if sep is None, >False otherwise. Right? Yep! >

[issue28180] sys.getfilesystemencoding() should default to utf-8

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

[issue28180] sys.getfilesystemencoding() should default to utf-8

Barry A. Warsaw added the comment: On Jan 05, 2017, at 11:11 AM, STINNER Victor wrote: >I'm sure that many Linux, UNIX and BSD systems don't have the "C.UTF-8" >locale. For example, HP-UX has "C.utf8" which is not exactly "C.UTF-8". > >I'

[issue29307] ModuleNotFoundError when using literal string interpolation with invalid format specifier

Barry A. Warsaw added the comment: On Jan 18, 2017, at 10:56 AM, Jeroen Van Goey wrote: >sudo add-apt-repository ppa:jonathonf/python-3.6 >sudo apt-get update >sudo apt-get install python3.6 > >I made a string, using the new literal string interpolation, but I supplied >

[issue1294959] Problems with /usr/lib64 builds.

Barry A. Warsaw added the comment: On Jan 18, 2017, at 03:57 PM, Matthias Klose wrote: >I don't think we need a PEP for this Correct. Generally we don't need PEPs for build system changes. -- ___ Python tracker <http:/

[issue29514] Add a test case that prevents magic number changes in minor releases

Barry A. Warsaw added the comment: On Feb 10, 2017, at 05:46 PM, Nick Coghlan wrote: >Note that Fedora doesn't even rebuild all the extension modules when bumping >CPython to a new maintenance release, let alone rebuilding and re-releasing >all the pure Python ones. (RPM suppo

[issue29324] test_aead_aes_gcm fails on Kernel 4.9

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

[issue29324] test_aead_aes_gcm fails on Kernel 4.9

Barry A. Warsaw added the comment: Confirmed that test_socket_aead_kernel49.patch fixes the problem for Ubuntu 17.04. It'll probably fix it for Debian Stretch too give its kernel version number, but I haven't tested that yet. -- ___ Pyth

[issue22807] uuid.uuid1() should use uuid_generate_time_safe() if available

Changes by Barry A. Warsaw : -- versions: +Python 3.3, Python 3.6, Python 3.7 ___ Python tracker <http://bugs.python.org/issue22807> ___ ___ Python-bugs-list m

[issue29514] Add a test case that prevents magic number changes in minor releases

Barry A. Warsaw added the comment: On Feb 12, 2017, at 05:42 PM, Brett Cannon wrote: >That comment is poorly worded. Pretty sure at one time it was accurately worded, but things have changed since PEP 3147 so the comment could use an upd

[issue29546] A more helpful ImportError message

New submission from Barry A. Warsaw: I haven't really thought about this deeply but I've observed that there are lots of cases where a user will report getting an ImportError trying to import a name from a module, where it turns out that the problem is that the module is comi

[issue22807] uuid.uuid1() should use uuid_generate_time_safe() if available

Changes by Barry A. Warsaw : -- assignee: -> barry ___ Python tracker <http://bugs.python.org/issue22807> ___ ___ Python-bugs-list mailing list Unsubscrib

[issue22807] uuid.uuid1() should use uuid_generate_time_safe() if available

Barry A. Warsaw added the comment: I changed my mind on whether this should affect older versions of Python. I have a branch which adds an UUID.is_safe attribute that relays the platform information about whether the UUID was generated safely or not, if available. It's an enum

[issue22807] uuid.uuid1() should use uuid_generate_time_safe() if available

Changes by Barry A. Warsaw : -- pull_requests: +98 ___ Python tracker <http://bugs.python.org/issue22807> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue29582] Add Python coverage make target(s)

Barry A. Warsaw added the comment: +1 Probably ought to reconfigure .travis.yml to use the new targets too, if possible. -- ___ Python tracker <http://bugs.python.org/issue29

[issue22807] uuid.uuid1() should use uuid_generate_time_safe() if available

Barry A. Warsaw added the comment: New changeset 8c130d7f8114158f5b94749032ec0c17dba96f83 by GitHub in branch 'master': bpo-22807: Expose platform UUID generation safety information. (#138) https://github.com/python/cpython/commit/8c130d7f8114158f5b94749032ec0c

[issue22807] uuid.uuid1() should use uuid_generate_time_safe() if available

Changes by Barry A. Warsaw : -- resolution: -> fixed ___ Python tracker <http://bugs.python.org/issue22807> ___ ___ Python-bugs-list mailing list Unsubscrib

[issue22807] uuid.uuid1() should use uuid_generate_time_safe() if available

Changes by Barry A. Warsaw : -- stage: -> resolved status: open -> closed ___ Python tracker <http://bugs.python.org/issue22807> ___ ___ Python-bugs-list

[issue29601] Need reST markup for enum types

New submission from Barry A. Warsaw: Over in https://github.com/python/cpython/pull/138 I noticed that we don't currently have markup for enum types. While class:: is technically still correct, it's not helpful because the html documentation should render this as `Enum SafeUUID`

[issue29601] Need reST markup for enum types

Barry A. Warsaw added the comment: On Feb 20, 2017, at 12:03 AM, Fred L. Drake, Jr. wrote: >Is there some special treatment you think should be given to specific enum >values as well? The only thing I thought about was optionally provide the enum item's value, when that's usef

[issue22807] uuid.uuid1() should use uuid_generate_time_safe() if available

Barry A. Warsaw added the comment: On Feb 20, 2017, at 02:21 PM, STINNER Victor wrote: >What am I supposed to do with an UUID with safe=False? Should I loop on the >function until I get safe==True? It would be an application dependent response. It might be that you would check some

[issue22807] uuid.uuid1() should use uuid_generate_time_safe() if available

Changes by Barry A. Warsaw : -- keywords: -security_issue ___ Python tracker <http://bugs.python.org/issue22807> ___ ___ Python-bugs-list mailing list Unsub

[issue22807] uuid.uuid1() should use uuid_generate_time_safe() if available

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

[issue22807] uuid.uuid1() should use uuid_generate_time_safe() if available

Barry A. Warsaw added the comment: Oh, and because the fix is an API change, I don't believe it should be applied to earlier versions. So I think adding the API in 3.7 is all the fix needed here. -- ___ Python tracker <http://bugs.py

[issue22807] uuid.uuid1() should use uuid_generate_time_safe() if available

Barry A. Warsaw added the comment: On Feb 20, 2017, at 03:45 PM, STINNER Victor wrote: >Can't we consider that UUID4 is always safe? It's not a guarantee made by the underlying platform, so I chose to use the default SafeUUID.unknow

[issue29546] A more helpful ImportError message

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

[issue15657] Error in Python 3 docs for PyMethodDef

Barry A. Warsaw added the comment: I think this bug has been fixed. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <http://bugs.python.or

[issue25008] Deprecate smtpd (based on deprecated asyncore/asynchat)

Barry A. Warsaw added the comment: aiosmtpd is coming along nicely: http://aiosmtpd.readthedocs.io/en/latest/ We'll soon have a 1.0 release. Still, I don't think it's worth pulling this into the stdlib. But we could silently deprecate it and point to aiosmt

[issue29642] Why does unittest.TestLoader.discover still rely on existence of __init__.py files?

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

[issue25008] Deprecate smtpd (based on deprecated asyncore/asynchat)

Changes by Barry A. Warsaw : -- pull_requests: +246 ___ Python tracker <http://bugs.python.org/issue25008> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue25008] Deprecate smtpd (based on deprecated asyncore/asynchat)

Changes by Barry A. Warsaw : -- pull_requests: +248 ___ Python tracker <http://bugs.python.org/issue25008> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue25008] Deprecate smtpd (based on deprecated asyncore/asynchat)

Changes by Barry A. Warsaw : -- pull_requests: +249 ___ Python tracker <http://bugs.python.org/issue25008> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue25008] Deprecate smtpd (based on deprecated asyncore/asynchat)

Changes by Barry A. Warsaw : -- pull_requests: +250 ___ Python tracker <http://bugs.python.org/issue25008> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue25008] Deprecate smtpd (based on deprecated asyncore/asynchat)

Changes by Barry A. Warsaw : -- resolution: -> fixed stage: needs patch -> resolved status: open -> closed ___ Python tracker <http://bugs.python.or

[issue27143] python 3.5 conflict with Mailman, ebtables and firewalld

Barry A. Warsaw added the comment: On May 28, 2016, at 12:26 AM, Rubén Rivero Capriles wrote: >While: Installing mailman. Which version of Mailman? Mailman 2.1 is not compatible with Python 3, Mailman 3.0 is only compatible with Python 3.4, and Mailman 3.1 (not yet released) will

[issue27143] python 3.5 conflict with Mailman, ebtables and firewalld

Barry A. Warsaw added the comment: This is definitely not the right place to discuss this. Please use the Mailman 3 users mailing list or the Mailman Developers mailing list. https://lists.mailman3.org/archives/list/mailman-us...@mailman3.org/ https://mail.python.org/mailman/listinfo/mailman

[issue26632] @public - an __all__ decorator

Barry A. Warsaw added the comment: I'm going to go ahead and close this issue. There wasn't much positive reception to @public in the Pycon 2016 language summit (where I presented it as a lightning talk). https://gitlab.com/warsaw/public Some of the other ideas for changes to

[issue27187] Relax __all__ location requirement in PEP 8

New submission from Barry A. Warsaw: PEP 8 says: Put any relevant __all__ specification after the imports. I don't remember why we wanted __all__ to go after imports. I think we should relax that since other dunders can go before imports. See related PYCQA issue: https://github.com/

[issue27187] Relax __all__ location requirement in PEP 8

Changes by Barry A. Warsaw : -- assignee: -> docs@python components: +Documentation nosy: +docs@python ___ Python tracker <http://bugs.python.org/issu

[issue26632] @public - an __all__ decorator

Barry A. Warsaw added the comment: On Jun 04, 2016, at 07:47 PM, Zachary Ware wrote: >So, +1 anyway. I think this would be rather worthwhile, especially in the >stdlib. Thanks! I still like it and plan on continuing to use it in my code. I would recommend you playing with the third

[issue27187] Relax __all__ location requirement in PEP 8

Barry A. Warsaw added the comment: Thanks for the patch! -- ___ Python tracker <http://bugs.python.org/issue27187> ___ ___ Python-bugs-list mailing list Unsub

[issue27187] Relax __all__ location requirement in PEP 8

Barry A. Warsaw added the comment: Thanks Ian. I'm going to apply that, but rephrase it a bit. -- ___ Python tracker <http://bugs.python.org/issue27187> ___ ___

[issue27066] SystemError if custom opener returns -1

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

[issue10839] email module should not allow some header field repetitions

Barry A. Warsaw added the comment: On Jun 11, 2016, at 09:25 PM, Raymond Hettinger wrote: >I think we should consider this as an API design bug and backport the fix. No, it's deliberate, required, and expected in some cases as RDM explains. Certainly for compat32 policy, this can&

<    19   20   21   22   23   24   25   26   27   28   >