[issue42173] Drop Solaris support
brett added the comment: Between SmartOS, Illumos, and mainline Solaris, there is ample interest and support for ensuring that SunOS derivatives remain 1st class python platforms. Platform genocide is both unnecessary and unwarranted. -- nosy: +brett3 ___ Python tracker <https://bugs.python.org/issue42173> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue31370] Remove support for threads-less builds
Brett Cannon added the comment: This has unfortunately turned out to be a blocker on getting WASI support as there's not direct threading support in WebAssembly. -- nosy: +brett.cannon ___ Python tracker <https://bugs.python.org/issue31370> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue31370] Remove support for threads-less builds
Brett Cannon added the comment: > https://web.dev/webassembly-threads/ suggests otherwise. It actually doesn't as that post isn't for WASI, it's for WASM in the browser (I chose my acronyms carefully 😉). WASI is like POSIX for WebAssembly, so it's meant for desktop usage and thus no browser or JS engine is involved to provide web workers. -- ___ Python tracker <https://bugs.python.org/issue31370> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40059] Provide a toml module in the standard library
Brett Cannon added the comment: > I just noticed that tomli has dropped support for Python 3.6. That's a road > block for general adoption of the package in the Python ecosystem. It's already in pip, so I think it's already generally adopted 😉. https://github.com/pypa/pip/tree/main/src/pip/_vendor/tomli > Is my understanding correct that this issue is blocked on SC guidance? Not officially, no. But I'm personally not going to bring it forward right now. If someone else wants to formulate a complete proposal for the SC on this then they are definitely welcome to! You will need to address where the code is coming from, why that code should be used, what's the API, etc. The only reason the SC is mentioned here is there will be a discussion about how to maintain the stdlib, but it simply hasn't happened yet. You don't have to wait for it and asking for a TOML module might actually force the issue. > Is there anything we could do in advance of SC guidance that would be > productive? Nope, someone eventually has to have the time to make the proposal and manage the deluge of comments. > Is there a good place to follow along or be notified of SC thoughts? https://github.com/python/steering-council as you already pointed out through the issues and monthly summaries. Otherwise you just need to open an issue and ask. 😃 -- ___ Python tracker <https://bugs.python.org/issue40059> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue31370] Remove support for threads-less builds
Brett Cannon added the comment: I am not opening a new discussion; this is just recording this fact here as it has come up in other places on the internet. -- ___ Python tracker <https://bugs.python.org/issue31370> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40059] Provide a toml module in the standard library
Brett Cannon added the comment: I opened https://github.com/python/steering-council/issues/92 for the SC to discuss stdlib additions in case I am not re-elected. -- ___ Python tracker <https://bugs.python.org/issue40059> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46044] Update distutils documentation to say PyPI only accepts tar.gz and zip.
Brett Cannon added the comment: Nah, I don't think setuptools cares about this doc update. -- resolution: -> fixed stage: commit review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue46044> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46044] Update distutils documentation to say PyPI only accepts tar.gz and zip.
Brett Cannon added the comment: New changeset 8202a7e3dd55d551906390742fc748d0747256b8 by Miss Islington (bot) in branch '3.9': [3.9] bpo-46044: Annotate deprecated sdists formats (GH-30043) (GH-30155) https://github.com/python/cpython/commit/8202a7e3dd55d551906390742fc748d0747256b8 -- ___ Python tracker <https://bugs.python.org/issue46044> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46044] Update distutils documentation to say PyPI only accepts tar.gz and zip.
Brett Cannon added the comment: New changeset dbd1dc23f60a6883adf1d18e660f163fa76b8ba9 by Miss Islington (bot) in branch '3.10': [3.10] bpo-46044: Annotate deprecated sdists formats (GH-30043) (#30154) https://github.com/python/cpython/commit/dbd1dc23f60a6883adf1d18e660f163fa76b8ba9 -- ___ Python tracker <https://bugs.python.org/issue46044> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46241] importlib.utils.find_spec() has issues with "tests" folder
Brett Cannon added the comment: This is working as intended. Because you don't have a `__init__.py` file in your `tests` directory, Python considers it a potential namespace package. As such, Python keeps searching for a "normal" package that defines `__init__.py` for the same package name. Since Astroid has one and seemingly has it on `sys.path` in such a way as to get discovered, it gets selected as the package to use for the name `test`. If you add a `tests/__init__.py` file then your issue will go away. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue46241> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46360] Inconsistent import behavior for (unusual) submodules
Brett Cannon added the comment: So which inconsistency do you want to change because you listed three and this is only one issue. 😉 I'm going to assume the "even though sys.modules has `None`" case, which I think is an oversight and should probably get fixed, but I also don't know what promises the language spec makes around this. As for the other two, you can open separate issues if you want to discuss them, but I double-check what the language spec says as I am tempted to say both are fine (and specifically in the latter case that's on you to have not messed up and left the attribute off). -- ___ Python tracker <https://bugs.python.org/issue46360> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20281] [doc] time.strftime %z format specifier is the same as %Z
Brett Cannon added the comment: New changeset 305588c67cdede4ef127ada90c1557bc1ef7c200 by Hugo van Kemenade in branch 'main': bpo-20281, bpo-29964: update datetime docs to refer %z and %Z to a pre-existing footnote (GH-30354) https://github.com/python/cpython/commit/305588c67cdede4ef127ada90c1557bc1ef7c200 -- nosy: +brett.cannon ___ Python tracker <https://bugs.python.org/issue20281> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29964] [doc] %z directive has no effect on the output of time.strptime
Brett Cannon added the comment: New changeset 305588c67cdede4ef127ada90c1557bc1ef7c200 by Hugo van Kemenade in branch 'main': bpo-20281, bpo-29964: update datetime docs to refer %z and %Z to a pre-existing footnote (GH-30354) https://github.com/python/cpython/commit/305588c67cdede4ef127ada90c1557bc1ef7c200 -- ___ Python tracker <https://bugs.python.org/issue29964> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39602] importlib: lazy loading can result in reimporting a submodule
Change by Brett Cannon : -- priority: normal -> low ___ Python tracker <https://bugs.python.org/issue39602> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46454] '0 -> /dev/null' is lost
Change by Brett Randall : -- nosy: +javabrett ___ Python tracker <https://bugs.python.org/issue46454> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46454] '0 -> /dev/null' is lost
Brett Randall added the comment: For the possible benefit of future readers of this issue, the sequence and behaviour here which may cause confusion: - say stdin is closed, perhaps along with stdout and stderr via a call to os.closerange(0, 3) or otherwise - os.open() is called and creates a new fd=0, which will always be 0 since 0 is now available and lowest. Per PEP 446 this fd is non-inheritable. - a call to os.dup2(fd, 0) is made but is a noop, since fd=0 and dup2() ignores copy-to-same. This behaviour may go unnoticed - it may not be noticed that the new fd=0 (it should always be this), or that dup2() has this noop behaviour. Per PEP 446, dup2() still creates inheritable by-default, so the caller may expect that they have just assigned an inheritable fd to stdin, instead of a noop. - subprocess() is called and the subprocess does not have stdin/0 fd assigned, since it was not inheritable. It seems the main way to avoid this is to os.open() the replacement fd _before_ closing stdin/0, in which case it will receive an fd >= 3. The dup2(fd, 0) call will then work and the resulting fd 0 will be inheritable, including by-default by subprocess() processes. -- ___ Python tracker <https://bugs.python.org/issue46454> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46454] '0 -> /dev/null' is lost
Brett Randall added the comment:
docker run -i --rm python:3.9 <<-EOF
import os
print(os.get_inheritable(0))
fd_null_before_close = os.open("/dev/null", os.O_RDWR)
os.close(0)
fd_null = os.open("/dev/null", os.O_RDWR)
print(fd_null_before_close)
print(fd_null)
os.dup2(fd_null, 0)
print(os.get_inheritable(0))
os.dup2(fd_null_before_close, 0)
print(os.get_inheritable(0))
EOF
True
3
0
False
True
--
___
Python tracker
<https://bugs.python.org/issue46454>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29688] Add support for Path.absolute()
Brett Cannon added the comment: New changeset 18cb2ef46c9998480f7182048435bc58265c88f2 by Barney Gale in branch 'main': bpo-29688: document and test `pathlib.Path.absolute()` (GH-26153) https://github.com/python/cpython/commit/18cb2ef46c9998480f7182048435bc58265c88f2 -- ___ Python tracker <https://bugs.python.org/issue29688> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29688] Add support for Path.absolute()
Brett Cannon added the comment: @eryksun I'm not seeing what's wrong with your example. Would you mind pointing out what you expect the result to be? And are you saying on Windows you have to resolve the drive separately from the working directory and then concatenate them? -- ___ Python tracker <https://bugs.python.org/issue29688> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21762] update the import machinery to only use __spec__
Change by Brett Cannon : -- dependencies: +Use specs instead of just __loader__ in C code ___ Python tracker <https://bugs.python.org/issue21762> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21762] update the import machinery to only use __spec__
Brett Cannon added the comment: Dumping my personal notes here as backup and in case anyone else wants to know how this is going. 1. `__package__` - [x] Make sure all uses of the attribute fall back on `__spec__` (done way back when) - [x] Add an `ImportWarning` when the attribute is used but it differs from `__spec__` (3.6) - [x] Update code to prefer the spec over the attribute, raising `ImportWarning` when having to fall back to the attribute (3.10) - [ ] Change `ImportWarning` to `DeprecationWarning` when falling back to the attribute - [ ] Remove code in `importlib` that used the old attribute 2. `__loader__` - [x] Make sure all Python code uses of the attribute fall back on `__spec__` (3.10) - [ ] Update C code to fall back to using `__spec__` ([issue](https://bugs.python.org/issue42132)) - [ ] Add an `ImportWarning` when the attribute is used but it differs from `__spec__` - [ ] Update code to prefer the spec over the attribute, raising `ImportWarning` when having to fall back to the attribute - [ ] Change `ImportWarning` to `DeprecationWarning` when falling back to the attribute - [ ] Remove code in `importlib` that used the old attribute 3. `__cached__` - [ ] Make sure all uses of the attribute fall back on `__spec__` - [ ] Add an `ImportWarning` when the attribute is used but it differs from `__spec__` - [ ] Update code to prefer the spec over the attribute, raising `ImportWarning` when having to fall back to the attribute - [ ] Change `ImportWarning` to `DeprecationWarning` when falling back to the attribute - [ ] Remove code in `importlib` that used the old attribute -- ___ Python tracker <https://bugs.python.org/issue21762> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46556] pathlib.Path.__enter__() should emit DeprecationWarning
Brett Cannon added the comment: New changeset 06e1701ad3956352bc0f42b8f51c2f8cc85bf378 by Barney Gale in branch 'main': bpo-46556: emit `DeprecationWarning` from `pathlib.Path.__enter__()` (GH-30971) https://github.com/python/cpython/commit/06e1701ad3956352bc0f42b8f51c2f8cc85bf378 -- nosy: +brett.cannon ___ Python tracker <https://bugs.python.org/issue46556> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46556] pathlib.Path.__enter__() should emit DeprecationWarning
Change by Brett Cannon : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue46556> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46678] Invalid cross device link in Lib/test/support/import_helper.py
Brett Cannon added the comment: New changeset c2735b75afd530631efde4ddd3cb24bbdc285559 by Miss Islington (bot) in branch '3.10': bpo-46678: Fix Invalid cross device link in Lib/test/support/import_helper.py (GH-31204) (GH-31207) https://github.com/python/cpython/commit/c2735b75afd530631efde4ddd3cb24bbdc285559 -- nosy: +brett.cannon ___ Python tracker <https://bugs.python.org/issue46678> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46678] Invalid cross device link in Lib/test/support/import_helper.py
Change by Brett Cannon : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue46678> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46337] urllib.parse: Allow more flexibility in schemes and URL resolution behavior
Change by Brett Cannon : -- nosy: -brett.cannon ___ Python tracker <https://bugs.python.org/issue46337> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43275] [venv] Add a `.gitignore` file with content `*` in the root folder generated by venv module
Change by Brett Cannon : -- superseder: -> [venv] Adding a .gitignore file to virtual environments ___ Python tracker <https://bugs.python.org/issue43275> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46835] ImportError: bad magic number in ... does not indicate where is that file located
Change by Brett Cannon : -- nosy: +brett.cannon ___ Python tracker <https://bugs.python.org/issue46835> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46853] Python interpreter can get code from memory, it is not secure.
Brett Cannon added the comment: This is by design and thus not a security hole or bug. Also, for any future security issues, please disclose them responsibly by following the instructions at https://www.python.org/dev/security/ . -- nosy: +brett.cannon resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue46853> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46860] `--with-suffix` not respected on case-insensitive file systems
New submission from Brett Cannon : If you use `--with-suffix` on a case-insensitive file system it is ultimately ignored and forced to `.exe`. PR incoming. -- assignee: brett.cannon components: Build messages: 414051 nosy: brett.cannon priority: normal severity: normal status: open title: `--with-suffix` not respected on case-insensitive file systems type: behavior ___ Python tracker <https://bugs.python.org/issue46860> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46860] `--with-suffix` not respected on case-insensitive file systems
Change by Brett Cannon : -- keywords: +patch pull_requests: +29716 stage: -> patch review pull_request: https://github.com/python/cpython/pull/31593 ___ Python tracker <https://bugs.python.org/issue46860> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue44035] Regenerating the configure script fails even if dependencies are satisfied
Brett Cannon added the comment: For me it took `docker run -v (pwd):/src quay.io/tiran/cpython_autoconf` (on fish and didn't run `docker pull` ahead of time). @tiran are you okay if we document your image and how to run it at https://devguide.python.org/setup/?highlight=autoconf#regenerate-configure ? -- nosy: +brett.cannon ___ Python tracker <https://bugs.python.org/issue44035> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46860] `--with-suffix` not respected on case-insensitive file systems
Brett Cannon added the comment: New changeset 50ec3453c50c490eca7e990103c79671bd08ab2e by Brett Cannon in branch 'main': bpo-46860: Respect `--with-suffix` on case-insensitive file systems (GH-31593) https://github.com/python/cpython/commit/50ec3453c50c490eca7e990103c79671bd08ab2e -- ___ Python tracker <https://bugs.python.org/issue46860> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46860] `--with-suffix` not respected on case-insensitive file systems
Change by Brett Cannon : -- versions: +Python 3.11 ___ Python tracker <https://bugs.python.org/issue46860> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46860] `--with-suffix` not respected on case-insensitive file systems
Change by Brett Cannon : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue46860> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
Re: [Tracker-discuss] Spammer-messages this morning just me cleaning up
On 6/9/07, Paul Dubois <[EMAIL PROTECTED]> wrote: You may have received some messages this morning that looked like more spam. They were not, they were me permanently retiring some issues that had been posted by spammers a month ago. Unfortunately we have set up an auditor that sends ALL changes to python-bugs-list, so even such administrative actions result in messages. I lobbied for not sending out mail when there was no message attached (which is Roundup's default) but we were told to do otherwise. I continue to think this is a bad idea, and this morning's messages are an example why. (Another one was me just closing an issue without comment; it had been a test issue I had posted some time back). Well, this might be the example that changes that idea for the bugs list. Will just have to tell people to include a comment about why they performed an action in order for it to show up. I am entering the totally-retired state (just 3 more working days) and will start spam patrol on the tracker on a regular basis. Thanks, Paul! And hopefully retirement will be fun for you. -Brett ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1675334] Draft implementation for PEP 364
Changes by Brett Cannon: -- keywords: +py3k _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1675334> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1001] 2to3 crashes on input files with no trailing newlines
Changes by Brett Cannon: -- keywords: +py3k __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1001> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1202533] a bunch of infinite C recursions
Changes by Brett Cannon: -- keywords: +patch priority: normal -> high severity: normal -> major type: -> crash versions: +Python 2.6 _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1202533> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1202533] a bunch of infinite C recursions
Changes by Brett Cannon: -- priority: high -> urgent _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1202533> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1022] use bytes for code objects
Brett Cannon added the comment: I have security/stability issues with code objects having mutable bytecode. This would allow someone to possibly crash the interpreter with crappy bytecode. I also have a worry that someone might come up with some clever way of causing different code to execute through manipulating what LOAD_GLOBALS or STORE_GLOBALS accesses/sets. -- nosy: +brett.cannon __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1022> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1127] No tests for inspect.getfullargspec()
Changes by Brett Cannon: -- components: Library (Lib) keywords: py3k priority: high severity: normal status: open title: No tests for inspect.getfullargspec() versions: Python 3.0 __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1127> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1267884] crash recursive __getattr__
Changes by Brett Cannon: -- superseder: -> a bunch of infinite C recursions _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1267884> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1202533] a bunch of infinite C recursions
Brett Cannon added the comment: Rev. 58032 applied the patch and added a test to test_descr. -- resolution: -> fixed status: open -> closed _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1202533> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1121] Document inspect.getfullargspec()
New submission from Brett Cannon: inspect.getfullargspec() needs to be documented before it is backported to 2.6. -- components: Documentation keywords: py3k messages: 55717 nosy: brett.cannon priority: normal severity: normal status: open title: Document inspect.getfullargspec() versions: Python 3.0 __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1121> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1121] Document inspect.getfullargspec()
Changes by Brett Cannon: -- severity: normal -> minor __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1121> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1456280] Traceback error when compiling Regex
Changes by Brett Cannon: -- superseder: -> re incompatibility in sre title: Traceback error when compiling Regex -> Traceback error when compiling Regex _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1456280> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue214033] re incompatibility in sre
Changes by Brett Cannon: -- resolution: accepted -> type: -> behavior versions: +Python 2.6 Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue214033> ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1096] Deeply recursive repr segfault
Changes by Brett Cannon: -- priority: -> urgent __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1096> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1096] Deeply recursive repr segfault
Brett Cannon added the comment: Fixed in rev. 58096. -- assignee: -> brett.cannon nosy: +brett.cannon resolution: -> fixed status: open -> closed versions: +Python 2.6 __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1096> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1147] string exceptions inconsistently deprecated/disabled
Changes by Brett Cannon: -- assignee: -> brett.cannon nosy: +brett.cannon __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1147> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1147] string exceptions inconsistently deprecated/disabled
Brett Cannon added the comment: Fixed on the trunk in rev. 58108. Need to change 2.5 to raise a warning. -- priority: -> normal versions: -Python 2.6 __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1147> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1147] string exceptions inconsistently deprecated/disabled
Brett Cannon added the comment: Rev. 58109 covers 2.5. -- resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1147> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1686386] Python SEGFAULT on invalid superclass access
Brett Cannon added the comment: So the first example (in msg31624) crashes because of infinite recursion with the repr of exceptions:: #7771 0x00065178 in BaseException_repr (self=0x5dc6b8) at Objects/exceptions.c:128 #7772 0x0001d90c in PyObject_Repr (v=0x5dc6b8) at Objects/object.c:362 #7773 0x0008c180 in tuplerepr (v=0x5dad58) at Objects/tupleobject.c:221 The second one in msg31626 dies because of the str of exceptions:: #3839 0x0001dd88 in PyObject_Str (v=0x5dc6b8) at Objects/object.c:427 #3840 0x00065120 in BaseException_str (self=0x5dc6b8) at Objects/exceptions.c:110 #3841 0x0001dc0c in _PyObject_Str (v=0x5dc6b8) at Objects/object.c:407 Both fail because BaseException uses the str/repr of its arguments to construct what string to return. When it's itself it just goes on forever trying to get the next object's representation. The repr issue might be fixed by looking at how lists catch loops in themselves (don't remember the exact C function). Either way it is not really str/repr that is causing the issue but exceptions for not worrying about possible recursion thanks to using the str/repr of contained objects. _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1686386> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1686386] Python SEGFAULT on invalid superclass access
Changes by Brett Cannon: -- versions: +Python 2.6 _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1686386> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1686386] Python SEGFAULT on invalid superclass access
Brett Cannon added the comment: OK, so I have attached a possible patch. I found out that tuple.__repr__ didn't do anything to prevent infinite recursion since you can't pull it off from Python code. But obviously C code is another matter. =) Same goes for object.__str__; it didn't think about a type's tp_str doing something that could lead to an infinite recursion. Assigning back to Georg to make sure I am not doing something stupid nor that the approach is to broad by changing _PyObject_Str() and tuple.__repr__ instead of BaseException itself. I have not written tests yet as they are rather difficult to do for what the C code is doing without relying specifically on how exceptions do their __repr__/__str__. -- assignee: brett.cannon -> georg.brandl keywords: +patch status: open -> pending _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1686386> _ infinite_rec_fix.diff Description: Binary data ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1686386] Python SEGFAULT on tuple.__repr__ and str()
Changes by Brett Cannon: -- title: Python SEGFAULT on invalid superclass access -> Python SEGFAULT on tuple.__repr__ and str() _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1686386> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1158] %f format for datetime objects
Brett Cannon added the comment: Are you going to add support to strptime as well? As for the 'time' module, I don't think it would be useful as it serves no purpose since the time tuple can't resolve to that resolution. If you do add support, though, I guess you just default to 0. -- nosy: +brett.cannon __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1158> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1158] %f format for datetime objects
Brett Cannon added the comment: On 9/13/07, Skip Montanaro <[EMAIL PROTECTED]> wrote: > > Skip Montanaro added the comment: > > Brett> Are you going to add support to strptime as well? > > I looked at strptime for about two seconds then moved on. I presume you > would know how to add it easily though. ;-) > Adding support is not issue. It's exposing the microseconds to datetime. It would probably require something along the lines of returning a tuple with microseconds included and have time use a function that creates another tuple with that info removed and datetime using the more informational tuple. But adding the %f support is very straightforward. > Brett> As for the 'time' module, I don't think it would be useful as it > serves > Brett> no purpose since the time tuple can't resolve to that > Brett> resolution. > > Resolution isn't the issue. You just make sure you add enough zeroes to > make it be microseconds. The bigger problem is that time.strftime() takes a > tuple of ints which basically represents a struct tm. That struct has an > int seconds field and no sub-second field. You'd either have to start > allowing floating point tm_sec fields then either truncating or rounding > (but which?) to get ints when you need to actually generate an actual struct > tm. Right. I am in favour of this being just a datetime thing as we should get people moved off of time for stuff like this anyway. -Brett __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1158> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue416670] MatchObjects not deepcopy()able
Changes by Brett Cannon: -- dependencies: +Fix #416670: register SRE types Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue416670> ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue416670] MatchObjects not deepcopy()able
Changes by Brett Cannon: -- dependencies: -Fix #416670: register SRE types Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue416670> ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue487331] time mod's timezone doesn't honor TZ var
Brett Cannon added the comment: time.tzset() was added in Python 2.3. Closing as fixed. -- nosy: +brett.cannon resolution: -> fixed status: open -> closed Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue487331> ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue504152] rfc822 long header continuation broken
Changes by Brett Cannon: -- keywords: +patch Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue504152> ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue614555] Rewrite _reduce and _reconstructor in C
Brett Cannon added the comment: Classifying as an RFE since this is not critical (as shown by it not happening since early 2003). -- nosy: +brett.cannon type: -> rfe Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue614555> ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1083] Confusing error message when dividing timedelta using /
Changes by Brett Cannon: -- keywords: +py3k versions: +Python 3.0 __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1083> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue539444] asyncore file wrapper & os.error
Brett Cannon added the comment: Following Josiah's advice and closing this as this has been sitting here long enough. -- nosy: +brett.cannon resolution: -> invalid status: open -> closed Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue539444> ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue542314] long file name support broken in windows
Brett Cannon added the comment: Can someone verify that the length issue has been fixed since Ptyhon 2.5? -- nosy: +brett.cannon Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue542314> ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1083] Confusing error message when dividing timedelta using /
Brett Cannon added the comment: If you set nb_true_div on timedelta objects to delta_divide (just like nb_floor_div) you won't have this problem as the division will just work. Otherwise there is no other good way as if the divisor doesn't work you need to return NotImplemented, which then tries the right-hand object which fails, and 'object' returns the TypeError. Best you could do is a warning or something. But it might make sense to only set it on nb_true_div as the division does not round anything. -- nosy: +brett.cannon __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1083> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1164] tp_print slots don't release the GIL
Brett Cannon added the comment: I quickly handled the GIL for lists and ints in their tp_print functions and your example still deadlocked. Don't have time to dig deeper right now, but what more are you suggesting be done? -- nosy: +brett.cannon __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1164> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1164] tp_print slots don't release the GIL
Changes by Brett Cannon: -- versions: +Python 2.6 __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1164> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1164] tp_print slots don't release the GIL
Brett Cannon added the comment: Since I already did this once I just did a more thorough job; patch is attached. PyObject_WriteString() just calls PyFile_WriteObject() which ends up using PyObject_Print(), so it is was simple to handle those cases. I then released the GIL for strings, lists, and ints. That is enough to pass Armin's deadlock test. If the approach I am taking is OK with people and I can go through Object/*.c and do the proper thing for all the various object types for fprintf(), fputs(), fputc() and fwrite() (while skipping all of the debug output stuff) before committing the changes. __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1164> __ release_GIL_around_stdout.diff Description: Binary data ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1164] tp_print slots don't release the GIL
Changes by Brett Cannon: -- keywords: +patch __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1164> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1134] Parsing a simple script eats all of your memory
Brett Cannon added the comment: Note the patch is inlined in a message. -- keywords: +patch, py3k nosy: +brett.cannon __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1134> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1164] tp_print slots don't release the GIL
Brett Cannon added the comment: Good point. I changed it on my machine and it cut that whole section down to a single release/acquire. I will go ahead and do this for the other types and then upload another patch to be reviewed when it's ready. __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1164> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1164] tp_print slots don't release the GIL
Brett Cannon added the comment: OK, every PyTypeObject in Objects and Modules has its tp_print release the GIL. Once someone OKs the patch I will apply it. __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1164> __ GIL_release_tp_print.diff Description: Binary data ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1164] tp_print slots don't release the GIL
Brett Cannon added the comment: Applied in r58176. And I am glad this is not an issue in Py3K. =) -- resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1164> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1158] %f format for datetime objects
Brett Cannon added the comment: In terms of strptime, I would just change _strptime.strptime() to _strptime._strptime() and have it return everything along with the microseconds measurement. Then have public functions that call that function and either strip off the microseconds or not. -Brett On 9/17/07, Skip Montanaro <[EMAIL PROTECTED]> wrote: > > Skip Montanaro added the comment: > > Brett, > > Continuing the discussion of strptime... It returns a time.struct_time. > Would it cause too much breakage (only do this in 3.0) to add a tm_usec > field to the end of that object? It seems a lot of bits of code might > still expect a length 9 tuple-ish thing and do this: > > yy, mm, dd, hh, mm, ss, wk, j, tz = time.strptime(...) > > If we could make that change for 3.0 that might allow strptime to parse > %f format codes. > > S > > __ > Tracker <[EMAIL PROTECTED]> > <http://bugs.python.org/issue1158> > __ > ___ > Python-bugs-list mailing list > Unsubscribe: > http://mail.python.org/mailman/options/python-bugs-list/brett%40python.org > > __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1158> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1686386] Python SEGFAULT on tuple.__repr__ and str()
Changes by Brett Cannon: -- status: pending -> open _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1686386> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1123] split(None, maxsplit) does not strip whitespace correctly
Brett Cannon added the comment: The algorithm is actually kind of odd:: >>> " a b".split(None, 0) ['a b'] >>> "a b ".split(None, 0) ['a b '] >>> "a b ".split(None, 1) ['a', 'b '] So trailing whitespace on the original string is stripped only if the number of splits is great enough to lead to a possible split past the last element. But leading whitespace is always removed. Basically the algorithm stops looking for whitespace once it has encountered maxsplit instances of contiguous whitespace plus leading whitespace. -- nosy: +brett.cannon __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1123> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1176] str.split() takes no keyword arguments (Should this be expected?)
Brett Cannon added the comment: This is expected as str.split() is implemented in C and C code only has keyword arguments if someone puts in the time and effort to support them. Support could be added if so desired. But it does slow down argument passing. If you look you will notice that none of str's methods have keyword support. Changing this to an rfe. -- nosy: +brett.cannon priority: normal -> low type: behavior -> rfe __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1176> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1076790] test test_codecs failed
Changes by Brett Cannon: -- keywords: +patch _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1076790> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1023290] proposed struct module format code addition
Changes by Brett Cannon: -- keywords: +patch _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1023290> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1127] No tests for inspect.getfullargspec()
Brett Cannon added the comment: Won't know if more tests are needed until the patch is reviewed. Thanks for the work so far, though! -- assignee: -> brett.cannon keywords: +patch nosy: +brett.cannon __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1127> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1217] infinite loop in re module
Brett Cannon added the comment: I am not convinced this an infinite loop but more of a poor-performing regex over a large string. You have three greedy quantifiers in that regex. That means the first one is going to consume the entire file, and then you begin back-off looking for '://'. Once that is found you consume the rest of the string again and then back off looking for ':'. Then the rest of the string is consumed and then back-off begins for '@' which should fail since I can't find a single instance of '@'. But that is a lot of backing off over a large string which has a ton of partial matches before failure occurs when looking for the '@'. It looks like you are trying to match a URL, which means you probably want something more specific than '.' for those greedy quantifiers. Closing as invalid. -- assignee: -> brett.cannon nosy: +brett.cannon resolution: -> invalid status: open -> closed __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1217> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1217] infinite loop in re module
Brett Cannon added the comment: If you chop out a bunch of the text it finishes fine. I more succinct example that triggers the infinite recursion is necessary before I will believe this is not just because the regex has horrible performance thanks to its backtracking requirements. __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1217> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1631171] implement warnings module in C
Changes by Brett Cannon: -- assignee: -> brett.cannon nosy: +brett.cannon _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1631171> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1686386] Python SEGFAULT on tuple.__repr__ and str()
Brett Cannon added the comment: Applied in r58288. If I did something stupid or people don't want the overhead they can yell at the commit. =) -- resolution: -> fixed status: open -> closed _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1686386> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1686386] Python SEGFAULT on tuple.__repr__ and str()
Brett Cannon added the comment: And fixed in r58289. _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1686386> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1223] httplib does not handle ssl end of file properly
Brett Cannon added the comment: Patch is inlined in the opening comment for the issue. -- keywords: +patch nosy: +brett.cannon type: crash -> behavior __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1223> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1240] str.split bug when using sep = None and maxsplit
Brett Cannon added the comment: I know there is another filed bug on this topic, I just need to find it. -- nosy: +brett.cannon __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1240> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1123] split(None, maxsplit) does not strip whitespace correctly
Brett Cannon added the comment: Re-opening as jafo was referring to the string module's function implementation which is deprecated. The real issue is that the built-in types docs are bad. -- assignee: fdrake -> resolution: invalid -> status: closed -> open versions: +Python 2.6 __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1123> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1240] str.split bug when using sep = None and maxsplit
Brett Cannon added the comment: issue1123 was the issue I was thinking of. Setting that as a superceder as 1123 was closed prematurely. -- superseder: -> split(None, maxsplit) does not strip whitespace correctly __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1240> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1240] str.split bug when using sep = None and maxsplit
Changes by Brett Cannon: -- resolution: -> duplicate status: open -> closed __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1240> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1229] 3.0 library/stdtypes.rst
Brett Cannon added the comment: Fixed in revision 58353. -- assignee: -> brett.cannon keywords: +py3k nosy: +brett.cannon resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1229> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue467384] provide a documented serialization func
Changes by Brett Cannon: -- nosy: -brett.cannon Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue467384> ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue416670] MatchObjects not deepcopy()able
Changes by Brett Cannon: -- nosy: -brett.cannon Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue416670> ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1035] bytes buffer API needs to support read locking and/or PyBUF_LOCKDATA
Brett Cannon added the comment: All the tests pass for me, Gregory. Were the failures with some patch you had only locally? -- nosy: +brett.cannon priority: -> normal __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1035> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1238] dictobject and dictentry not used consistently in dictobject.c
Changes by Brett Cannon: -- priority: -> low __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1238> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1238] dictobject and dictentry not used consistently in dictobject.c
Brett Cannon added the comment: While I understand the argument for faster recompiles, dictobject.(c|h) do not change that often, and thus faster recompiles are not critical. I am with Guido and would rather see the module moved over to public names. Setting the priority to low as this is not critical in any way, although I am all for making code more readable and thus will review any patch that Anthon comes up with that uses the public names. -- nosy: +brett.cannon __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1238> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1160] Medium size regexp crashes python
Changes by Brett Cannon: -- priority: -> normal __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1160> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
