aboutsummaryrefslogtreecommitdiff
path: root/lang/python
Commit message (Collapse)AuthorAge
* treewide: Use pypi.mk for Python packagesJeffery To2019-10-30
| | | | | | | | | | | | | This updates all Python packages that download their source from PyPi to use pypi.mk. This will allow future improvements/changes to pypi.mk to affect all relevant packages. This also makes it easier for future Python packages to start using pypi.mk, when it's clear how it is used in existing packages. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* Merge pull request #10387 from commodo/cffi-updateRosen Penev2019-10-29
|\ | | | | python-cffi: bump to version 1.13.1
| * python-cffi: bump to version 1.13.1Alexandru Ardelean2019-10-29
| | | | | | | | Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* | Merge pull request #10386 from commodo/pillow-updateRosen Penev2019-10-29
|\ \ | | | | | | pillow: bump to version 6.2.1
| * | pillow: bump to version 6.2.1Alexandru Ardelean2019-10-29
| |/ | | | | | | Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* / django1: bump to version 1.11.25Alexandru Ardelean2019-10-29
|/ | | | Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* Merge pull request #10349 from dynasticorpheus/pytz-2019.03Hannu Nyman2019-10-26
|\ | | | | python-pytz: update to 2019.03
| * python-pytz: update to 2019.03Fabian Lipken2019-10-24
| | | | | | | | Signed-off-by: Fabian Lipken <dynasticorpheus@gmail.com>
* | python-asn1crypto: bump to version 1.2.0Alexandru Ardelean2019-10-25
|/ | | | Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* django: split django1 package and update to 2.2.6Alexandru Ardelean2019-10-24
| | | | | | | | | | | | | | | | | After many failed attempts at upgrading Django to 2.2.6, the solution seems to be to split a `python-django1` package that works with Python2 and upgrade `python3-django` to the latest 2.2[.6] LTS release. This also means that all Python2 Django packages will be stuck & based on Django 1.11[.24] LTS release. But, it's currently the sanest approach I could find to be able to perform an upgrade of Django to 2.2, and not break Seafile. Upgrading Seafile is also pretty difficult, as their Python3 support is not yet finished & released. And in the meantime, we want to allow people to use newer Django versions. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* Merge pull request #10322 from jefferyto/python-2.7.17Hannu Nyman2019-10-21
|\ | | | | python: Update to 2.7.17, refresh patches
| * python: Update to 2.7.17, refresh patchesJeffery To2019-10-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Patches already merged and so removed: * 011-fix-ssl-build-use-have-npn.patch * 019-bpo-36216-Add-check-for-characters-in-netloc-that-normalize-to-separators-GH-12216.patch * 020-bpo-36216-Only-print-test-messages-when-verbose-GH-12291.patch * 021-2.7-bpo-35121-prefix-dot-in-domain-for-proper-subdom.patch * 022-bpo-30458-Disallow-control-chars-in-http-URLs-GH-13315.patch * 023-bpo-35907-Avoid-file-reading-as-disallowing-the-unnecessary-URL-scheme-in-urllib-GH-11842.patch * 027-bpo-38243-Escape-the-server-title-of-DocXMLRPCServer.patch * 028-bpo-34155-Dont-parse-domains-containing-GH-13079.patch Patches no longer necessary and so removed: * 017_lib2to3_fix_pyc_search.patch Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* | Merge pull request #10314 from commodo/python-3-8Hannu Nyman2019-10-21
|\ \ | | | | | | python3: bump to version 3.8
| * | python3: bump to version 3.8Alexandru Ardelean2019-10-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This required a bit work to get working, compared to other versions. So, some things have changed a bit more significantly. Some highlights: * there is no longer a pgen executable, seems this is now part of libpython; let's see what this means for us in the future * blake2 hash (from OpenSSL) detection needs some fixing; will upstream added patch 002-fix-blake2-detection.patch * removed all bpo patches; those should be fixed in upstream * some needed to be manually re-applied as stuff changed: - 001-enable-zlib.patch - file changed - 004-do-not-write-bytes-codes.patch - file changed - 015-abort-on-failed-modules.patch - variable was renamed cross_compiling -> CROSS_COMPILING * 017_lib2to3_fix_pyc_search.patch - the code changed, it does not seem to have the original problem with respect to file-extension, as there does not seem to be any special extension logic anymore there * 006-remove-multi-arch-and-local-paths.patch - dropped patch; I can't remember the full-details of this issue; it was something with Debian/Ubuntu's multi-arch stuff; it was probably added maybe due to some overzealous (on my part) thingy caused by some weird reports, that I could never solve; let's have this patch dropped and see * make package/python3/refresh to reduce fuzz for the rest Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* | | python,python3: Add PYPI_SOURCE_NAME to pypi.mkJeffery To2019-10-21
| |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | This adds a new (optional) variable, PYPI_SOURCE_NAME, to pypi.mk. For some PyPi packages (e.g. aiohttp_cors, click, django-compressor), the name of the package and the source tarball name are slightly different (usually by capitalisation or hyphen/underscore change). This new variable is to make this difference explicit. PYPI_NAME is meant for the "official" package name, whereas PYPI_SOURCE_NAME is meant for the source tarball name. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* | python-ipaddress: Update to 1.0.23Jeffery To2019-10-21
| | | | | | | | Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* | python-automat: Update to 0.8.0Jeffery To2019-10-21
| | | | | | | | Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* | python-attrs: Update to 19.3.0Jeffery To2019-10-21
| | | | | | | | Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* | python-cryptography: Update to 2.8Jeffery To2019-10-21
| | | | | | | | | | | | | | | | With this update, the package no longer depends on python-asn1crypto[1]. [1]: https://github.com/pyca/cryptography/blob/master/CHANGELOG.rst#28---2019-10-16 Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* | python-cffi: Update to 1.13.0Jeffery To2019-10-21
|/ | | | Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* Merge pull request #10242 from jefferyto/pypi-mkRosen Penev2019-10-18
|\ | | | | python,python3: Add pypi makefile
| * python,python3: Add pypi makefileJeffery To2019-10-19
| | | | | | | | | | | | | | | | | | | | | | This adds pypi.mk, which can be included in Python packages that download their sources from PyPI, to auto-fill various PKG_* variables based on the value of PYPI_NAME. This makefile should be included after $(TOPDIR)/rules.mk but before $(INCLUDE_DIR)/package.mk (and $(INCLUDE_DIR)/host-build.mk). Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* | python-pyasn1-modules: Update to 0.2.7Jeffery To2019-10-16
|/ | | | Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* Merge pull request #10181 from commodo/python-simple-json-drop-testsRosen Penev2019-10-14
|\ | | | | python[3]-simplejson: drop tests from simplejson package
| * python[3]-simplejson: drop tests from simplejson packageAlexandru Ardelean2019-10-08
| | | | | | | | | | | | These tests take-up a bit of space. And they aren't typically needed. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* | python-sentry-sdk: Update to version 0.12.3Josef Schlehofer2019-10-12
| | | | | | | | Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
* | Merge pull request #10182 from jefferyto/python-attrs-19.2.0Rosen Penev2019-10-09
|\ \ | | | | | | python-attrs: Update to 19.2.0
| * | python-attrs: Update to 19.2.0Jeffery To2019-10-09
| |/ | | | | | | Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* | Merge pull request #10187 from commodo/python-asn1crypto-updateRosen Penev2019-10-09
|\ \ | | | | | | python-asn1crypto: bump to version 1.0.1
| * | python-asn1crypto: bump to version 1.0.1Alexandru Ardelean2019-10-09
| |/ | | | | | | Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* / python-pillow: bump to version 6.2.0Alexandru Ardelean2019-10-09
|/ | | | Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* python,python3: Fix CVE-2019-16056, CVE-2019-16935Jeffery To2019-10-04
| | | | | | | | | | | | | | | These patches address issues: CVE-2019-16056: email.utils.parseaddr mistakenly parse an email CVE-2019-16935: A reflected XSS in python/Lib/DocXMLRPCServer.py (for Python 2.7) CVE-2019-16935 was fixed for python3 in #10109 Links to Python issues: https://bugs.python.org/issue34155 https://bugs.python.org/issue38243 Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* python-simplejson: Fix python[3]-decimal dependencyJeffery To2019-10-04
| | | | | | | | | | simplejson depends on the decimal module[1][2]. This adds python[3]-decimal to the package's DEPENDS. [1]: https://github.com/simplejson/simplejson/blob/v3.16.0/simplejson/__init__.py#L110 [2]: https://github.com/simplejson/simplejson/blob/v3.16.0/simplejson/encoder.py#L7 Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* Merge pull request #10121 from BKPepe/werkzeugRosen Penev2019-10-02
|\ | | | | Werkzeug: Update to version 0.16.0
| * Werkzeug: Update to version 0.16.0Josef Schlehofer2019-10-01
| | | | | | | | | | | | | | | | | | | | - Remove PKG_BUILD_DEPENDS as it is no longer necessary. - The Python3 is already included in DEPENDS. - Remove PKG_BUILD_DIR and PKG_UNPACK was for dual Python version. - Change TITLE and description - Add source package Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
* | Merge pull request #10122 from BKPepe/flaskRosen Penev2019-10-02
|\ \ | | | | | | Flask: Update to version 1.1.1
| * | Flask: Update to version 1.1.1Josef Schlehofer2019-10-01
| |/ | | | | | | | | | | | | - Change TITLE and URL to better one - Add source package Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
* / python3-maxminddb: Update to version 1.5.1Josef Schlehofer2019-10-01
|/ | | | Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
* python-pyrsistent: Update to version 0.15.4Josef Schlehofer2019-09-30
| | | | Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
* python3: backport three security patchesJosef Schlehofer2019-09-29
| | | | | | Fixes: CVE-2019-16935 Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
* Merge pull request #10083 from BKPepe/sentrysdkRosen Penev2019-09-27
|\ | | | | python-sentry-sdk: Update to version 0.12.2
| * python-sentry-sdk: Update to version 0.12.2Josef Schlehofer2019-09-26
| | | | | | | | Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
* | python-cryptodome: update to 3.9.0Richard Yu2019-09-27
| | | | | | | | Signed-off-by: Richard Yu <yurichard3839@gmail.com>
* | python-urllib3: Update to version 1.25.6Josef Schlehofer2019-09-26
|/ | | | Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
* treewide: add PKG_CPE_ID for cvescannerJan Pavlinec2019-09-24
| | | | Signed-off-by: Jan Pavlinec <jan.pavlinec@nic.cz>
* gunicorn: convert to Python packaging format + add Python3 variantAlexandru Ardelean2019-09-20
| | | | | | | | | | | | | | | | | | | | | | | | | And splitting the gunicorn[3] binary/executable away from the python[3]-gunicorn libraries. This was inspired from Debian packaging. The gunicorn[3] binaries require the new `python[3]-pkg-resources` libraries to run, which add ~1.1 MB on the [ram]disk when uncompressed. For the Python2 variant, the `_gaiohttp.py` is dropped as it fails to compile, so it would likely be unusable anyway: ``` File "/usr/lib/python2.7/site-packages/gunicorn/workers/_gaiohttp.py", line 84 yield from self.wsgi.close() ^ SyntaxError: invalid syntax ``` People around the web recommend this as well: https://stackoverflow.com/questions/25611140/syntax-error-installing-gunicorn https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803170 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803202 Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* python,python3: add Py[3]Shebang functions & move outside of scriptAlexandru Ardelean2019-09-20
| | | | | | | | | | | | | | | | Some packages just install some Python binaries, that may need their shebang fixed. This change adds some utilities to help with that and try to centralize the sed rules a bit. It also removes the logic from the `python-package-install.sh` into the `python-package[3].mk` files. This does 2 things: 1. It minimizes the need for the shell script to know the Python version 2/3 2. Makes the logic re-usable in packages; especially if the install rules differ a bit Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* python,python3: split python[3]-pkg-resources from setuptoolsAlexandru Ardelean2019-09-20
| | | | | | | | | | This package is required by other packages to run some binaries via `load_entry_point`. So, this splits this package away from setuptools. setuptools is pretty big, akd pkg-resources is also big, but not as big. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* python: change condition check for legacy opt for Python3Alexandru Ardelean2019-09-20
| | | | | | | | As I remember this worked. But since `set -e` is set, I am a bit paranoid about it. In the sense that it may fail if `ver` != 3. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* python-certifi: bump to 2019.9.11Eneas U de Queiroz2019-09-19
| | | | Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
Powered by cgit, Themed by Ted Yin.