[issue8619] Doc bug for urllib.request._urlopener in Python 3.1+

sri added the comment: You missed the code part: urllib._urlopener = AppURLopener() -- ___ Python tracker ___ ___ Python-bugs-list ma

[issue8619] Doc bug for urllib.request._urlopener in Python 3.1+

Senthil Kumaran added the comment: Fixed in r80773 and r80774. Thanks. -- assignee: d...@python -> orsenthil nosy: +orsenthil resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker

[issue8619] Doc bug for urllib.request._urlopener in Python 3.1+

New submission from Sriram Thaiyar : http://docs.python.org/dev/py3k/library/urllib.request.html#urllib.request._urlopener [in the body] urllib._urlopener should be urllib.request._urlopener -- assignee: d...@python components: Documentation messages: 104998 nosy: Sriram.Thaiyar, d...@p

[issue8615] turtle.py - backport of 3.1 features

Benjamin Peterson added the comment: Feature freeze begins at beta 1, therefore I'm rejecting this. -- resolution: -> rejected status: open -> closed ___ Python tracker ___

[issue7472] email.encoders.encode_7or8bit(): typo "iso-2202". "iso-2022" is correct.

Changes by Shashwat Anand : Added file: http://bugs.python.org/file17215/encoders.patch ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue7472] email.encoders.encode_7or8bit(): typo "iso-2202". "iso-2022" is correct.

Shashwat Anand added the comment: I was getting a feel that the inner if-test is not being used in any case. Submitting the patch which removes the inner if test and adding a unittest. -- ___ Python tracker _

[issue8617] Non-existent variables documented

R. David Murray added the comment: These are references to environment variables. The markup marks them as such, but this does not translate into HTML in a visible way. Without a text description it is also left to guesswork as to how they function. The 2.7 docs are even more confusing, add

[issue7472] email.encoders.encode_7or8bit(): typo "iso-2202". "iso-2022" is correct.

R. David Murray added the comment: Comments on patch: We prefer patches to be generated from the top level directory of the checkout, so that it can be applied by doing 'patch -p0 ___ __

[issue8215] getargs.c in Python3 contains some TODO and the documentation is outdated

STINNER Victor added the comment: See also #8592. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue8592] 'y' does not check for embedded NUL bytes

STINNER Victor added the comment: See also #8215. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue8592] 'y' does not check for embedded NUL bytes

STINNER Victor added the comment: Same issue for y#: y# (...) This variant on s# doesn’t accept Unicode objects, only bytes-like objects. s# (...) The string may contain embedded null bytes. -- y* might mention that it accepts embedded null bytes. -- grep 'PyArg_Parse[^"]\+"[^:;)"]*y[^*]'

[issue2091] file accepts 'rU+' as a mode

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue4265] shutil.copyfile() leaks file descriptors when disk fills

STINNER Victor added the comment: Could you write a test? Use a fake file objects that raise (or not) an IOError on close(), and then check that close() was closed on both files. There are 4 cases: input.close() raises or not an exception, output.close() raises or not an exception. -

[issue4265] shutil.copyfile() leaks file descriptors when disk fills

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue665761] reduce() masks exception

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue8313] message in unittest tracebacks

STINNER Victor added the comment: > The downside of using backslashreplace (or repr, for that matter) is > that it does not preserve lengths, so the diff markers can get > misaligned. I find that an acceptable tradeoff, but 'replace' is > another option that preserves lengths, at least more ofte

[issue8610] Python3/POSIX: errors if file system encoding is None

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue8618] test_winsound failing on Windows Server 2008

New submission from Brian Curtin : Some of the test_alias_* functions in test_winsound are failing with a RuntimeError "Failed to play sound" when run on Server 2008 R2. The sound from each test exists in the registry so the test doesn't end up getting skipped. I'm guessing there is some miss

[issue8610] Python3/POSIX: errors if file system encoding is None

Changes by Antoine Pitrou : -- nosy: +loewis ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue8610] Python3/POSIX: errors if file system encoding is None

Changes by STINNER Victor : -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue8603] Create a bytes version of os.environ and getenvb()

STINNER Victor added the comment: @loewis: So do you agree to add os.environb and os.getenvb()? The documentation of os.environb and os.getenvb() in my last patch is very short. I'm not inspired. We told me on IRC to not use function annotations because annotation semantic was not decided ye

[issue8610] Python3/POSIX: errors if file system encoding is None

STINNER Victor added the comment: Patch for the second solution (fallback to utf-8 on get_codeset() failure): - create a subfunction initfsencoding() (Py_InitializeEx is already very long) - hardcode the encoding to utf-8 if nl_langinfo(CODESET) is missing - don't call get_codeset() on Windo

[issue8617] Non-existent variables documented

New submission from Dave Abrahams : http://docs.python.org/library/site.html#module-site mentions two variables that don't appear in my Python 2.6.5 installation's site module: PYTHONNOUSERSITE New in version 2.6. PYTHONUSERBASE New in version 2.6. -- assignee: d...@python components:

[issue8610] Python3/POSIX: errors if file system encoding is None

STINNER Victor added the comment: Here is a patch for the first solution: display a fatal error if we are unable to get the locale encoding. It does always exit with a fatal error if nl_langinfo(CODESET) is not available (and Py_FileSystemDefaultEncoding is not set). I don't think it's a goo

[issue7472] email.encoders.encode_7or8bit(): typo "iso-2202". "iso-2022" is correct.

Shashwat Anand added the comment: Adding unit-test for the patch -- keywords: +patch Added file: http://bugs.python.org/file17212/test_email.patch ___ Python tracker ___

[issue8616] Changes to content of Demo/turtle

Changes by Éric Araujo : -- nosy: +benjamin.peterson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue8615] turtle.py - backport of 3.1 features

Gregor Lingl added the comment: I see, that Benjamin Peterson, the release manager, is on the nosy list now. So please decide on this issue. If you need any supplementary information, I'll try to provide it. (The issue concerning the adoption of this version of the turtle module for Python 3

[issue8586] test_imp.py test failures on Py3K Mac OS X

Michael Foord added the comment: Committed revision 80771. -- assignee: michael.foord -> barry resolution: accepted -> works for me stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker

[issue8615] turtle.py - backport of 3.1 features

Gregor Lingl added the comment: As far as I remember, in the past there was a feature - freeze only with the appearance of beta2? Maybe I'm wrong. So there remains only to try to interpret the term "new feature" appropriately, as all those features are already present in Python 3.1. If there

[issue8432] buildbot: test_send_signal of test_subprocess failure

Michael Foord added the comment: I get this same failure on Mac OS X 10.6.3 as well. -- nosy: +michael.foord ___ Python tracker ___ __

[issue8616] Changes to content of Demo/turtle

Changes by Gregor Lingl : Added file: http://bugs.python.org/file17211/tdemo_scribble.py ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue8615] turtle.py - backport of 3.1 features

Martin v. Löwis added the comment: Unfortunately, I feel that you are (again) too late here. 2.7 has already seen its first beta release, so new features are not acceptable. You can still try to petition acceptance of new features with the release manager. --

[issue8616] Changes to content of Demo/turtle

Changes by Gregor Lingl : Added file: http://bugs.python.org/file17210/tdemo_round_dance.py ___ Python tracker ___ ___ Python-bugs-list mailing

[issue8616] Changes to content of Demo/turtle

Changes by Gregor Lingl : Added file: http://bugs.python.org/file17209/tdemo_nim.py ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue8616] Changes to content of Demo/turtle

New submission from Gregor Lingl : turtleDemo.py contains a string referring to the outdated xturtle. Should be replaced according to the submitted diff. Moreover I'd like to propose to add to demo-scripts to the Demo-directory, namely tdemo_nim.py and tdemo_round_dance.py as well as to replace

[issue8615] turtle.py - backport of 3.1 features

Changes by Brian Curtin : -- nosy: +benjamin.peterson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue8615] turtle.py - backport of 3.1 features

Gregor Lingl added the comment: Here, just for your information, the appropriate unified diff (from the version in 2.7b1 to the new submitted one. -- keywords: +patch Added file: http://bugs.python.org/file17207/turtle27b1_to_turtle27.diff ___ Pytho

[issue8615] turtle.py - backport of 3.1 features

New submission from Gregor Lingl : The file submitted, turtle.py, essentially contains a backport of the new features, which were added to the turtle module with Python 3.1. Otherwise this versions is 100% compatible with the turtle module of Python 2.6. So scripts written with Python 3.1's tu

[issue5727] doctest pdb readline broken

Changes by Alexander Belopolsky : -- nosy: +belopolsky ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue7835] Minor bug in 2.6.4 related to cleanup at end of program

Changes by cburroughs : -- nosy: +cburroughs ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue812369] module shutdown procedure based on GC

Changes by cburroughs : -- nosy: +cburroughs ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue8483] asyncore.dispatcher's __getattr__ method produces confusing effects

Giampaolo Rodola' added the comment: As per discussion on #python-dev we think it's better to proceed as follows: for python 2.7 and 3.2: - fix __getattr__ error message - raise a DeprecationWarning if cheap inheritance is used and definitively remove its support in the next major version

[issue5727] doctest pdb readline broken

Changes by Jean-Paul Calderone : -- stage: unit test needed -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue8614] test_gzip fails on OS X

Mark Dickinson added the comment: Thanks, Antoine. Applied in r80762 through r80765. -- resolution: -> fixed stage: -> committed/rejected status: open -> closed type: -> behavior ___ Python tracker

[issue5727] doctest pdb readline broken

Sriram added the comment: Hi, On second thoughts, it made more sense to validate pdb directly instead of validating doctest's debugger. I have also used few inputs, I got from irc chat at #python-dev room in writing the test case. Thanks to them. I have attached the svn diff. Please review

[issue8614] test_gzip fails on OS X

Mark Dickinson added the comment: That fixes the failure. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue1533] Bug in range() function for large values

Alexander Belopolsky added the comment: I am attaching a py3k patch that adds new tests. Since there are no end user visible changes, I don't believe a Misc/NEWS entry is needed. A commit message may read: Issue #1533: Tests only. Added tests for consistency in range function argument proc

[issue8614] test_gzip fails on OS X

Antoine Pitrou added the comment: Ok, can you try the following patch then: Index: Lib/gzip.py === --- Lib/gzip.py (révision 80760) +++ Lib/gzip.py (copie de travail) @@ -362,7 +362,7 @@ if self.mode == WRITE:

[issue8614] test_gzip fails on OS X

Mark Dickinson added the comment: Yep, that's enough to trigger it: Python 2.7b1+ (trunk:80760, May 4 2010, 19:27:27) [GCC 4.2.1 (Apple Inc. build 5659)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> f = open('LICENSE', 'rb') [35032 refs] >>> f.flush() T

[issue8586] test_imp.py test failures on Py3K Mac OS X

Barry A. Warsaw added the comment: +1 -- assignee: barry -> michael.foord resolution: works for me -> accepted ___ Python tracker ___

[issue8614] test_gzip fails on OS X

Antoine Pitrou added the comment: Can you try the following: >>> f = open('LICENSE', 'rb') >>> f.flush() -- ___ Python tracker ___ __

[issue8614] test_gzip fails on OS X

New submission from Mark Dickinson : test_buffered_reader test_gzip is failing for me since r80720, on trunk on OS X 10.6.3: == ERROR: test_buffered_reader (__main__.TestGzip) ---

[issue8586] test_imp.py test failures on Py3K Mac OS X

Michael Foord added the comment: On trunk the definition of unlink is: def unlink(filename): try: os.unlink(filename) except OSError: pass :-) Changing it as you suggest fixes the problem though. Ok to commit? -- ___ Pytho

[issue8586] test_imp.py test failures on Py3K Mac OS X

Barry A. Warsaw added the comment: Maybe you just want to relax the test in the except clause of test.support.unlink()? Or change the test to if error.errno not in (errno.ENOENT, errno.ENOTDIR) ? -- ___ Python tracker

[issue8586] test_imp.py test failures on Py3K Mac OS X

Michael Foord added the comment: Ok, so the cause of the bug is 'simple' - not sure what the best fix is. When I run python from a freshly built py3k I have the following as sys.path: ['', '/dev/null/lib/python32.zip', '/compile/python-trunk3/Lib', '/compile/python-trunk3/Lib/plat-darwin', '

[issue8611] Python3 doesn't support locale different than utf8 and an non-ASCII path (POSIX)

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue8586] test_imp.py test failures on Py3K Mac OS X

Michael Foord added the comment: Any idea where this path comes from? I can go spelunking through the code myself to investigate. -- ___ Python tracker ___ _

[issue1533] Bug in range() function for large values

Mark Dickinson added the comment: +1 for forward-porting/adapting relevant tests to py3k. -- assignee: mark.dickinson -> belopolsky ___ Python tracker ___ ___

[issue8008] Allow Arbitrary OpenID providers in this bug tracker

Jesús Cea Avión added the comment: Uhmmm... My browser seems crazy. -- nosy: +georg.brandl, r.david.murray ___ Python tracker ___ ___

[issue8008] Allow Arbitrary OpenID providers in this bug tracker

Jesús Cea Avión added the comment: Someway, the closed state vanished. -- nosy: -georg.brandl, r.david.murray priority: normal -> ___ Python tracker ___ ___

[issue1533] Bug in range() function for large values

Alexander Belopolsky added the comment: On Tue, May 4, 2010 at 12:32 PM, Mark Dickinson wrote: > > Mark Dickinson added the comment: > > Applied to trunk in r80758. > > Do people want this to go into 2.6 as well? Also, should additional unit tests forward ported to 3.x? If so, let me do it a

[issue1533] Bug in range() function for large values

Mark Dickinson added the comment: Applied to trunk in r80758. Do people want this to go into 2.6 as well? The patch would need to be modified to produce a warning for floats instead of giving a TypeError (and the tests would need to be modified to test for that warning). -- ___

[issue8576] test_support.find_unused_port can cause socket conflicts on Windows

Paul Moore added the comment: Thanks for the suggestions, I'll see if I can implement something based on them. -- ___ Python tracker ___ _

[issue8576] test_support.find_unused_port can cause socket conflicts on Windows

Jean-Paul Calderone added the comment: > One of the tests in test_socket is checking that an attempt to connect to a > port with no server running gives socket.error. For that, we need a port > that's guaranteed to have no server present. A good way to do this is to create a socket, bind it t

[issue1533] Bug in range() function for large values

Mark Dickinson added the comment: [Some of the Alexander's questions about procedures aren't really related to this issue; I've answered those offline. Here are the answers to the others.] >> - initialize low to NULL, to match the Py_XDECREF(low) (could change >> that Py_XDECREF to Py_DE

[issue8576] test_support.find_unused_port can cause socket conflicts on Windows

Paul Moore added the comment: One of the tests in test_socket is checking that an attempt to connect to a port with no server running gives socket.error. For that, we need a port that's guaranteed to have no server present. I think that one of the tests in test_httplib checks the source_addre

[issue8576] test_support.find_unused_port can cause socket conflicts on Windows

Jean-Paul Calderone added the comment: > You mean that socket.create_connection(), httplib (issue 3972) and ftplib > (issue 8594) should have used a different API to implement their > "source_address" option? I'm not sure what you mean. The problem here is that you cannot reliably bind a sp

[issue5753] CVE-2008-5983 python: untrusted python modules search path

R. David Murray added the comment: FWIW I agree with Antoine. -- nosy: +r.david.murray ___ Python tracker ___ ___ Python-bugs-list mai

[issue8313] message in unittest tracebacks

STINNER Victor added the comment: Attached patch fixes _some_str() function of the traceback module: encode unicode exception message to ASCII using backslashreplace error handler. ASCII is not the best choice, but str(unicode(...)) uses also ASCII (the default encoding) and we don't know the

[issue1533] Bug in range() function for large values

Changes by Alexander Belopolsky : -- assignee: belopolsky -> mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue1533] Bug in range() function for large values

Alexander Belopolsky added the comment: On Tue, May 4, 2010 at 8:34 AM, Mark Dickinson wrote: .. > I took the liberty of messing with your patch slightly; I didn't want > to ask you to make further changes since the patch was fine, and my > messing was mostly just to satisfy my own fussiness (

[issue8313] message in unittest tracebacks

STINNER Victor added the comment: > Very recently, issue8533 changed regrtest.py to use > 'backslashreplace' when printing errors. This issue seems > very similar Issue #8533 is not directly related because in this issue the error occurs before writing the traceback to the terminal.

[issue8313] message in unittest tracebacks

STINNER Victor added the comment: The example raises an AssertionError(u'\n- \ufffd+ \ufffd\ufffd') which is converted to string by traceback.format_exception(). This function fails in _some_str() on str(value) instruction. You can reproduce the error with: >>> str(AssertionError(u"\xe9")) Un

[issue8613] Decimal module flags undetermined when a signal is trapped.

New submission from Mark Dickinson : In an effort to keep to one issue per tracker item, I'm pulling this issue out of the comments on issue 8567. Issue: if a Decimal operation raises several signals, and one or more of those signals is trapped, how should that operation affect flags? Decima

[issue8567] decimal module doesn't respect precedence rules for exceptional conditions

Mark Dickinson added the comment: Precedence fixed in r80753 through r80756. That still leaves open the problem of what flags should be set; however, we should discuss this in a separate issue. -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed

[issue8313] message in unittest tracebacks

Amaury Forgeot d'Arc added the comment: Very recently, issue8533 changed regrtest.py to use 'backslashreplace' when printing errors. This issue seems very similar -- nosy: +amaury.forgeotdarc, haypo ___ Python tracker

[issue8612] multiprocessing Queue module failes to send INIConfig objects

New submission from Zaar Hai : I'm using INIConfig class from iniparse module(http://code.google.com/p/iniparse). I've tried to use multiprocessing.Queue to propagate configuration changes between the processes. However, INIConfig instances have troubles being pushed through Queue objects. I

[issue8611] Python3 doesn't support locale different than utf8 and an non-ASCII path (POSIX)

STINNER Victor added the comment: I have a patch implementation most of the point described in my first message. I have to rework on it before submit it. The patch depends on other issues, and I prefer to first fix all related issues. -- ___ Python

[issue8313] message in unittest tracebacks

Michael Foord added the comment: Sounds like a good solution - I'll look at this, thanks. -- ___ Python tracker ___ ___ Python-bugs-li

[issue5753] CVE-2008-5983 python: untrusted python modules search path

Antoine Pitrou added the comment: > Can anyone move this to Stage: patch review (for the fix approach > proposed in msg90336)? Or does anyone have better idea on how to move > this closer to final fix or wontfix / reject? Thank you! I stand by my opinion that adding another hack in the initia

[issue3823] ssl.wrap_socket() is incompatible with servers that drop privileges, due to keyfile requirement

Antoine Pitrou added the comment: There's a patch in issue8550 to expose SSL contexts as first-class objects. It allows you to create first your context object(s) and load certificates, then drop privileges, then create sockets using this/these contexts. In any case, resolution can't happen be

[issue8313] message in unittest tracebacks

Gunnlaugur Thor Briem added the comment: Replacing the message with its repr seems to me at least strongly preferable to the current “hide it all” behavior. :) Better, msg.encode('ascii', 'backslashreplace') does what repr does with unencodable characters, but does not add the quotes, so the

[issue8477] _ssl: support surrogates in filenames, and bytes/bytearray filenames

Antoine Pitrou added the comment: Most of this should be solved if the patch in issue8550 gets accepted. As for test_decode_certificate, it seems it isn't used anywhere, and could therefore be deleted. -- ___ Python tracker

[issue8611] Python3 doesn't support locale different than utf8 and an non-ASCII path (POSIX)

Antoine Pitrou added the comment: Or find_module() could use wcstombs() as long as Py_FileSystemDefaultEncoding is NULL. -- ___ Python tracker ___ __

[issue8611] Python3 doesn't support locale different than utf8 and an non-ASCII path (POSIX)

Antoine Pitrou added the comment: We could have a separate list storing the original bytes form of sys.path; this list would be used by find_module() as long as Py_FileSystemDefaultEncoding isn't initialized. -- nosy: +pitrou ___ Python tracker

[issue8242] Improve support of PEP 383 (surrogates) in Python3: meta-issue

STINNER Victor added the comment: I opened a different issue to use surrogates in Python module path: #8611, but the issue is not specific to surrogates ("Python3 doesn't support locale different than utf8 and an non-ASCII path (POSIX)"). -- ___ Py

[issue8611] Python3 doesn't support locale different than utf8 and an non-ASCII path (POSIX)

New submission from STINNER Victor : Python3 is unable to start (bootstrap failure) on a POSIX system if the locale encoding is different than utf8 and the Python path (standard library path where the encoding module is stored) contains a non-ASCII character. (Windows and Mac OS X are not affe

[issue1533] Bug in range() function for large values

Mark Dickinson added the comment: Re emacs: C-c . python should set a python 2.x-friendly indentation mode. There's also a python-new style floating around somewhere on the web (not part of emacs as standard), suitable for the 4-space indent style that's supposed to be used for new code. -

[issue1533] Bug in range() function for large values

Alexander Belopolsky added the comment: I see. Let me take a look. BTW, I tried to use tabs for indentation in the patch, but emacs was not always happy about it. Is there some c-mode setting that I don't know about that would take care of that? On May 4, 2010, at 8:34 AM, Mark Dickinson

[issue1533] Bug in range() function for large values

Mark Dickinson added the comment: Hi Alexander, I took the liberty of messing with your patch slightly; I didn't want to ask you to make further changes since the patch was fine, and my messing was mostly just to satisfy my own fussiness (only the first two items were really necessary): Mi

[issue1533] Bug in range() function for large values

Alexander Belopolsky added the comment: On May 4, 2010, at 7:27 AM, Mark Dickinson wrote: > > Mark Dickinson added the comment: > > Thanks for the fixes. The latest patch looks good to me. > > Alexander, is it okay for me to commit this? > Sure. Why do you have to ask? -- nosy: +

[issue5753] CVE-2008-5983 python: untrusted python modules search path

Tomas Hoger added the comment: Can anyone move this to Stage: patch review (for the fix approach proposed in msg90336)? Or does anyone have better idea on how to move this closer to final fix or wontfix / reject? Thank you! -- ___ Python tracker

[issue8608] fix_import prefixes "." to already relative imports

R. David Murray added the comment: Thanks, but this is a duplicate of issue 8553, which has already been fixed. -- nosy: +r.david.murray resolution: -> duplicate stage: -> committed/rejected status: open -> closed superseder: -> 2to3 breaks relative imports _

[issue8557] subprocess PATH semantics and portability

R. David Murray added the comment: Fair enough. Thank you for your detective work, and hopefully someone will be interested enough to pick this up again later. -- status: open -> languishing ___ Python tracker __

[issue8610] Python3/POSIX: errors if file system encoding is None

New submission from STINNER Victor : On POSIX (but not on Mac OS X), Python3 calls get_codeset() to get the file system encoding. If this function fails, sys.getfilesystemencoding() returns None. PyUnicode_DecodeFSDefaultAndSize() fallbacks to utf-8 whereas subprocess fail: ... File "/ho

[issue1533] Bug in range() function for large values

Mark Dickinson added the comment: Thanks for the fixes. The latest patch looks good to me. Alexander, is it okay for me to commit this? -- resolution: -> accepted ___ Python tracker _

[issue8513] subprocess: support bytes program name (POSIX)

STINNER Victor added the comment: Bytes program name problem should be splitted in two parts: (a) subprocess.call([b'env']) and subprocess.call([b'env'], env={'PATH': '/usr/bin'}): bytes program and unicode environ (b) bytes program and bytes environ Part (a) (a) would benefit fro

[issue8514] Create fsencode() and fsdecode() functions in os.path

STINNER Victor added the comment: I think that fsencode() (and fsdecode()) should be specific to POSIX. I don't know any good reason to encode a nice and correctly encoded unicode string to the ugly MBCS "encoding". -- ___ Python tracker

[issue8603] Create a bytes version of os.environ and getenvb()

STINNER Victor added the comment: New version of my patch, which looks much better. Summary: Issue #8603: Create os.environb and os.getenvb() on POSIX system. os.unsetenv() encodes str argument using file system encoding and surrogateescape error handler (instead of utf8/strict), and acce

[issue8609] itertools: problem with nested groupby, list()

Nico added the comment: Okay, thanks for the hint. Closing as invalid. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

  1   2   >