* how to define inputs for python packages
@ 2020-09-28 6:05 Reza Alizadeh Majd
2020-09-28 8:28 ` Wiktor Żelazny
2020-09-28 18:27 ` Hartmut Goebel
0 siblings, 2 replies; 4+ messages in thread
From: Reza Alizadeh Majd @ 2020-09-28 6:05 UTC (permalink / raw)
To: help-guix
Hi Guix,
I'm a little confused about definition of inputs for a python based
package.
I had defined a package for a python library that I wrote, defining the
dependencies as `inputs`, package builds successfully, and all my tests
will be passed.
but when I try to import this library to another program, I receive
various errors about missing dependencies of the library. (the ones
that I defined as `inputs` for the library).
is there any rule that I missed to choose a dependency as an `input` or
as a `propageted-input` one?
Regards,
Reza
--
Reza Alizadeh Majd
PantherX Team
https://www.pantherx.org/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: how to define inputs for python packages
2020-09-28 6:05 how to define inputs for python packages Reza Alizadeh Majd
@ 2020-09-28 8:28 ` Wiktor Żelazny
2020-09-28 18:27 ` Hartmut Goebel
1 sibling, 0 replies; 4+ messages in thread
From: Wiktor Żelazny @ 2020-09-28 8:28 UTC (permalink / raw)
To: help-guix
[-- Attachment #1: Type: text/plain, Size: 487 bytes --]
On Mon, Sep 28, 2020 at 09:35:59AM +0330, Reza Alizadeh Majd wrote:
> is there any rule that I missed to choose a dependency as an `input` or
> as a `propageted-input` one?
Hi,
I’d say that you always need to declare `python-*` dependencies as
`propagated-inputs`, unless it’s something required for building and
testing the package, exclusively, in which case the package in question
goes to `native-inputs`.
As an aside, it’s the same for `r-*` packages.
WŻ
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: how to define inputs for python packages
2020-09-28 6:05 how to define inputs for python packages Reza Alizadeh Majd
2020-09-28 8:28 ` Wiktor Żelazny
@ 2020-09-28 18:27 ` Hartmut Goebel
2020-09-29 9:02 ` Reza Alizadeh Majd
1 sibling, 1 reply; 4+ messages in thread
From: Hartmut Goebel @ 2020-09-28 18:27 UTC (permalink / raw)
To: Reza Alizadeh Majd, help-guix
Am 28.09.20 um 08:05 schrieb Reza Alizadeh Majd:
> is there any rule that I missed to choose a dependency as an `input` or
> as a `propageted-input` one?
This is described in the manual:
https://guix.gnu.org/manual/en/html_node/Python-Modules.html#Specifying-Dependencies
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: how to define inputs for python packages
2020-09-28 18:27 ` Hartmut Goebel
@ 2020-09-29 9:02 ` Reza Alizadeh Majd
0 siblings, 0 replies; 4+ messages in thread
From: Reza Alizadeh Majd @ 2020-09-29 9:02 UTC (permalink / raw)
To: Hartmut Goebel; +Cc: help-guix
On Mon, 28 Sep 2020 20:27:57 +0200
Hartmut Goebel <h.goebel@crazy-compilers.com> wrote:
> Am 28.09.20 um 08:05 schrieb Reza Alizadeh Majd:
> > is there any rule that I missed to choose a dependency as an
> > `input` or as a `propageted-input` one?
>
> This is described in the manual:
>
> https://guix.gnu.org/manual/en/html_node/Python-Modules.html#Specifying-Dependencies
>
Thanks, that was so helpful.
Regards,
Reza
--
Reza Alizadeh Majd
PantherX Team
https://www.pantherx.org/
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2020-09-29 9:03 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-09-28 6:05 how to define inputs for python packages Reza Alizadeh Majd
2020-09-28 8:28 ` Wiktor Żelazny
2020-09-28 18:27 ` Hartmut Goebel
2020-09-29 9:02 ` Reza Alizadeh Majd
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).