Re: Note for Python packages: packages do not have "inputs" (most of the time)

[ng0]

Hartmut Goebel <address@hidden> writes:

> Hi,
>
> I just found some Python packages recent checked in to master, which
> have "inputs" defined.
>
> All Python packages, please keep in mind:
>
> *The default for including other Python packages is "propagated-inputs".*
>
> guix import is wrong here, as it defaults to "inputs". Please refer to
> the section "Specifying Dependencies" in info doc/guix "Python Modules".
>
> Thanks!
>
> Note: Currently specifying dependencies as "input" works by mere luck
> and all these packages will fail with the new python build system. (And
> I'm having a hard time cleaning up all these wrong inputs :-((

I think this is wrong. My assumption is I work with the old system as
long as the new system is not in place. I see no changes which fix this,
so why should I do work in advance when this must be fixed afterwards?

Will the current system report packages as broken, or are they entirely
broken? From my perspective this reads weird. I have not read the new
documentation section, but I assumed this is not yet in place?

> -- 
> Regards
> Hartmut Goebel
>
> | Hartmut Goebel          | address@hidden               |
> | www.crazy-compilers.com | compilers which you thought are impossible |
>
>
>