You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Figured it might be better to have its own issue, even though it's not really an "issue" perse (#29).
It's entirely possible that this workflow is overkill or misguided, esp. since I just started learning PyPI and Anaconda building and maintaining within the last few weeks or so. There are some rough GitHub actions workflows at mat_discover/.github/workflows. It would be great to hear your thoughts/suggestions.
pipreqs .# outputs requirements.txt based on imports# <touch up requirements.txt>
flit init
# <touch up pyproject.toml># <add `__init__.py` under `mat_discover/mat_discover` with docstring and e.g. `__version__ = "1.3.9"`># <add `dependencies = ["", "", "", ...]` to pyproject.toml based on requirements.txt># <add PyPI credentials (i.e. token) to `~/.pypirc`>
grayskull pypi mat_discover
# <touch up run_grayskull.py based on default output of grayskull>
manually modified run_grayskull.py
"""Touch up the conda recipe from grayskull using conda-souschef."""fromsouschef.recipeimportRecipeimportosfromos.pathimportjoinfrompathlibimportPathimportmat_discovername, version=mat_discover.__name__, mat_discover.__version__os.system("grayskull pypi {0}=={1}".format(name, version))
Path("scratch").mkdir(exist_ok=True)
fpath=join(name, "meta.yaml")
fpath2=join("scratch", "meta.yaml")
my_recipe=Recipe(load_file=fpath)
#--touchups---my_recipe["requirements"]["host"].append("flit")
my_recipe["build"]["noarch"] ="python"delmy_recipe["requirements"]["build"]
my_recipe["requirements"]["run"].replace("kaleido", "python-kaleido")
my_recipe["requirements"]["run"].append("pytorch >=1.9.0")
my_recipe["requirements"]["run"].append("cudatoolkit <11.4")
#^^touchups^^my_recipe.save(fpath)
my_recipe.save(fpath2)
publish to PyPI and Anaconda
flit publish
python run_grayskull.py
cd scratch
conda build .
Figured it might be better to have its own issue, even though it's not really an "issue" perse (#29).
It's entirely possible that this workflow is overkill or misguided, esp. since I just started learning PyPI and Anaconda building and maintaining within the last few weeks or so. There are some rough GitHub actions workflows at mat_discover/.github/workflows. It would be great to hear your thoughts/suggestions.
dependencies
setup
(see https://flit.readthedocs.io/en/latest/ for
flit
instructions, minimally discussed in following comments)manually modified
run_grayskull.py
publish to PyPI and Anaconda
Initial
grayskull
output:final
grayskull
output:Note: several of these packages come from the
sgbaird
Anaconda channelTo just install instead of upload, you can use:
The text was updated successfully, but these errors were encountered: