On Sat, Aug 06, 2016 at 02:52:37PM +0200, David Craven wrote:
> > I believe we already have python2-ipaddress, although an older version.
>
> Ups, I missed that. Thanks.
>
> Can you answer some questions on best practices for packaging python packages?
>
> 1. Are python-setuptools inputs or nati
> 1. Are python-setuptools inputs or native-inputs? It seems to be done
> both ways but I guess it doesn't really matter since it's an interpreted
> language.
Usually native-inputs. The idea is you only need the native-inputs to compile
and install the thing and then you can throw the native-inpu
> I believe we already have python2-ipaddress, although an older version.
Ups, I missed that. Thanks.
Can you answer some questions on best practices for packaging python packages?
1. Are python-setuptools inputs or native-inputs? It seems to be done
both ways but I guess it doesn't really matte
On Fri, Aug 05, 2016 at 08:37:30PM +0200, David Craven wrote:
> * gnu/packages/python.scm (python-ipaddress): New package.
> (python2-ipaddress): New package.
I believe we already have python2-ipaddress, although an older version.
Great news if you can update it and enable the tests!
* gnu/packages/python.scm (python-ipaddress): New package.
(python2-ipaddress): New package.
---
gnu/packages/python.scm | 21 +
1 file changed, 21 insertions(+)
diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm
index 4f2eba2..c8d169a 100644
--- a/gnu/packages/p
