On Sun, 9 Sep 2018, Miro Hrončok wrote:
I'm thinking about removing some of my Python 2 subpackages (that
are no longer used). However, I'm wondering about the case where
the removed packages should be added to fedora-obsolete-packages. I
don't _think_ the removal of my packages would cause
I'm thinking about removing some of my Python 2 subpackages (that are no
longer used). However, I'm wondering about the case where the removed
packages should be added to fedora-obsolete-packages. I don't _think_ the
removal of my packages would cause any problems upon upgrade.
Can someone
On Wed, 12 Sep 2018, Miro Hrončok wrote:
Hello.
In line with
https://fedoraproject.org/wiki/Changes/No_more_automagic_Python_bytecompil
ation_phase_2
I plan to mass push the following 3 lines on the top of your package spec:
I updated my packages to set _python_bytecompile_extra to 0, but
On Thu, 13 Sep 2018, Miro Hrončok wrote:
Hello.
In line with
https://fedoraproject.org/wiki/Changes/No_more_automagic_Python_bytecompil
ation_phase_2
I plan to mass push the following 3 lines on the top of your package spec:
I updated my packages to set _python_bytecompile_extra to 0, but
Hi,
It seems that you just updated python-more-itertools and dropped Python 2
support. Unfortunately, this breaks quite a few packages - namely
python2-pytest and all of its users. Can you please restore Python 2
support for now?
Thanks,
Scott
On Mon, 20 May 2019, Miro Hrončok wrote:
Hello packagers. During the rebuilds for Python 3.8, we have found out that
your package most likely has precythonized C sources.
There was an update to Cython and the C sources needs to be regenerated. In
line with Fedora packaging policies and
On Fri, 3 May 2019, Miro Hrončok wrote:
python-suds jortel swt2c
suds is actually FTBFS due to pytest 4. I am working on fixing it. I
filed a bug as well.
Scott___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To
On Fri, 26 Apr 2019, Orion Poplawski wrote:
It appears that in at least some situations pytest will create -PYTEST.pyc
files, and sometimes (always?) with weird permissions:
-rw---. 1 root root 1614 Jul 13 2018
> On 27. 08. 19 22:20, Miro Hrončok wrote:
>
> python27 build in progress.
>
> Will retire python2 later tomorrow or on Friday (in case something is
> terribly
> broken I want to have some maneuvering space).
Hey Miro,
I can't rebuild python-wxpython4 with the new python27. This is what I'm
On Mon, 27 Apr 2020, Miro Hrončok wrote:
Hello Python packagers,
since there is no upstream supported universal test invocation for Python
(`python setup.py test` is deprecated and the de-facto-standard `tox` doesn't
always do what we want in RPM's %check and/or is not always used by
On Fri, 1 May 2020, Ian McInerney wrote:
I am working on packaging up a git tool that is written in Python
(git-revise: https://github.com/mystor/git-revise), and was wondering if the
"python3-%{name}" applies to tools like this, e.g. ones that are written in
Python but are designed for use on
On Mon, 18 May 2020, Miro Hrončok wrote:
On 18. 05. 20 18:23, Scott Talbert wrote:
Any good workarounds for working with epel7 Python packages on Fedora?
Mainly dealing with the fact that python3_pkgversion differs from Fedora to
EPEL7. Ie, when doing 'fedpkg mockbuild' the SRPM
Any good workarounds for working with epel7 Python packages on Fedora?
Mainly dealing with the fact that python3_pkgversion differs from Fedora
to EPEL7. Ie, when doing 'fedpkg mockbuild' the SRPM will be generated
with the wrong python3_pkgversion.
I tried this, but it didn't seem to work:
On Tue, 23 Jun 2020, Tomas Hrnciar wrote:
swt2c congruity python-pexpect python-pypubsub python-pytest-forked
python-pytest-timeout python-pytest-xdist python-suds
All fixed in rawhide except for python-pexpect, which doesn't actually use
setuptools. Strangely, it only uses it when
On Wed, 9 Dec 2020, Scott Talbert wrote:
I'm working on test builds of OpenColorIO 2.0 in a COPR[1] and one of the
requirements to build the documentation is python-testresources.
The problem is it's looking for version 2.0+ but only 1.0 is in Fedora[2].
But I can't even find where that exists
On Wed, 9 Dec 2020, Richard Shaw wrote:
I'm working on test builds of OpenColorIO 2.0 in a COPR[1] and one of the
requirements to build the documentation is python-testresources.
The problem is it's looking for version 2.0+ but only 1.0 is in Fedora[2].
But I can't even find where that exists
On Sun, 15 Aug 2021, Miro Hrončok wrote:
Hi,
I am trying to update spyder on rawhide and F35. The main issue I have is
that pyqt requirements are strict. From the setup file,
'pyqt5<5.13',
'pyqtwebengine<5.13',
Fedora has 5.15.x. If I relax QT versions, built and launch spyder, I get
this
On Sun, 15 Aug 2021, Elliott Sales de Andrade wrote:
I am trying to update spyder on rawhide and F35. The main issue I have is
that pyqt requirements are strict. From the setup file,
'pyqt5<5.13',
'pyqtwebengine<5.13',
Fedora has 5.15.x. If I relax QT versions, built and launch spyder, I get
On Fri, 22 Oct 2021, Peter Kotvan wrote:
Hello folks!
I'd like to package the autorandr project for Fedora. This would be my
first python package so I'd like to ask some questions.
Firstly the project already contains a spec file. However I'm not sure
whether it could be used without any
On Wed, 23 Jun 2021, Miro Hrončok wrote:
%pyproject_buildrequires works and generates requirements on python3dist(sip)
and python3dist(pyqt-builder) \o/
%pyproject_buildrequires -r doesn't work. It says:
ValueError: build backend cannot provide build metadata
(incl. runtime requirements)
Hi all,
Does anyone have any experience with using Fedora's MinGW stack to
cross-compile Python wheels for Windows?
Scott
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to
On Fri, 21 Jan 2022, Felix Schwarz wrote:
Does anyone have any experience with using Fedora's MinGW stack to
cross-compile Python wheels for Windows?
I'm using the mingw stack to cross-compile a Windows binary which shipped as
part of an otherwise platform neutral Python wheel. The main
Hi all,
First, is it possible to use this macro if the pyproject.toml isn't in the
root directory of the package? There doesn't seem to be an option to
specify a path, so I tried cd'ing into a path and running it, but it
seemed to run into an odd error like it was trying to include my
On Wed, 13 Sep 2023, Miro Hrončok wrote:
On 13. 09. 23 5:03, Scott Talbert wrote:
Hi all,
Hi Scott.
First, is it possible to use this macro if the pyproject.toml isn't in the
root directory of the package? There doesn't seem to be an option to
specify a path, so I tried cd'ing
On Sat, 13 Aug 2022, Orion Poplawski wrote:
Can anyone tell me why python-astroid gets built as "UNKNOWN" on EPEL9?
Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.mum5to
+ umask 022
+ cd /builddir/build/BUILD
+ cd astroid-2.12.1
+ echo pyproject-rpm-macros
+ echo python3-devel
25 matches
Mail list logo
