Closed GoogleCodeExporter closed 8 years ago
I looked briefly at this and it appears to be more complex than I had initially
hoped. Cygwin acts like a POSIX environment, but the system level code still
needs to
be Windows-specific. Unfortunately this means that most of the code is similar
to the
Windows codebase, but that the Cygwin version of Python doesn't know about
things
like PyErr_SetFromWindowsErr which we use all over the place. Conversely, the
/proc
system and sysctl() don't appear to be available under Cygwin so we can't use
the
code from other unix-like systems.
It's likely we'd need a separate cygwin C module specific to working with
Cygwin,
based on the Windows code but with workarounds for things like
PyErr_SetFromWindowsErr() and any other issues that crop up. Opening this
ticket as
an enhancement for a placeholder if/when we have a chance to look at this more
in depth.
Original comment by jlo...@gmail.com
on 20 Mar 2010 at 1:21
Issue 87 has been merged into this issue.
Original comment by jlo...@gmail.com
on 12 May 2010 at 4:29
I'm closing this out for now as it's unlikely we'll find time to look into this
in the near future.
Original comment by g.rodola
on 19 Jun 2010 at 6:14
Original issue reported on code.google.com by
jlo...@gmail.com
on 20 Mar 2010 at 1:17