aboutsummaryrefslogtreecommitdiff
path: root/lang/python/python-pycparser
Commit message (Collapse)AuthorAge
* python-packages: Clean up MakefilesJeffery To2020-04-22
| | | | | | | | | | | | | | | | | | | This removes: * Python 3 variants (VARIANT:=python3) * "for Python3" from package titles * Package selection condition from package dependencies, e.g. +PACKAGE_python3-six:python3-light replaced with +python3-light * "Default" package information sections, e.g. Package/python-six/Default removed and package details merged into Package/python3-six * "(Variant for Python3)" from package descriptions Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* python-libraries: Remove Python 2 variantsJeffery To2020-04-02
| | | | | | The Python 2 variants will be added to the abandoned packages feed. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* python-pycparser: Update to 2.20Jeffery To2020-03-16
| | | | Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* 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>
* multiple-python-packages: Update package dataJeffery To2019-02-20
| | | | | | | | | | | This updates the Python 2 and 3 versions of each package to share the same title field. (For packages that only had this change, their PKG_RELEASE were not incremented.) This also updates the package title, url and source urls, where necessary. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* python-pycparser: Update to 2.19Rosen Penev2018-11-14
| | | | Signed-off-by: Rosen Penev <rosenp@gmail.com>
* python-*,python3-*: add src packages for multiple packagesJeffery To2018-01-15
| | | | Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* treewide: use local python-package.mk & python3-package.mk filesAlexandru Ardelean2018-01-10
| | | | | | | | | | This guarantees for the package feeds that the mk files will always be available for all packages. Will need to see about external-feed Python packages a bit later. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* python-pycparser: update to 2.18, fix _build_tables errorJeffery To2018-01-11
| | | | Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* python-pycparser: bump to version 2.17 and drop host-buildAlexandru Ardelean2017-07-19
| | | | Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* python packages: move all things python under lang/pythonAlexandru Ardelean2017-05-17
I admit this may be be a bit aggressive, but the lang folder is getting cluttered/filled up with Python, PHP, Perl, Ruby, etc. packages. Makes sense to try to group them into per-lang folders. I took the Pythons. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
Powered by cgit, Themed by Ted Yin.