| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
| |
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-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>
|
|/ /
| |
| |
| | |
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Build depends refer to source package names, not binary package names.
In many cases, PKG_BUILD_DEPENDS simply duplicated runtime dependencies of
a source package's binary packages; as the corresponding source packages
are implicitly added as bulid dependencies, PKG_BUILD_DEPENDS can simply be
dropped in these cases. In the other cases, *_BUILD_DEPENDS is fixed to
refer to the correct source package name.
Dependency of mysql-server is adjusted from libncursesw to libncurses
(as libncursesw is a virtual package provided by libncurses), so the build
dependency on ncurses is emitted unconditionally.
Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
|
|
|
|
|
|
|
|
|
|
| |
This reverts commits 4333d1dcbfd67dde4ca7d08717bc345cc424fbf8 and
074d2863be48c1a9093fffcda91f7a328bc7d0cb, making Python packages
discoverable again by pkg_resources.
Fixes #5361.
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 3c6d14021e62d68a7d9bdd4520b799c5c207fde1.
( which is a revert of commit c764f77dc1a62ce667b38520496ddb9bfaececab )
The initiall commit ( c764f77dc1a62ce667b38520496ddb9bfaececab )
was reverted, becase zlib did not have a host-build.
Now it does:
https://github.com/openwrt/openwrt/commit/cbe71649bc49ccc6ae96385482d0794c33336f68
So, now it should be good to put this in.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Re-worked patch `003-do-not-run-distutils-tests.patch`
to reduce patch-size.
Removed `011-fix-ncursesw-definition-colisions.patch`
it is fixed upstream.
Refreshed with `make package/python3/refresh`
Resetting PKG_RELEASE to 1.
This variable was never used for pip3 & setuptools, since
VERSION is specified in the package definitions.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
|\
| |
| | |
python,python3: add support for SOURCE_DATE_EPOCH var
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
See:
https://github.com/openwrt/packages/issues/5278
This should make Python & Python3 packages reproducible
when building.
In my local tests, I got the same sha256 for a sample
.pyc file, so likely this is the solution that should address
this.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
|/
|
|
|
|
|
|
|
|
| |
Fixes:
https://github.com/openwrt/packages/issues/5318
Not sure how this worked before.
The host python-cffi needs a libffi installed on the host side.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit c764f77dc1a62ce667b38520496ddb9bfaececab.
The commit caused warnings to be displayed at make defconfig etc.
WARNING: Makefile 'package/feeds/packages/python/python/Makefile'
has a host build dependency on 'zlib/host' but
'package/libs/zlib/Makefile' does not implement a 'host' build type
Signed-off-by: Hannu Nyman <hannu.nyman@iki.fi>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This should fix the zlibmodule build on the host side.
Usually, if zlib is not found, Python/Python3 builds fine
without it, but there are some cases where the Python/Python3
interpreter on the host-side requires zlib to run.
At the moment, zlib does not have a host-build.
This should be available when this PR gets merged:
https://github.com/lede-project/source/pull/1329
[ or a similar one that contains host-build support for zlib ].
In the meantime, this change can go into Python/Python3.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
|
|\
| |
| | |
python-curl: update to 7.43.0.1
|
| |
| |
| |
| | |
Signed-off-by: Waldemar Konik <informatyk74@interia.pl>
|