Package maap-py so it can be installed through a package manager

[marjo-luc]

Right now, maap-py needs to be installed from source. This makes it harder on users who are creating custom environments who may not know how or which versions to install from source. Having the module packaged and installable using a package manager such as pip would improve the user experience and align it with how users install other packages.

[grallewellyn]

@marjo-luc Do you want me to work on this? I am looking for new tickets. Is pip the preferred way to go?

[rtapella]

we did this for the Unity project in case you want to talk to ppl about how to get it into pypi
https://pypi.org/project/unity-sds-client/

[rtapella]

One thing you should do first is look at pypi to see if there are similarly named packages...
https://pypi.org/project/MAAP/

[rtapella]

(some of the MAAP stuff is from Marjorie, it looks like... but not all?)

[grallewellyn]

Thanks Rob! I was working on this for ipycmc following these steps: https://packaging.python.org/en/latest/tutorials/packaging-projects/

Looks like I can get away with the name maap-py

[marjo-luc]

We have the jupyter server extension on pypi already. The frontend extensions are on npm.

Let's hold off on doing this right away. I want to take this opportunity to review maap-py first.

[grallewellyn]

I believe this includes removing the need for locating the maap.cfg file to instantiate a MAAP instance, correct me if I am wrong since that is not a separate ticket but I can make one

[marjo-luc]

We would like to do that, but that doesn't necessarily preclude us from packaging maap-py. Feel free to create a ticket to track maap.cfg updates separately.

[grallewellyn]

Created new ticket here: #909

[chuckwondo]

@grallewellyn, we can package maap.cfg within the maap-py package as part of the packaging process. To aid doing so, it should be moved within the maap directory so that it becomes a package resource. It's a matter of only a couple of code changes related to reading the config and an addition to setup.py.

I'd be happy to show you how to do this.

[grallewellyn]

@sujen1412 said he wanted to work on the ticket for removing the need for tracking maap.cfg

[chuckwondo]

@grallewellyn, as mentioned in conversation with @sujen1412 in #909, I'll now work on making maap.cfg a package resource, which will obviate the need for using the MAAP_CONF env var. This corresponding issue in the maap-py repo: MAAP-Project/maap-py#78.

[chuckwondo]

I believe my work on MAAP-Project/maap-py#78 addressed this issue. Does that suffice to close this issue as complete?

[grallewellyn]

@chuckwondo Did you release maap-py on a package manager? I don't see it on pip, conda or npm
I think you did resolve this issue though: #909

[chuckwondo]

Nope, no release. Isn't @bsatoriu supposed to work on setting things up to allow us to cut releases to pip and/or conda-forge?

[marjo-luc]

MAAP-Project/maap-py#78 does not satisfy the work captured in this ticket.

@chuckwondo I'm not aware of any other ticket that describes the work outlined in this ticket. If there is one, please feel free to link it to this one.

[chuckwondo]

@marjo-luc and @grallewellyn, apologies, I replied to the wrong issue. I meant to comment in #909, which I'll do now.

[chuckwondo]

As we discussed in a Slack thread, I'm adding a dependency on removing support for Python 2. We'll wait to publish any sort of package until Python 2 remnants are removed, and a minimum Python 3.x version is documented.

[chuckwondo]

@marjo-luc, I just chatted with @grallewellyn about prioritizing this issue of packaging/publishing maap-py over other things and she mentioned that you seem to be on the same page. She also indicated that you'v recently been packaging and publishing other things as well, so do you want to do it for maap-py, or do you need someone else to pick up this issue?

[marjo-luc]

@chuckwondo the platform team will discuss this during our release planning tomorrow.