@flipflop87 @mickael9: It was my .gitignore causing the issue this whole time. It's fixed now, sorry about that.

I can reproduce the issue flipflop97 has.

@flipflop87: If you can reproduce the issue with python-async-tkinter-loop as well, then it's something to do with python-poetry-core. Either way, both build fine in a chroot.

@flipflop97: I just built it in a clean chroot with no issues. I have it installed as a dependency for ognibuild and everything is working fine. Not sure what's happening on your end.

Hi, this package still does not produce any actual library files. Could you please look into that or orphan the package so someone else can?

Just running poetry build in the source directory, the wheel and source tarball don't include the requirements module (just the metadata).

It seems to be related to the use of the include keyword in pyproject.toml:

packages = [
    { include = "requirements" }
]
include = [
    "AUTHORS.rst",
    "LICENSE",
    "README.md"
]

Adding requirements/**/* to it fixes the problem:

include = [
    "AUTHORS.rst",
    "LICENSE",
    "README.md",
    "requirements/**/*",
]

I suppose this is a bug/regression in poetry or a misunderstanding of the include mechanism ?

@flipflop97:

ModuleNotFoundError: No module named 'requirements'

That makes no sense as the module resides in /usr/lib/python3.10/site-packages/requirements/ no matter if build / install vs. setuptools is used. It's designed to be installed with poetry.

This was mainly an example of a pkgbuild that results in a usable package. I didn't know setup.py was deprecated, thanks for telling!

I'm able to build it just fine using your pkgbuild, but I can't import the package in python afterwards, it just says ModuleNotFoundError: No module named 'requirements' (the same happens with the new release you just pushed). Using my example pkgbuild does let me import and use the module. Does this work correctly for you? I wonder what's going on in that case…

@flipflop97: ognibuild is able to use this package just fine.

Your PKGBUILD is missing the correct dependencies. setup.py install is deprecated, why do you think that makes any difference?

Hi, after installing this package I cannot import requirements in Python. I think something might be broken.

EDIT: This PKGBUILD works for me:

_pkgname=requirements-parser
pkgname=python-${_pkgname}
pkgver=0.5.0
pkgrel=3
pkgdesc='Small Python module for parsing Pip requirement files'
arch=(x86_64 aarch64)
url='https://github.com/madpah/requirements-parser'
license=(Apache)
depends=(
    python
)
makedepends=(
    python-setuptools
)
source=("https://files.pythonhosted.org/packages/source/${_pkgname::1}/${_pkgname}/${_pkgname}-${pkgver}.tar.gz")
b2sums=('ad3ac00e4556107d0d2cfc3b34fb3c9ca6f7f0a1f46c48bf46e9fd476eccdfdfc9ea6bfd691869cff78f628797c6afdaa9333de951481094d4abdf5947daf35a')

build() {
    cd "${_pkgname}-${pkgver}"
    python setup.py build
}

package() {
    cd "${_pkgname}-${pkgver}"
    python setup.py install --skip-build --root="${pkgdir}" --optimize=1
    install -Dm644 LICENSE "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"    
}