I have checked Anaconda Navigator and no metadata is populated. I have looked at the dist-info folder, and the metadata is filled in properly in the METADATA and License.txt files. What am I doing wrong?
I am assuming that this issue would have nothing to do with the fact that I am pulling the package from a custom Conda channel on a shared network drive?
Where does Anaconda Navigator pull the metadata from for the description?
I know that the description for the Python Package Manager comes from ..\envs\arcgispro-py3-clone\pkg-metadata\metadata.json and would like to know if there is a way to update that.
I need to distribute the package to my users, and I know that I may be a bit obsessive with the metadata since the install actually works, but it would be nice to do this properly.
Great to see your work on packaging! Yes, you found the location for the Pro installation to manage its metadata for the backstage -- if you have a description / summary entry for your package, I can add it to that file, and it will be included in a later Pro release, or can be upgraded with `conda update` on the root environment. I'm not sure where Anaconda Navigator is pulling its metadata, I would expect it to be from one of two places: either the package metadata itself, or the information provided on Anaconda.org. For the package metadata itself, if you extract the package .tar.bz2, and look at info/recipe/meta.yaml, you'll see the final rendered output after the jinja templating is completed, that may provide clues if say a particular variable isn't pulling across a value. For the anaconda.org metadata, you can typically set this by visiting anaconda.org/<your username>/package/ and manually edit the description field there.
Thanks for the reply. I opened the meta.yaml file (below) and it looks fully populated. I can look into that some more using your other suggestion.
As for the ArcGIS Pro side of things, when you say it can be upgraded with `conda update` on the root environment, what exactly do you mean? Are you saying that if I install lafpy to the root env it will show up properly in the Python Project Manager? Just want to make sure since everyone says to only make changes to the clone...
I forgot to mention that I have lafpy on an internal government server channel. I do not upload the package to Anaconda.org, so I guess I am out of options there... I would have thought that Anaconda could deal with that?