Re: Circular import issue in F37

2023-06-25 Thread Sandro
On 07-06-2023 22:15, Sandro wrote: On 07-06-2023 02:30, Sandro wrote: On 06-06-2023 09:39, Elliott Sales de Andrade wrote: 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

Re: Circular import issue in F37

2023-06-07 Thread Sandro
On 07-06-2023 02:30, Sandro wrote: On 06-06-2023 09:39, Elliott Sales de Andrade wrote: 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

Re: Circular import issue in F37

2023-06-06 Thread Sandro
On 06-06-2023 09:39, Elliott Sales de Andrade wrote: 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

Re: Circular import issue in F37

2023-06-06 Thread Elliott Sales de Andrade
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

Circular import issue in F37

2023-06-05 Thread Sandro
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 F37 complaints? The versions of the involved packages