summaryrefslogtreecommitdiffstats
path: root/Modules/posixmodule.c
Commit message (Collapse)AuthorAgeFilesLines
* - Issue #7658: Ensure that the new pythonw executable works on OSX 10.4Ronald Oussoren2010-01-171-0/+4
| | | | | | | | | | | | - Issue #7714: Use ``gcc -dumpversion`` to detect the version of GCC on MacOSX. - Make configure look for util.h as well as libutil.h. The former is the header file that on OSX contains the defition of openpty. (Needed to compile for OSX 10.4 on OSX 10.6) - Use the correct definition of CC to compile the pythonw executable
* Fix possible integer overflow in lchown and fchown functions. For issue1747858.Gregory P. Smith2009-12-231-4/+5
|
* Issue #7333: The `posix` module gains an `initgroups()` function providingAntoine Pitrou2009-12-021-0/+27
| | | | | access to the initgroups(3) C library call on Unix systems which implement it. Patch by Jean-Paul Calderone.
* Issue #6508: Add posix.{getresuid,getresgid,setresuid,setresgid}.Martin v. Löwis2009-11-271-0/+89
|
* Fix issue #1590864, multiple threads and fork() can cause deadlocks, byThomas Wouters2009-09-161-3/+31
| | | | | | | | | | | | | | | | | | | | | | acquiring the import lock around fork() calls. This prevents other threads from having that lock while the fork happens, and is the recommended way of dealing with such issues. There are two other locks we care about, the GIL and the Thread Local Storage lock. The GIL is obviously held when calling Python functions like os.fork(), and the TLS lock is explicitly reallocated instead, while also deleting now-orphaned TLS data. This only fixes calls to os.fork(), not extension modules or embedding programs calling C's fork() directly. Solving that requires a new set of API functions, and possibly a rewrite of the Python/thread_*.c mess. Add a warning explaining the problem to the documentation in the mean time. This also changes behaviour a little on AIX. Before, AIX (but only AIX) was getting the import lock reallocated, seemingly to avoid this very same problem. This is not the right approach, because the import lock is a re-entrant one, and reallocating would do the wrong thing when forking while holding the import lock. Will backport to 2.6, minus the tiny AIX behaviour change.
* Issue #4856: Py_GetFileAttributesEx[AW] are not needed because ↵Hirokazu Yamamoto2009-06-291-58/+2
| | | | | | | GetFileAttributesEx[AW] won't fail with ERROR_CALL_NOT_IMPLEMENTED on win NT. Reviewed by Amaury Forgeot d'Arc.
* Issue #4856: Remove checks for win NT.Hirokazu Yamamoto2009-06-281-324/+262
|
* Fix build under WindowsAntoine Pitrou2009-05-241-3/+1
|
* Some pid_t-expecting or producing functions were forgotten in r72852.Antoine Pitrou2009-05-231-11/+17
|
* Issue #1983: Fix functions taking or returning a process identifier to useAntoine Pitrou2009-05-231-16/+35
| | | | | the dedicated C type `pid_t` instead of a C `int`. Some platforms have a process identifier type wider than the standard C integer type.
* Issue #3527: Removed Py_WIN_WIDE_FILENAMES which is not used any more.Hirokazu Yamamoto2009-05-171-33/+25
|
* Issue #5913: os.listdir() should fail for empty path on windows.Hirokazu Yamamoto2009-05-041-6/+7
|
* Fixes issue5705: os.setuid() and friends did not accept the same range ofGregory P. Smith2009-04-051-17/+55
| | | | values that pwd.getpwnam() returns.
* http://bugs.python.org/issue5623Kristján Valur Jónsson2009-04-011-33/+24
| | | | | Dynamically discoverd the size of the ioinfo struct used by the crt for its file descriptors. This should work across all flavors of the CRT. Thanks to Amaury Forgeot d'Arc Needs porting to 3.1
* Issue #5341: Fix a variety of spelling errors.Mark Dickinson2009-02-211-2/+2
|
* Issue 4804. Add a function to test the validity of file descriptors on ↵Kristján Valur Jónsson2009-02-101-1/+125
| | | | Windows, and stop using global runtime settings to silence the warnings / assertions.
* simplify codeBenjamin Peterson2009-01-191-4/+2
|
* Issue 4957Kristján Valur Jónsson2009-01-191-1/+1
| | | | Let os.ftruncate raise OSError like documented.
* Issue #1040026: Fix os.times result on systems where HZ is incorrect.Martin v. Löwis2008-12-291-9/+16
|
* Issue #4071: ntpath.abspath returned an empty string for long unicode path.Hirokazu Yamamoto2008-11-081-6/+20
|
* removed unused _PyUnicode_FromFileSystemEncodedObject.Hirokazu Yamamoto2008-10-161-6/+2
| | | | made win32_chdir, win32_wchdir static.
* r66862 contained memory leak.Hirokazu Yamamoto2008-10-091-1/+3
|
* On windows, os.chdir given unicode was not working if GetCurrentDirectoryWHirokazu Yamamoto2008-10-091-1/+4
| | | | | returned a path longer than MAX_PATH. (But It's doubtful this code path is really executed because I cannot move to such directory on win2k)
* Issue #2222: Fixed reference leak when occured os.rename()Hirokazu Yamamoto2008-08-171-28/+26
| | | | fails unicode conversion on 2nd parameter. (windows only)
* Issue #3139: Make buffer-interface thread-safe wrt. PyArg_ParseTuple,Martin v. Löwis2008-08-121-3/+4
| | | | | | | by denying s# to parse objects that have a releasebuffer procedure, and introducing s*. More module might need to get converted to use s*.
* On Windows, silence a Purify warning and initialize the memory passed to ↵Amaury Forgeot d'Arc2008-07-211-0/+1
| | | | | | CryptGenRandom. Since python doesn't provide any particular random data, it seems more reasonable anyway.
* #1608818: errno can get set by every call to readdir().Georg Brandl2008-07-161-8/+10
|
* Fix posix.fork1() / os.fork1() to only call PyOS_AfterFork() in the childGregory P. Smith2008-07-141-1/+2
| | | | | | | | process rather than both parent and child. Does anyone actually use fork1()? It appears to be a Solaris thing but if Python is built with pthreads on Solaris, fork1() and fork() should be the same.
* Issue #2722. Now the char buffer to support the path string hasFacundo Batista2008-06-221-5/+24
| | | | | not fixed length, it mallocs memory if needed. As a result, we don't have a maximum for the getcwd() method.
* This reverts r63675 based on the discussion in this thread:Gregory P. Smith2008-06-091-34/+34
| | | | | | | http://mail.python.org/pipermail/python-dev/2008-June/079988.html Python 2.6 should stick with PyString_* in its codebase. The PyBytes_* names in the spirit of 3.0 are available via a #define only. See the email thread.
* Renamed PyString to PyBytesChristian Heimes2008-05-261-34/+34
|
* #2890: support os.O_ASYNC and fcntl.FASYNC.Georg Brandl2008-05-161-0/+5
|
* Fix chown on 64-bit linux. It needed to take a long (64-bit on 64bit linux) asGregory P. Smith2008-03-181-2/+2
| | | | | | | | | uid and gid input to accept values >=2**31 as valid while still accepting negative numbers to pass -1 to chown for "no change". Fixes issue1747858. This should be backported to release25-maint.
* Remove all traces of HAVE_STRERROR.Brett Cannon2008-03-181-4/+0
| | | | | The removal of strerror.c led to the function check being removed from configure.in.
* #2063: correct order of utime and stime in os.times()Georg Brandl2008-02-131-2/+2
| | | | result on Windows.
* Another int -> pid_t caseChristian Heimes2008-02-031-1/+2
|
* The wrapper function is supposed to be for spawnvpe() so that'sAndrew MacIntyre2008-02-031-2/+2
| | | | | | what we should call [this wrapper only available on OS/2]. Backport candidate to 2.5.
* More int -> pid_t.Christian Heimes2008-02-011-11/+18
|
* Fixed bug #1983: Return from fork() is pid_t, not intChristian Heimes2008-01-311-6/+7
|
* #1663329: add os.closerange() to close a range of fds,Georg Brandl2008-01-191-0/+19
| | | | | ignoring errors, and use this in subprocess to speed up subprocess creation in close_fds mode. Patch by Mike Klaas.
* Modified PyImport_Import and PyImport_ImportModule to always use absolute ↵Christian Heimes2008-01-031-1/+1
| | | | | | imports by calling __import__ with an explicit level of 0 Added a new API function PyImport_ImportModuleNoBlock. It solves the problem with dead locks when mixing threads and imports
* #1629: Renamed Py_Size, Py_Type and Py_Refcnt to Py_SIZE, Py_TYPE and ↵Christian Heimes2007-12-191-1/+1
| | | | Py_REFCNT. Macros for b/w compatibility are available.
* Forward-port r59310:Martin v. Löwis2007-12-031-2/+5
| | | | os.access now returns True on Windows for any existing directory.
* Fix for feature request #1528 Add os.fchmodChristian Heimes2007-11-301-0/+83
| | | | | Georg Brandl has added fchmod() and fchown(). I've contributed lchown but I'm not able to test it on Linux. However it should be available on Mac and some other flavors of Unix. I've made a quick test of fchmod() and fchown() on my system. They are working as expected.
* #1735632: add O_NOATIME constant to os module.Georg Brandl2007-11-241-0/+4
| | | | Also document a few other O_ constants that were missing from documentation.
* Document that we rely on the OS to release the cryptoMartin v. Löwis2007-09-041-0/+2
| | | | context. Fixes #1626801.
* Fix memory leak in os.readlinkNeal Norwitz2007-08-121-2/+6
|
* PEP 3123: Provide forward compatibility with Python 3.0, while keepingMartin v. Löwis2007-07-211-1/+1
| | | | | backwards compatibility. Add Py_Refcnt, Py_Type, Py_Size, and PyVarObject_HEAD_INIT.
* Fix problems in x64 build that were discovered by the testsuite:Kristján Valur Jónsson2007-05-031-1/+0
| | | | | | | | | | | | - Reenable modules on x64 that had been disabled aeons ago for Itanium. - Cleared up confusion about compilers for 64 bit windows. There is only Itanium and x64. Added macros MS_WINI64 and MS_WINX64 for those rare cases where it matters, such as the disabling of modules above. - Set target platform (_WIN32_WINNT and WINVER) to 0x0501 (XP) for x64, and 0x0400 (NT 4.0) otherwise, which are the targeted minimum platforms. - Fixed thread_nt.h. The emulated InterlockedCompareExchange function didn´t work on x64, probaby due to the lack of a "volatile" specifier. Anyway, win95 is no longer a target platform. - Itertools module used wrong constant to check for overflow in count() - PyInt_AsSsize_t couldn't deal with attribute error when accessing the __long__ member. - PyLong_FromSsize_t() incorrectly specified that the operand were unsigned. With these changes, the x64 passes the testsuite, for those modules present.
* Stop using PyMem_FREE while the GIL is not held. For details see:Neal Norwitz2007-05-021-1/+1
| | | | http://mail.python.org/pipermail/python-dev/2007-May/072896.html