Re: Need help with conda package - launcher script

On Sun, Oct 8, 2023 at 10:20 AM Orion Poplawski wrote: > > With the update to conda 23.5.2 and using the pyproject macros, the > conda package is no longer producing the /usr/bin/conda-env launcher > script which is causing problems. What problems specifically? > I don't know how I can get that

Re: Circular import issue in F37

On Mon, Jun 5, 2023 at 6:45 AM Sandro wrote: > > Hi again, > > I'm trying to understand why I'm getting a circular import error running > tests only in F37 [1]. > > It's an easy fix adding an empty __init__.py in %prep, but why are F38 > and rawhide buildroots happy not having that file, while

Re: pathfix.py will be removed from Python 3.12

On Thu, Oct 27, 2022 at 5:51 AM Miro Hrončok wrote: > > On 26. 10. 22 23:19, Elliott Sales de Andrade wrote: > > This list is not sorted, which makes it difficult to scan. Please also > > provide the maintainers-by-package list that is usually sent for > > changes t

Re: pathfix.py will be removed from Python 3.12

On Wed, Oct 26, 2022 at 6:41 AM Lumír Balhar wrote: > > Hello. > > Since Python 2.0 (1994), Python provided a useful tool pathfix.py that > we use in Python RPM macros for fixing shebangs of Python modules and > some RPM packages use it as well directly in their specfiles for similar > purposes.

Re: Help needed triaging build failures without distutils

On Tue, Oct 18, 2022 at 5:28 AM Miro Hrončok wrote: > > Hey Pythonistas. > > The Python standard library distutils module will be removed from Python 3.12+ > > https://peps.python.org/pep-0632/ > > As preparatory work, we build all python packages in a Copr repository with > Python 3.11 sans

Retiring python-sphinx-panels in Rawhide+F37

Hi, python-sphinx-panels is currently FTBFS as it does not support Sphinx 5. It is abandoned upstream with the suggestion of sphinx-design instead. My package which depended on it has moved to sphinx-design, and I believe all others have as well. According to repoquery, there should be no

Re: The great Mailman 3 / Hyperkitty upgrade: bumping flufl-lock and mistune?

On Tue, 14 Dec 2021 at 17:32, Michel Alexandre Salim wrote: > > Hi all, > > Neal Gompa and I have been reviving the effort to get our mailing list > server infrastructure (currently running on RHEL 7 with missing packages > provided in an unofficial repo) hostable on RHEL 9 + EPEL. > > Pagure

Re: Automatically generated Obsoletes tags?

On Mon, 29 Nov 2021 at 08:04, Tomáš Orsava wrote: > > The downside is that we will have a few thousand (est. 3624 [1]) > additional Obsoletes tags in the Fedora repos that are mostly useless. > Does anyone see a problem with this? Given the amount of tags already > present (e.g. 336 thousand

Re: Migrating python-graphql-server to new guidelines

On Sun, 22 Aug 2021 at 06:06, Mattia Verga wrote: > > Hello folks, > I'm trying to migrate graphql-server spec file to the newer Python > guidelines, but I'm hitting some walls. > > - Building the package locally went fine, while on Koji [¹] I get: > error: line 39: Unknown tag:

Obsoleting extras subpackages

In Dask, they have some extras that have effectively been removed, but they kept them in their config for backwards compatibility. In Fedora, I would like to remove the meta-subpackages, as they don't provide any additional Requires. As such, I would like to Obsolete them from the main package,

Re: Building docs of compiled extensions with new macros

On Wed, 18 Aug 2021 at 19:51, Miro Hrončok wrote: > > On 18. 08. 21 11:09, Elliott Sales de Andrade wrote: > > I've been experimenting with the new macros for Python packages, and > > ran into some issues building Sphinx docs for compiled extensions. > > > > When

Building docs of compiled extensions with new macros

I've been experimenting with the new macros for Python packages, and ran into some issues building Sphinx docs for compiled extensions. When building docs, one usually has to be able to import the project. When the project uses compiled extensions, it is not sufficient to point to the original

Re: requesting help to update spyder

On Sun, 15 Aug 2021 at 19:40, Scott Talbert wrote: > > 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', > >>

Re: pypy3 renamed to pypy3.7 on Fedora 35+, also available in Fedora 33/34

On Wed, 11 Aug 2021 at 08:50, Miro Hrončok wrote: > > Hello PyPyistas, > > we have renamed the pypy3 package to pypy3.7 (both the component and the > "binary" package) on Fedora 35+. The package no longer installs to > /usr/lib64/pypy3-7.x/ but rather to /usr/lib64/pypy3.7/. > > *What is this

Retiring python-pyinsane2

I have just retired python-pyinsane2; it has been archived by upstream in favour of its replacement libinsane. I believe all users in Fedora have also moved on to using libinsane as well. Since tests have broken, it is also FTBFS in Rawhide, and I don't intend to invest any time into fixing it.

Retiring python-descartes

Hi, I am retiring python-descartes in Rawhide. Upstream died when Bitbucket dropped Mercurial support, and has no intention of reviving it. Downstream users have stopped using it, and I have removed the unnecessary dependency from Fedora packages, or patched it out after reporting upstream. It

Orphaning python-pytest-helpers-namespace

I am orphaning python-pytest-helpers-namespace, which is no longer a dependency of my packages. It currently has one bug report [1] for updating to the latest version, which has grown a new dependency (setuptools-declarative-requirements) that I do not wish to also package. AFAIK, nothing else

numpy+wx breaks pillow on ppc64le: cannot allocate memory in static TLS block

I'm not sure in which package the error lies here and thus where to file the bug report. This occurs on only ppc64le with a matplotlib build [1]. Does anyone have any ideas? This works: >>> import wx >>> from PIL import Image and this works: >>> import numpy >>> from PIL import Image but if you

Re: Plans for Matplotlib 3.0+

On Fri, 21 Sep 2018 at 05:11, Miro Hrončok wrote: > On 29.8.2018 10:56, Miro Hrončok wrote: > > On 29.8.2018 05:38, Elliott Sales de Andrade wrote: > >> On Fri, 17 Aug 2018 at 18:42, Miro Hrončok >> <mailto:mhron...@redhat.com>> wrote: > >> > >&g

Re: Plans for Matplotlib 3.0+

On Fri, 17 Aug 2018 at 18:42, Miro Hrončok wrote: > On 17.8.2018 21:51, Elliott Sales de Andrade wrote: > > On Fri, 17 Aug 2018 at 15:18, Miro Hrončok > <mailto:mhron...@redhat.com>> wrote: > > > > > > > > On 17.8.2018 20:20, José Abílio Mato

Re: Plans for Matplotlib 3.0+

On Fri, 17 Aug 2018 at 15:18, Miro Hrončok wrote: > > > On 17.8.2018 20:20, José Abílio Matos wrote: > > On Friday, 17 August 2018 18.54.59 WEST Miro Hrončok wrote: > >> Is there an upstream schedule? That would very much help us to determine > >> if this is F29 material. > > > > You know the

Re: flit

On 16 November 2017 at 01:31, Nick Coghlan wrote: > On 16 November 2017 at 12:30, Orion Poplawski wrote: > >> So - is it possible to build rpms with flit? >> > > There are already some packages that are built using flit: $ dnf repoquery --disablerepo=\*

Re: Self-introduction

Hi Zbyszek, On 13 August 2017 at 12:32, Zbigniew Jędrzejewski-Szmek <zbys...@in.waw.pl> wrote: > On Fri, Aug 11, 2017 at 02:13:16PM +0200, Miro Hrončok wrote: > > On 11.8.2017 08:25, Elliott Sales de Andrade wrote: > > >Hello, > > > > > >My name

Self-introduction

Hello, My name is Elliott, but you may know me as QuLogic on IRC/FAS/GitHub/etc. I am interested in Python 3 porting, scientific libraries, Jupyter, etc., some of which you can find in my coprs [1]. I am also an upstream developer on libraries such as Matplotlib and Cartopy. I have opened a few