Conda build?

Is your feature request related to a problem? Please describe.

I’m on a M1 Mac and trying to install graspologic. However, the pip install is pretty buggy for me in general, and so conda usually is the way to go to install things with numba/cython/etc. dependencies. Is there the possibility of having a conda release as well as a pypi release?

However, when installing, I get the following error:

(mnex64) adam2392@Adams-MBP-2 graspologic % pip install graspologic
Requirement already satisfied: graspologic in /Users/adam2392/miniforge3/lib/python3.9/site-packages/graspologic-0.3.0-py3.9.egg (0.3.0)
Collecting anytree>=2.8.0
  Using cached anytree-2.8.0-py2.py3-none-any.whl (41 kB)
Collecting beartype>=0.7.1
  Using cached beartype-0.8.0-py3-none-any.whl (455 kB)
Collecting gensim<=3.9.0,>=3.8.0
  Using cached gensim-3.8.3.tar.gz (23.4 MB)
Collecting graspologic
  Using cached graspologic-0.2.0.tar.gz (5.1 MB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Installing backend dependencies ... done
    Preparing wheel metadata ... done
  Using cached graspologic-0.1.0.tar.gz (5.1 MB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Installing backend dependencies ... done
    Preparing wheel metadata ... done
ERROR: Cannot install graspologic==0.1.0, graspologic==0.2.0 and graspologic==0.3.0 because these package versions have conflicting dependencies.

The conflict is caused by:
    graspologic 0.3.0 depends on graspologic-native>=1.0.0
    graspologic 0.2.0 depends on graspologic-native
    graspologic 0.1.0 depends on graspologic-native

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

Describe the solution you’d like

I’m not exactly sure what the problem is, but if there is a conda build then that would alleviate this issue I think.

[daxpryce]

Fantastic, I’ll create another build pipeline specifically for m1 builds and we’ll publish them just to github for now (so you’ll have to do manual download / install to test vs. using pip or conda-pointing-at-pypi). Can you send me an email @ [e-mail] so we can run through things over email instead of tickets? I will report back once we have some results and we can let this ticket go into stasis in the meantime

[bdpedigo]

@adam2392 seems like what @daxpryce suggests is worth figuring out regardless.

As far as your original request goes, I’m open to setting up a conda-forge feedstock once this gets fixed, but first it would require that all of our dependencies are also on conda-forge. This means we’d need graspologic-native as well as hyppo (cc @sampan501) on there. I’m not sure what would be involved for graspologic-native as its not really a python package but we could look into it if there’s interest (and if hyppo wants to get on there too).