| Commit message (Collapse) | Author | Age |
|\
| |
| | |
python-automat: new package
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is a new requirement for the Twisted package.
From the readme:
Automat is a library for concise, idiomatic Python expression of
finite-state automata (particularly deterministic finite-state
transducers).
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
|
|\ \
| | |
| | | |
python-hyperlink: new package
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is a new requirement for the Twisted package.
From the readme:
Hyperlink provides a pure-Python implementation of immutable URLs. Based
on RFC 3986 and 3987, the Hyperlink URL makes working with both URIs and
IRIs easy.
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
|
|\ \
| | |
| | | |
python-incremental: new package
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is a new requirement for the Twisted package.
From the readme:
Incremental is a small library that versions your Python projects.
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
|
|\ \
| | |
| | | |
python-constantly: new package
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is a new requirement for the Twisted package.
From the readme:
A library that provides symbolic constant support. It includes
collections and constants with text, numeric, and bit flag values.
Originally twisted.python.constants from the Twisted project.
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There have been some new dependencies added in recent versions of
Twisted (mostly internal classes that have been spun out into their own
libraries):
* constantly (#5453), since 16.5.0
* incremental (#5454), since 16.5.0
* Automat (#5456), since 17.1.0
* hyperlink (#5455) since 17.5.0
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
|
| |
| |
| |
| |
| |
| |
| | |
For python `src` packages we should clear out the DEPENDS
to prevent recursive deps from happening.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
|\ \
| | |
| | | |
python,python3: add vars to customize setup arguments / variables
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This adds:
* PYTHON_PKG_SETUP_ARGS
* PYTHON_PKG_SETUP_VARS
* PYTHON3_PKG_SETUP_ARGS
* PYTHON3_PKG_SETUP_VARS
to customize Python package setup arguments / environment variables.
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
|
|/
|
|
|
|
|
| |
Related to:
https://github.com/openwrt/packages/issues/5424
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
|\
| |
| | |
python-txsocksx: use variant PyBuild/Compile syntax, add src package, refresh patches
|
| |
| |
| |
| |
| |
| | |
refresh patches
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
|
|\ \
| | |
| | | |
python-*,python3-*: add src packages for multiple packages
|
| | |
| | |
| | |
| | | |
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
|
|/ /
| |
| |
| | |
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
|
|\ \
| | |
| | | |
python,python3: honour the SOURCE_DATE_EPOCH for the build-info
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The Modules/getbuildinfo.c allows the use of DATE and TIME
macros to be defined via CFLAGS.
These vars, control the build date & time when the
interpreter is opened, and can be read via the
`platform._sys_version()` function.
So, a conversion from SOURCE_DATE_EPOCH to DATE & TIME
is required at build-time.
This is especially needed for `platform._sys_version()`
to work.
The installation of pip seems to rely on this.
The logic has been adapted from:
https://wiki.debian.org/ReproducibleBuilds/TimestampsProposal#Makefile
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
|\ \ \
| | | |
| | | | |
python-pyptlib: use default variant build/compile rule, add src package
|
| | |/
| |/|
| | |
| | | |
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
|
|\ \ \
| | | |
| | | | |
python-ipaddress: use default variant build/compile rule, add src package
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
package
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
|
|/ /
| |
| |
| | |
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
|
| |
| |
| |
| | |
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
|
|\ \
| | |
| | | |
zope-interface: update to 4.4.3, rename to python-zope-interface, add python3 variant
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
python3 variant
Renaming the package is needed to allow for a Python 3 variant
(python3-zope-interface). Packages that depend on this (only twisted)
also have their dependencies adjusted.
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
|
|/ /
| |
| |
| | |
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
|
|\ \
| | |
| | | |
treewide: re-organizing python-package.mk & python3-package.mk
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The only difference just a parameter for Python3
[ -b to compile bytecodes in legacy mode ].
No need to keep 2 almost identical files now
that they're exported.
I'm a bit scared of that param, since it may get
removed at some point.
But let's see until then.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Now that all files are exported, it makes sense
to just reference the script directly.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since `lang/python` is it's own folder of Python packages
(for both Python 2 & 3), and these build rules are needed
in a lot of packages [especially Python packages],
putting them here makes sense architecturally,
to be shared.
This also helps get rid of the `include_mk` construct
which relies on OpenWrt core to provide, and seems
like a broken design idea that has persisted for a while.
Reason is: it requires that Python 2/3 be built to provide
these mk files for other Python packages,
which seems like a bad idea.
Long-term, there could be an issue where some other feeds
would require these mk files [e.g. telephony] for
some Python packages.
We'll see how we handle this a bit later.
For now we limit this to this feed.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The .mk snippets are not really usable at the moment, as they cannot be
considered for metadata collection (package DUMP) when included through
include_mk. Python packages do not use include_mk anymore for this reason,
so the install commands can be removed as well.
Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
|
|/ /
| |
| |
| | |
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
|
|\ \
| | |
| | | |
python-pycparser: update to 2.18, fix _build_tables error
|
| | |
| | |
| | |
| | | |
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
|
|\ \ \
| | | |
| | | | |
python-pyasn1-modules: update to 0.2.1
|
| |/ /
| | |
| | |
| | | |
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
|
|\ \ \
| | | |
| | | | |
python-pyasn1: update to 0.4.2
|
| |/ /
| | |
| | |
| | | |
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
|
|\ \ \
| | | |
| | | | |
python-parsley: add python3 variant
|
| |/ /
| | |
| | |
| | | |
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
|
|\ \ \
| | | |
| | | | |
python-ipaddress: update to 1.0.19
|
| |/ /
| | |
| | |
| | | |
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
|
|\ \ \
| | | |
| | | | |
python-gmpy2: add python3 variant
|
| |/ /
| | |
| | |
| | | |
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
|
|\ \ \
| | | |
| | | | |
python-cryptography: update to 2.1.4, refresh patches
|
| |/ /
| | |
| | |
| | | |
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
|