Re: [PATCH 1/1] gnu: Add python-betamax.

2016-10-17 Thread Hartmut Goebel
Am 16.10.2016 um 22:22 schrieb Marius Bakke: > Can we leverage this mechanism instead of propagating everything? Are > there any drawbacks to doing that? propagating all inputs is the correct way for two reasons: a) In Python only *one* version of a module can but used within an environment [*] S

Re: [PATCH 1/1] gnu: Add python-betamax.

2016-10-17 Thread Hartmut Goebel
Am 16.10.2016 um 19:17 schrieb Leo Famulari: > +(inputs > + `(("python-requests" ,python-requests))) These need to be propagated inputs, In assume. Please refer to the Python packaging guide which was updated some days ago. -- Regards Hartmut Goebel | Hartmut Goebel | h.goe...@

Re: [PATCH 1/1] gnu: Add python-betamax.

2016-10-16 Thread Marius Bakke
Leo Famulari writes: > This is a build time dependency of python-requests-toolbelt when using > Python 3.5. > > * gnu/packages/python.scm (python-betamax, python2-betamax): New variables. This LGTM, but I have a couple of off-topic remarks. The requests input/reference was a bit odd and seems t