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
makes it tricky to install pysiaf in an offline environment. relic is required during package installation, but is not otherwise declared as a dependency anywhere. If you don't do anything special, it will try to go down the git clone path, which is of course not possible without internet access.
There are sort of two related issues in here: First, when collecting a set of requirements in your online environment for later deployment, relic will not be collected automatically. Second, even if you have a wheel for relic, pip doesn't know it needs to install to install relic before it can install pysiaf.
I believe this is an example of the problem the build system requirements section of pyproject.toml was intended to solve. If pysiaf had a pyproject.toml, it could read
which I think would cue pip to do the right thing. However, I unfortunately I haven't worked on a project that uses pyproject.toml or migrated my own to it, so I'm not 100% sure on how that works, or if any other changes to setup.py or requirements declaration would be needed.
I've worked around the issue in my particular application by explicitly added relic to my set of up requirements, and doing a first pip install pass for setuptools wheel relic, but it took a little exploration to understand the issue.
@mperrin, FYI, this indirectly impacts offline installation of webbpsf through the pysiaf dependency, which is what got me here. Fortunately the workaround isn't too hard.
The text was updated successfully, but these errors were encountered:
Is relic even still supported/maintained at this point? I think not, deprecated in favor of setuptools_scm. Maybe consider updating pysiaf to be more consistent with the current stsci-package-template and with how we do things elsewhere in webbpsf and poppy?
This block in
setup.py
:makes it tricky to install
pysiaf
in an offline environment.relic
is required during package installation, but is not otherwise declared as a dependency anywhere. If you don't do anything special, it will try to go down thegit clone
path, which is of course not possible without internet access.There are sort of two related issues in here: First, when collecting a set of requirements in your online environment for later deployment,
relic
will not be collected automatically. Second, even if you have a wheel forrelic
,pip
doesn't know it needs to install to installrelic
before it can installpysiaf
.I believe this is an example of the problem the build system requirements section of
pyproject.toml
was intended to solve. Ifpysiaf
had apyproject.toml
, it could readwhich I think would cue
pip
to do the right thing. However, I unfortunately I haven't worked on a project that usespyproject.toml
or migrated my own to it, so I'm not 100% sure on how that works, or if any other changes tosetup.py
or requirements declaration would be needed.I've worked around the issue in my particular application by explicitly added
relic
to my set of up requirements, and doing a firstpip install
pass forsetuptools wheel relic
, but it took a little exploration to understand the issue.@mperrin, FYI, this indirectly impacts offline installation of
webbpsf
through thepysiaf
dependency, which is what got me here. Fortunately the workaround isn't too hard.The text was updated successfully, but these errors were encountered: