[issue11875] OrderedDict.__reduce__ not threadsafe

Raymond Hettinger added the comment: Mario, thanks for the bug report. -- status: open -> closed ___ Python tracker ___ ___ Python-bu

[issue8809] smtplib should support SSL contexts

Kasun Herath added the comment: I'm submitting a new patch with changes suggested by Terry. But I feel an example of how to use a SSLContext inside the Docstring of SMTP_SSL constructor is unnecessary since no smtp specific things are done to the passed SSLContext. Any ideas about this sugges

[issue7549] 2.6.4 Win32 linked to debug DLLs?

Jonathon Rossi added the comment: I just encountered this error with an older version (2.6.2) of python on Windows Server 2008 R2. >From looking at the logs it looks like the Customer Experience Improvement >Program (CEIP) functionality is causing this problem because it has a >scheduled tas

[issue10596] modulo operator bug

Tim Peters added the comment: Raymond, Mark pointed to the footnote explaining the first result. As to the second, Kahan tried his best, but I'm afraid nobody can make me care about the sign bit on a zero ;-) Whatever Mark thought best is fine by me. --

[issue8809] smtplib should support SSL contexts

david added the comment: It should also explain how the context can be used. An example of how to use it to establish a 'secured' connection would be a nice to have. -- ___ Python tracker

[issue8809] smtplib should support SSL contexts

Terry J. Reedy added the comment: This sentence is awkward, at best. "Alternative to a private key and a certificate key an optional SSLContext could be specified." I suggest something like: "SSLcontext, also optional, is an alternative to keyfile and certfile; if it is specified, keyfile and

[issue8886] zipfile.ZipExtFile is a context manager, but that is not documented

Changes by Brian Curtin : -- resolution: accepted -> fixed stage: patch review -> committed/rejected status: open -> closed versions: -Python 3.1 ___ Python tracker ___ _

[issue8886] zipfile.ZipExtFile is a context manager, but that is not documented

Roundup Robot added the comment: New changeset 83a426e969f5 by Brian Curtin in branch '2.7': Fix #8886. Use context managers throughout zipfile tests. http://hg.python.org/cpython/rev/83a426e969f5 -- nosy: +python-dev ___ Python tracker

[issue11619] On Windows, don't encode filenames in the import machinery

STINNER Victor added the comment: > c) parse_source_module() > => covered by the issue #10785. Issue #10785 didn't change parse_source_module(): it does still encode the filename. We need Unicode version of PyParser_ASTFromFile() and PyAST_Compile(): a new version of these functions acceptin

[issue11619] On Windows, don't encode filenames in the import machinery

Roundup Robot added the comment: New changeset e4e92d68ba3a by Victor Stinner in branch 'default': Close #11619: write_compiled_module() doesn't encode the filename http://hg.python.org/cpython/rev/e4e92d68ba3a -- resolution: -> fixed stage: -> committed/rejected status: open -> close

[issue1294232] Error in metaclass search order

Nick Coghlan added the comment: This last point sounds like an error in PEP 3115 rather than an error in the implementation - as the exception says, the metaclass of a derived class must be the same as or a subclass of the metaclasses of all of its bases. Since that rule applies recursively, and

[issue10540] test_shutil fails on Windows after r86733

Brian Curtin added the comment: This hasn't been an issue for quite some time, and I suspect the follow-up work on symbolic and hard links and their supporting functions corrected any problems in this area. -- resolution: -> works for me stage: needs patch -> committed/rejected statu

[issue11873] test_regexp() of test_compileall failure on "x86 OpenIndiana 3.x"

Changes by R. David Murray : -- nosy: +r.david.murray ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue8944] test_winreg.test_reflection_functions fails on Windows Server 2003

Brian Curtin added the comment: I no longer have access to a Server 2003 machine and I don't remember this happening the last few times I worked on that OS so it may have been fixed. If this occurs for anyone else, feel free to reopen. -- resolution: -> rejected stage: needs patch ->

[issue8407] expose signalfd(2) and sigprocmask(2) in the signal module

STINNER Victor added the comment: Oh, I forget to read again http://codereview.appspot.com/1132041. Here is an updated patch reusing some tests and with a better documentation. -- Added file: http://bugs.python.org/file21736/signal_pthread_sigmask-2.patch _

[issue11882] test_imaplib failed on x86 ubuntu

R. David Murray added the comment: This is a repeatable error? What is your system timezone set to? The difference is exactly one half hour. Does the test pass if you change the calendar.timegm call to have '0' or '1' as the last element of the tuple instead of '-1'? -- nosy: +bel

[issue11859] test_interrupted_write_text() of test_io failed of Python 3.3 on FreeBSD 7.2

Changes by STINNER Victor : -- dependencies: +expose signalfd(2) and sigprocmask(2) in the signal module ___ Python tracker ___ ___ Py

[issue8407] expose signalfd(2) and sigprocmask(2) in the signal module

STINNER Victor added the comment: signal_pthread_sigmask.patch: - add signal.pthread_sigmask() function with doc and tests - add SIG_BLOCK, SIG_UNBLOCK, SIG_SETMASK constants - fix #11859: fix tests of test_io using threads and an alarm: use pthread_sigmask() to ensure that only the main thr

[issue11875] OrderedDict.__reduce__ not threadsafe

Roundup Robot added the comment: New changeset 408f23b6cec5 by Raymond Hettinger in branch '3.1': Issue #11875: Alter the previous fix to work better with subclasses http://hg.python.org/cpython/rev/408f23b6cec5 New changeset 4e6840477d96 by Raymond Hettinger in branch '3.2': Issue #11875: Alte

[issue11875] OrderedDict.__reduce__ not threadsafe

Roundup Robot added the comment: New changeset db66eaf353a6 by Raymond Hettinger in branch '2.7': Issue #11875: Alter the previous fix to work better with subclasses http://hg.python.org/cpython/rev/db66eaf353a6 -- ___ Python tracker

[issue11223] interruption of locks by signals not guaranteed when the semaphore implementation is not used

Roundup Robot added the comment: New changeset bc1c6bd7eeb0 by Victor Stinner in branch 'default': Issue #11223: fix test_dummy_threading, add _dummy_thread.info() http://hg.python.org/cpython/rev/bc1c6bd7eeb0 -- ___ Python tracker

[issue11223] interruption of locks by signals not guaranteed when the semaphore implementation is not used

STINNER Victor added the comment: Let's wait 6 hours for "x86 FreeBSD 6.4 3.x": http://www.python.org/dev/buildbot/all/builders/x86%20FreeBSD%206.4%203.x The first build including my fix (383a7301616b) should be: http://www.python.org/dev/buildbot/all/builders/x86%20FreeBSD%206.4%203.x/builds/1

[issue11223] interruption of locks by signals not guaranteed when the semaphore implementation is not used

Roundup Robot added the comment: New changeset 383a7301616b by Victor Stinner in branch 'default': Issue #11223: Add threading._info() function providing informations about the http://hg.python.org/cpython/rev/383a7301616b -- ___ Python tracker

[issue11223] interruption of locks by signals not guaranteed when the semaphore implementation is not used

Antoine Pitrou added the comment: > I also renamed 'name' key to 'thread', so 'thread' is the name of the > *thread* implementation, and 'lock' is the name of the *lock* > implementation. Not that I want to bikeshed, but I think 'name' was ok (since you get the dict by calling threading._info()

[issue11223] interruption of locks by signals not guaranteed when the semaphore implementation is not used

STINNER Victor added the comment: > The path which sets "pthread_version" should be inside "#ifdef > _POSIX_THREADS". > Also, some comments about the doc: > - you need a "versionadded" tag Right, fixed. > - "use_semaphores" should explain that these semaphores are used for > locks; also the al

[issue11882] test_imaplib failed on x86 ubuntu

Changes by Antoine Pitrou : -- nosy: +r.david.murray ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue11863] Enforce PEP 11 - remove support for legacy systems

Antoine Pitrou added the comment: > Python/thread.c contains a reference to a missing file: > > #ifdef PLAN9_THREADS > #include "thread_plan9.h" > #endif > > But I don't see where PLAN9_THREADS is defined. > > remove_threads.patch removes these 3 lines. > > -- > > There is also an unused fi

[issue11875] OrderedDict.__reduce__ not threadsafe

Changes by Daniel Urban : -- nosy: +durban ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue9896] Introspectable range objects

Daniel Urban added the comment: Thanks, I've corrected my patch. -- Added file: http://bugs.python.org/file21733/range_attrs_3.patch ___ Python tracker ___ __

[issue11863] Enforce PEP 11 - remove support for legacy systems

STINNER Victor added the comment: Python/thread.c contains a reference to a missing file: #ifdef PLAN9_THREADS #include "thread_plan9.h" #endif But I don't see where PLAN9_THREADS is defined. remove_threads.patch removes these 3 lines. -- There is also an unused file: Python/thread_wince.c.

[issue11883] Call connect() before sending an email with smtplib

Changes by Sandro Tosi : Added file: http://bugs.python.org/file21732/smtp_connect-3.2.patch ___ Python tracker ___ ___ Python-bugs-list maili

[issue11883] Call connect() before sending an email with smtplib

New submission from Sandro Tosi : Hi, following up http://mail.python.org/pipermail/docs/2011-April/003742.html here are a couple of patches to call connect() after smtplib.SMTP() and sendmail(). Patches are: 2.7: to be applied in 2.7 and merged into 3.1 3.2: to be applied in 3.2 and merged in

[issue11875] OrderedDict.__reduce__ not threadsafe

Amaury Forgeot d'Arc added the comment: The call to self.__class__() can break subclasses of OrderedDict for two reasons: - The subclass constructor may have a different signature - Attributes set by the subclass.__init__ are removed from the pickle:: import collections, pickle class Mydict(c

[issue8809] smtplib should support SSL contexts

Kasun Herath added the comment: I did a patch that allows smtplib.SMTP_SSL constructor to accept an optional SSLContext -- keywords: +patch nosy: +kasun Added file: http://bugs.python.org/file21730/smtp_sslcontext.patch ___ Python tracker

[issue1294232] Error in metaclass search order

Daniel Urban added the comment: Thanks for the review! I've updated my patch: - renamed it to _PyType_CalculateMetaclass - in __build_class__ call it even when a metaclass is declared - added a test for this case (which fails with my previous patch) However I noticed another problem: the decla

[issue11875] OrderedDict.__reduce__ not threadsafe

Mario Juric added the comment: Hi Raymond, Excellent! Many thanks for such a quick fix, this has been bugging us for months! -- ___ Python tracker ___

[issue10910] pyport.h FreeBSD/Mac OS X "fix" causes errors in C++ compilation

Nasos Dousis added the comment: Meador et al, Thanks for your attention to this issue. Just to clarify, I can eliminate the compile errors by prepending #include "Python.h" to any source file with #include Also, my code compiles in Linux, with and without the Python.h header: $ uname -a L

[issue11881] Add list.get

Raymond Hettinger added the comment: > operator.getitem could be extended to accept default value That would be relatively harmless. And because it isn't type specific to lists, it would be applicable to other types that might better use cases than lists do. If you want to pursue this, plea

[issue10932] distutils.core.setup - data_files misbehaviour ?

Prashant Kumar added the comment: Sure, patch.diff is a complete one. -- Added file: http://bugs.python.org/file21727/patch.diff ___ Python tracker ___ _

[issue10932] distutils.core.setup - data_files misbehaviour ?

Changes by Prashant Kumar : Removed file: http://bugs.python.org/file21721/fix-manifest.diff ___ Python tracker ___ ___ Python-bugs-list maili

[issue10932] distutils.core.setup - data_files misbehaviour ?

Changes by Prashant Kumar : Removed file: http://bugs.python.org/file21720/test_command_sdist.diff ___ Python tracker ___ ___ Python-bugs-list

[issue11881] Add list.get

Filip Gruszczyński added the comment: Nick Coghlan suggested, that operator.getitem could be extended to accept default value. How does it sound to you? -- ___ Python tracker _

[issue11882] test_imaplib failed on x86 ubuntu

New submission from Kasun Herath : test_imaplib failed on x86 ubuntu machine with following error(s) == FAIL: test_Internaldate2tuple (test.test_imaplib.TestImaplib) --

[issue11881] Add list.get

Raymond Hettinger added the comment: What did you have in mind for the operator module? -- ___ Python tracker ___ ___ Python-bugs-lis

[issue11875] OrderedDict.__reduce__ not threadsafe

Raymond Hettinger added the comment: Mario, I removed the unnecessary mutation, but remember that OrderedDict's are not thread-safe in general. Anything that updates an OrderedDict will temporarily leave it in an inconsistent state while the links and mappings are being updated. That bein

[issue11881] Add list.get

Raymond Hettinger added the comment: Sorry, this has come up before and was rejected. -- nosy: +rhettinger resolution: -> rejected status: open -> closed ___ Python tracker ___

[issue11881] Add list.get

New submission from Filip Gruszczyński : I have proposed on Core Mentorship list to add get(index, default) method to list object. I was suggested to bring it up here and also told, that improving operator module could be a better solution. This is why I would like to ask, if it makes sense to

[issue11828] startswith and endswith don't accept None as slice index

Torsten Becker added the comment: Hi, Jesús, I merged the patch up in the branches "startswith-slices-issue11828-3.2" [1] and "startswith-slices-issue11828-3.3" [2] in my hg repository. [1]: https://bitbucket.org/t0rsten/cpython/changeset/49028581e43a [2]: https://bitbucket.org/t0rsten/cpytho

[issue11875] OrderedDict.__reduce__ not threadsafe

Roundup Robot added the comment: New changeset 50a89739836f by Raymond Hettinger in branch '3.1': Issue 11875: Keep OrderedDict's __reduce__ from temporarily mutating the object. http://hg.python.org/cpython/rev/50a89739836f New changeset a7ac7a7c8c78 by Raymond Hettinger in branch '3.2': Issue

[issue11877] Mac OS X fsync() should really be fcntl(F_FULLFSYNC)

Charles-Francois Natali added the comment: I know that POSIX makes no guarantee regarding durable writes, but IMHO that's definitely wrong, in the sense that when one calls fsync, he expects the data to be committed to disk and be durable. Fixing this deficiency through Python's exposed fsync

[issue11849] ElementTree memory leak

Charles-Francois Natali added the comment: > BTW, after utilize lxml instead of ElementTree, such phenomenon of increasing > memory usage disappeared. If you looked at the link I posted, you'll see that lxml had some similar issues and solved it by calling malloc_trim systematically when free

[issue8426] multiprocessing.Queue fails to get() very large objects

Charles-Francois Natali added the comment: > IMO, it would be nice if I could ask my queue, "Just what is your capacity (in bytes, not entries) anyways? I want to know how much I can put in here without worrying about whether the remote side is dequeueing." I guess I'd settle for explicit docu

[issue10596] modulo operator bug

Raymond Hettinger added the comment: Uncle Timmy, was this the right thing to do? -- assignee: mark.dickinson -> tim_one nosy: +rhettinger, tim_one ___ Python tracker ___ __

[issue11880] add a {dist-info} category to distutils2

Éric Araujo added the comment: This feature is two-fold: add a method to install_distinfo to make it write some data in some file; add a new resource category. -- assignee: tarek -> eric.araujo ___ Python tracker

[issue11875] OrderedDict.__reduce__ not threadsafe

Roundup Robot added the comment: New changeset 3150b6939731 by Raymond Hettinger in branch '2.7': Issue 11875: Keep OrderedDict's __reduce__ from temporarily mutating the object. http://hg.python.org/cpython/rev/3150b6939731 -- nosy: +python-dev ___

[issue828450] sdist generates bad MANIFEST on Windows

Éric Araujo added the comment: > I'm not sure it is necessary to use TempdirManager here to write tests > for MANIFEST reading. Well, the sdist command has to run on some directory where some files exist, right? So it’s better to do it in a temp dir that will automatically get cleaned up. >

[issue11880] add a {dist-info} category to distutils2

New submission from dholth : In distutils2 there is currently no way to add files such as egg_info.txt that should be part of the package metadata. A new category named the same as the .dist-info directory would be a nice way to do it. distutils2 should raise an error if any of the reserved fi

[issue828450] sdist generates bad MANIFEST on Windows

higery added the comment: I'm not sure it is necessary to use TempdirManager here to write tests for MANIFEST reading. The attachment is the test diff file against my last patch with the latest version. Detail: Step 1: Write sample MANIFEST strings to the MANIFEST file with '/' as separator

[issue10932] distutils.core.setup - data_files misbehaviour ?

Éric Araujo added the comment: Can you remove all obsolete repositories and patches from this report and upload one complete patch? -- ___ Python tracker ___ __

[issue11879] TarFile.chown: should use TarInfo.uid if user lookup fails

New submission from Michael Gold : In TarFile.chown, if the lookup u = pwd.getpwnam(tarinfo.uname)[2] fails, this line is used: u = pwd.getpwuid(tarinfo.uid)[2] This will fail if the uid isn't in /etc/passwd. I think "u = tarinfo.uid" would make more sense. This fallback could also be use

[issue8933] Invalid detection of metadata version

Éric Araujo added the comment: “I’m putting this on standby until distutils2 is fully merged into the standard library and we have a clear workflow from packaging to d2 to d1.” -- ___ Python tracker __

[issue11867] Make test_mailbox deterministic

R. David Murray added the comment: I think the fix is to either put a try/except around the socket shutdown call, or to remove it entirely (I think things will still work right on linux without it). If you leave the self.c_sock_close = True in, it should take care of the resource warning. -

[issue11877] Mac OS X fsync() should really be fcntl(F_FULLFSYNC)

Ronald Oussoren added the comment: Traditionally the functions in os are thin wrappers around OS functions, this patch changes that for os.fsync. Two nits wrt. the patch itself: 1) The behaviour on OSX should be documented in the stdlib reference, that currently says that os.fsync will cal

[issue11223] interruption of locks by signals not guaranteed when the semaphore implementation is not used

Antoine Pitrou added the comment: > Yeah, I know. My patch should be updated if #11863 is fixed before this issue. > > Updated patch: > - add 'pthread_version' key to threading._info() > - test_os uses threading._info() to check if we are using linuxthreads The path which sets "pthread_versi

[issue11223] interruption of locks by signals not guaranteed when the semaphore implementation is not used

STINNER Victor added the comment: Example on my Debian Sid: >>> threading._info() {'pthread_version': 'NPTL 2.11.2', 'use_semaphores': True, 'name': 'pthread'} -- ___ Python tracker __

[issue11858] configparser.ExtendedInterpolation and section case

Changes by Éric Araujo : -- nosy: +eric.araujo stage: -> test needed versions: +Python 3.3 ___ Python tracker ___ ___ Python-bugs-lis

[issue11223] interruption of locks by signals not guaranteed when the semaphore implementation is not used

STINNER Victor added the comment: > Most of these names will be removed in 3.3: > http://bugs.python.org/issue11863 Yeah, I know. My patch should be updated if #11863 is fixed before this issue. Updated patch: - add 'pthread_version' key to threading._info() - test_os uses threading._info()

[issue11863] Enforce PEP 11 - remove support for legacy systems

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

[issue11276] 2to3: imports fixer doesn't update references to modules specified without attributes

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

[issue9896] Introspectable range objects

Éric Araujo added the comment: Looks good, apart from the use of assertEquals (deprecated in favor of assertEqual). I’d also remove “merely” from the doc addition. -- nosy: +eric.araujo ___ Python tracker ___

[issue8982] argparse docs cross reference Namespace as a class but the Namespace class is not documented

Éric Araujo added the comment: Attached patch adds a link target for :class:`Namespace` (already used in the docs) and adds a reference to it from for the first mentions of “namespace object”. Use “hg import blah.diff” (after “hg up 3.2”) to get the patch in the repo directly (with checkin m

[issue11878] No SOAP libraries available for Python 3.x

Brian Curtin added the comment: This is something that should be handled on the trackers of any of the external SOAP libraries. If they are ported to Python 3 and are seen as best in class and are willing to move all development into the standard library, then inclusion could be considered.

[issue11878] No SOAP libraries available for Python 3.x

New submission from Michiel Van den Berghe : There doesn't seem to exist a SOAP library for Python 3.x. Several different third party libraries exist for the 2.x releases, but none of these are being ported to 3.x. None of these modules are easily ported using 2to3 due to string encoding issue

[issue11877] Mac OS X fsync() should really be fcntl(F_FULLFSYNC)

STINNER Victor added the comment: Oh, it remembers a long story around ext3/ext4 and write barrier, with a specific problem in Firefox with SQLite. http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/man2/fsync.2.html " For applications that require tighter guar

[issue11837] smtplib._quote_periods triggers spurious type error in re.sub

Axel Rau added the comment: One more hint: The bug does not happen with plain text mails, but can easily be reproduced with MIME attachments. -- ___ Python tracker ___

[issue11867] Make test_mailbox deterministic

Steffen Daode Nurpmeso added the comment: Short glance into it, and after commenting out self.c_sock_close = self.c_sock_shutdown = True in the parent process it ends up as (maybe i can spend more time this evening): 15:36 ~/tmp $ python3 -E -Wd -m test -r -w -uall test_mailbox Using rand

[issue11863] Enforce PEP 11 - remove support for legacy systems

STINNER Victor added the comment: FYI Hurd only supports cthread, without cthread support, Python will not support threads on Hurd anymore. There are two Hurd issues to move from cthread to pthread http://savannah.gnu.org/task/?5487 (opened 5 years ago) http://savannah.gnu.org/task/?7895 (open

[issue8933] Invalid detection of metadata version

Filip Gruszczyński added the comment: Bump! How about commiting this patch, Eric? -- status: pending -> open ___ Python tracker ___ __

[issue11863] Enforce PEP 11 - remove support for legacy systems

STINNER Victor added the comment: Patch removing cpthread, pth, lwp and solaris thread implementations. The patch on configure.in, around the following diff, is invalid: AC_DEFINE(_REENTRANT) -AC_CHECK_HEADER(cthreads.h, [AC_DEFINE(WITH_THREAD) -AC_DEFINE(C_THREADS) -AC_DE

[issue10932] distutils.core.setup - data_files misbehaviour ?

Prashant Kumar added the comment: If I'm not wrong, the contents in the manifest file should be: 'data.cfg' (not cfg/data.cgg) I've added a patch which fixes the above issue. -- Added file: http://bugs.python.org/file21721/fix-manifest.diff ___ Pyt

[issue11867] Make test_mailbox deterministic

R. David Murray added the comment: Thanks for testing this. I was afraid something like that would happen, since socket implementations are different on different platforms. I presume you ran it on OSX. Now I have to decide if I want to fix it, or if I should just switch to using threads.

[issue10932] distutils.core.setup - data_files misbehaviour ?

Changes by Prashant Kumar : Added file: http://bugs.python.org/file21720/test_command_sdist.diff ___ Python tracker ___ ___ Python-bugs-list m

[issue1294232] Error in metaclass search order

Nick Coghlan added the comment: Sorry, my last review wasn't right and the patch is incorrect as it stands. After digging a little deeper, there is still a case that isn't covered correctly in __build_class__. Specifically, the case where the most derived class has a declared metatype that i

[issue1294232] Error in metaclass search order

Nick Coghlan added the comment: Removed 2.7 from the affected versions - with neither __build_class__ nor __prepare__ in 2.x, there's no alternate metaclass calculation to go wrong. This should definitely be fixed for the final 3.1 release and for 3.2 though. An updated patch against current

[issue11867] Make test_mailbox deterministic

Steffen Daode Nurpmeso added the comment: Nice ping pong you play.. I, buildbot get: Using random seed 2215045 [1/1] test_mailbox test test_mailbox failed -- multiple errors occurred; run in verbose mode for details test test_mailbox failed -- Traceback (most recent call last): File "/Users/

[issue1294232] Error in metaclass search order

Nick Coghlan added the comment: Yep, the leading underscore and the fact you added it to a block of code that is skipped when Py_LIMITED_API is defined makes it OK to include the prototype in object.h. However, I would suggest _PyType_CalculateMetaclass as the name - CalculateWinner is a bit

[issue11863] Enforce PEP 11 - remove support for legacy systems

STINNER Victor added the comment: Issue #11876 has been marked as a duplicate of this issue. -- nosy: +haypo ___ Python tracker ___ _

[issue11876] SGI Irix threads, SunOS lightweight processes, GNU pth threads, Mach C Threads are now unsupported, and code will be removed in 3.3

STINNER Victor added the comment: Oh, this is a duplicate of #11863. -- resolution: -> duplicate status: open -> closed ___ Python tracker ___ _

[issue11223] interruption of locks by signals not guaranteed when the semaphore implementation is not used

Antoine Pitrou added the comment: > threading_info.patch: > - Add thread._info() function -> dict with 'name' and > 'use_semaphores' (pthread only) keys Most of these names will be removed in 3.3: http://bugs.python.org/issue11863 -- ___ Python tra

[issue11750] Mutualize win32 functions

Brian Curtin added the comment: For the first point, I just put it there since other Windows-only modules already exist there. _subprocess did, msvcrt and winreg currently do, and there's a few other Windows-only things in there. It's not a big deal, so I can move it into Modules if we want -

[issue11277] Crash with mmap and sparse files on Mac OS X

STINNER Victor added the comment: > (My last reply-mail changed the title. Fixing.) Yeah, it's a common problem if you use the email interface :-/ -- ___ Python tracker ___ __

[issue8271] str.decode('utf8', 'replace') -- conformance with Unicode 5.2.0

Ezio Melotti added the comment: Attached patch against 3.1 fixes the number of FFFD. A test for the range in the error message should probably be added. I haven't done any benchmark yet. There's some code duplication, but I'm not sure it can be factored out. -- versions: +Python 3.3

[issue11277] Crash with mmap and sparse files on Mac OS X

Steffen Daode Nurpmeso added the comment: (My last reply-mail changed the title. Fixing.) -- title: test_zlib.test_big_buffer crashes under BSD (Mac OS X and FreeBSD) -> Crash with mmap and sparse files on Mac OS X ___ Python tracker

[issue11277] test_zlib.test_big_buffer crashes under BSD (Mac OS X and FreeBSD)

Steffen Daode Nurpmeso added the comment: On Tue, Apr 19, 2011 at 10:34:11AM +, STINNER Victor wrote: > 11277.3.diff: this patch looks correct Unbelievable - you really fought yourself through this immense bunch of code in such a short time! :) -- title: Crash with mmap and sparse

[issue11877] Mac OS X fsync() should really be fcntl(F_FULLFSYNC)

Changes by Nadeem Vawda : -- nosy: +nadeem.vawda ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue11877] Mac OS X fsync() should really be fcntl(F_FULLFSYNC)

New submission from Steffen Daode Nurpmeso : Issue 11277 revealed that Mac OS X fsync() does not always and gracefully synchronize file data to physical backing store. To gain real fsync(2) behaviour fcntl(2) must be called with the F_FULLFSYNC flag. -- components: Library (Lib) files: f

[issue11300] mmap() large file failures on Mac OS X docfix

Steffen Daode Nurpmeso added the comment: Outdated due to found #11277 solution. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue11277] Crash with mmap and sparse files on Mac OS X

Steffen Daode Nurpmeso added the comment: Updated 11277.4.diff also includes mmap.rst update. (Maybe os.fsync() and os.sync() should be modified to really do that fcntl, too? I'll think i'll open an issue with patch soon.) -- Added file: http://bugs.python.org/file21717/11277.4.diff _

[issue11876] SGI Irix threads, SunOS lightweight processes, GNU pth threads, Mach C Threads are now unsupported, and code will be removed in 3.3

Changes by Jesús Cea Avión : -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue11277] Crash with mmap and sparse files on Mac OS X

STINNER Victor added the comment: Oh, and can you add a comment explaining why F_FULLFSYNC is needed on Mac OS X in your patch? (If I understood correctly, it is needed to avoid crash with sparse files). -- ___ Python tracker

  1   2   >