Hi Scott
Scott Talbert via python-devel venit, vidit, dixit 2025-07-09 04:31:15:
> Is there any way to use the pyproject macros when setup.py isn't in the
> root directory?
>
> I maintain a couple of packages where this is the case - one where there
> are actually two PyPI packages built from t
Ankur Sinha via python-devel venit, vidit, dixit 2025-06-25 14:19:28:
...
> So, we're thinking of:
>
> - prioritising packaging/maintaining software that is unavailable on
> PyPi (or difficult to install from there)
> - dropping software that is pip installable from Fedora
> - shifting focus to
Hi there,
Karolina Surma venit, vidit, dixit 2024-05-31 10:55:16:
> Hello,
>
> To deliver Python 3.13 with Fedora Linux 41, we will run a coordinated
> rebuild in a side tag.
>
> https://fedoraproject.org/wiki/Changes/Python3.13
>
> Python 3.13.0b2 is scheduled for Tuesday, Jun 4th 2024.
> We
Am Fr., 26. Jan. 2024 um 09:26 Uhr schrieb Miro Hrončok :
>
> On 26. 01. 24 4:33, Nico Kadel-Garcia wrote:
> > What is the*fascination* with splitting and renaming packages this
> > way?
>
> No idea generally, but in the world of Python packaging,
> the two cases I know (poetry, flit) were motivat
Is the matrix bridge down? Anyways:
If I have a fix for a package which has just been merged (dblatex), should I
build it with target rawhide? I'm asking because mock sees py 3.12 only with
--enablerepo=local, and the f39-python target is gone, obviously.
Hi there
I have rebuilt
https://apps.fedoraproject.org/packages/portmidi
with cythonizing during build rather than using the project-shipped ancient
cython output. Is this change supposed to trickle down to F30? (The package
itself needs to go away sooner or later anyways.)
MIchael
__
