gdbm is broken and as a result breaks dbm/shelve (dbm.open fails)
Don't include it so the dbm.dumb backend is used instead,
like with the official CPython build.
CPython uses isatty() to detect a terminal and change some settings
like line buffering and interactive mode. Use is_cygpty() to make
this also work under mintty.
See https://github.com/Alexpux/MINGW-packages/issues/2645
This also removes the bash script which forced the interactive mode
when python3 was started without arguments. This is no longer needed as
Python now detects the terminal output and does this automatically.
Also use is_cygpty() to detect when not under mintty and disable the readline
module there, as using it breaks input of certain characters and
leads to errors on shutdown when it tries to save the readline history.
(The readline module is not available in the official Python build)
See https://github.com/Alexpux/MINGW-packages/issues/2656
With non-mingw builds POSIX_SEMAPHORES_NOT_ENABLED is not enabled and
sem_unlink is a no-op. Change it to always be provided on Windows instead.
This adds a minimal test suite which makes it easier to catch regressions
in the future for common MSYS2 related bugs.
* python3: Update to 3.6.1
The patches starting with 16 are new to fix the build.
Some no longer relevant patches were dropped, the rest is just refreshed.
* Bump pkgrel of all packages containing Python 3 bytecode/extensions.
The package list was generated using:
pkgfile.exe -R mingw64 -r "cpython.*\\.(py[cod]|dll)"
* lensfun: Add cmake to makedepends
* numpy: Don't hardcode the Python version
* blender: rebuild for new Python
* boost: Don't hardcode Python versions; rebuild
* pillow: Don't hardcode Python version; rebuild
* python-dateutil: Don't hardcode Python versions
* sip: Don't hardcode Python versions
* pyqt4: Don't hardcode Python versions; rebuild
* pyqt5: Don't hardcode Python versions; rebuild
* opencv: Update Python3 version in patch
On Windows XP SP3 there is no GetTickCount64, current workaround for this problem has a bug: ```GetProcAddress(hKernel32, "GetTickCount64")``` returns ```NULL```, but next if compares result with ```-1``` and so it tries to call function by ```NULL``` address. This leads to segfault.
* readline - 7.0 - Update to latest veersion - NOTE: Will probably break stuff - rebuild what depends upon it
Rekeyed patch for new version and ifdef'ed out chown calls if not
available
* Rebuild some packages that depend upon readline for good measure
* upgrade some broken packages
* correct some broken urls/checksums
* use secure urls where possible
* update PKGBUILD templates
* remove line-ending whitespace
* minor typos/fixes
Remaining md5sums either didn't download or
didn't pass checksum tests.
* Update python2 to 2.7.11
* Update numpy to 1.10.2 (and number the patches).
* New python2 + 3 patch so that sys.version returns
something more similar to normal CPython so that
get_build_architecture in distutils msvccompiler.py
returns the right thing (NumPy uses it so there's
every chance other things will too).
Implement _nt_quote_args using subprocess module's
list2cmdline since that handles all the tricky quoting
logic properly while the previous implementation was
not capable of handling anything more complicated than
the most basic commandline arguments and those with
spaces (so no tabs, or double quotes etc).
A specific example of trouble this caused was on MSYS2
when building the gobject-introspection part of GEGL 0.3.4
and a macro of -DG_LOG_DOMAIN="GEGL"-__FILE__ was passed
to the C compiler. From distutils perspective, the final
call ended up as:
gegl-introspection-module =
Extensions('gegl-introspection',
define_macros=
[('G_LOG_DOMAIN', '"GEGL-"__FILE__')])
This *will* cause trouble in software that special-cased
Windows. An example existed in Python's own setup.py when
building the sqlite module.
The MODULE_NAME define was set to '"sqlite3"' for everything
else and to '\\"sqlite3\\"' for Windows. This commit removes
this special-casing, obviously!
The bad-old-implementation has existed for so long now that
everyone's hacked around it, which means that it's probably
too late for this change, so this means in the long-term,
this commit will go one of three ways:
1. It'll stay in and we'll fix everything up that's broken.
pip and C extensions will screw up badly here.
2. I implement a two-pass scheme where I try both the old
way and the new way for things that fail on first attempt.
3. I remove this altogether, and hack up GEGL like everything
else has been hacked up, lesson learnt.
I'm leaning towards 2 at present.
Either way, I need to figure out why GEGL was hanging before
this change as that was less than useful. Some good came out
of it; we can build debuggable python2 and py-bt works now
too!
Also renamed python-gdb.py to python_gdb.py
Alexey Pavlov
Christoph Reiter
K.Takata
Nikolay Polyarniy
Andrew Dutcher
J. Peter Mugaas
Viktor Szakats
Ray Donnelly