P. L. Lim
P. L. Lim
Looking at the linked issue, I see two possible ways forward. Example implementations of each: 1. https://github.com/nextcloud/appstore/pull/1294 -- This does not require third-party Action. I think maintainer re-triggers only the...
Huh, I think for `astropy`, I actually have to patch the OpenAstronomy workflow (https://github.com/OpenAstronomy/github-actions-workflows/pull/199), but not for `jdaviz` (https://github.com/spacetelescope/jdaviz/pull/2865).
@astrofrog reverted my attempt to address this at https://github.com/OpenAstronomy/github-actions-workflows/pull/206 Also it never quite work because of a token failure that I cannot understand: #16535 So, for now, just check the...
FWIW * OpenAstronomy has packaging guide that uses cookiecutter at https://github.com/OpenAstronomy/packaging-guide * Scientific Python has some guides here as well: https://learn.scientific-python.org/development/guides/packaging-simple/
I seldom have to create a package from scratch but for the 1-2 times I had to do it, cookiecutter was nice. It had prompts and then give you a...
Hello and thanks for your interest. You can always open a draft PR for now if you insist on working on this issue. Though we also have others available; your...
Oh... maybe. I cannot keep track of all the APE updates. Thx for the reminder. I will update original post.
> What about adding a symlink/copy at time of packaging? At the time of packaging? How? 👀
> how do you pick up the [tool:pytest] section I can't. That is why I added a `astroquery_pytest.ini` in the astropy-integration-testing PR linked above, following sunpy's example. > surely there...
> Would copying the conftest over would work as the same workaround then? AFAIK there is no way to tell pytest to select this or that conftest.py for a given...