These are chat archives for astropy/astropy
.. plot:: plot.pyin side a
mydocs.rstfile, in a project using the Astropy affiliated package setup. Does anyone know how to skip that
plot.pyfile from being executed as a doctest? (it is and we do want it executed as part of the docs build).
Cadairon collection because it's a sphinx directive
CadairI have no idea about the doctests :)
Cadairanyone going to euroscipy this year?
doctest_norecursedirs = docs/plot.pyin
Cadairbsipocz: astrofrog and I were talking about writing a little web app to montior astropy dev builds of affiliated packages
Cadairmy idea was to have something that explicitly reports from travis (just for the dev build) to a web app
Cadairwhich then displays the status
Cadairso it would know what astropy commit was run against and when the run was
bsipoczwould it shop around in the affiliates' own travis builds, or have one of its own?
bsipoczalthough I still think it's not really our job/task, but the maintainers!
Cadairwell it puts no requirement on you to do anything with the info
Cadairit's just a status page of affilated packages vs astropy masterr
Cadairso you can see if something has gone horribly wrong
bsipocz(but that's just the usual rant of mine as I got rather upset when I saw cron builds failing for weeks, but didn't get reported back upstream, yet the users will probably blaim it on us astropy to break that package..)
bsipoczit may not work when you have a separate plot.py, but in astropy/docs/nddata/utils.rst it works whe n yhe plot directive has the code in the main rst file
bsipoczan alternative solution could be to set up the sphinx-gallery examples, we have some of those skipped, too. But probably that's a big overkill
Cadairbsipocz: sure, my main issue with that frameattribute thing was lack of time to react
Cadairand you can slow it all the hell down by doing RC after RC or you can have a look at a dashboard thing to see if all seems ok
bsipoczI don't mean you. That was indeed a massive mistake mostly from my side. I should have checked the changelog before merging, assumed it's a bugfix
Cadairsure, I think it was supposed to be a bug fix
bsipoczyes, but the issue is that getting in more bug and docs fixes is still very tempting, even after the last RC
CadairI mean the only way to do it is to have "release 24-48 hours after last merge"
Cadairbut I would not like doing that for sunpy
bsipoczyeap. just checked, the sdist was made ~20 hours after merging the frameattribute PR, and ~3 hours after merging the last meaningless fixup PR (but those very last ones were really just to cleanup the release, xfail some more tests, etc)
Cadairmy comment on the PR was the git tag
CadairI mean I have done much worse than 3 hours with sunpy
bsipoczyeah, git tag happeded about the same time as the last backport as we needed that to build the wheels, but those failed at the first attempt and needed some more hacking, etc.
equant on FreenodeWhen I use WCS(hdu.header) on ALMA data, I get 4 axes because it's reading in STOKES and FREQ data. Is there a way to have that information ignored so that it's 2-axis just like the Horse Head example in the docs?
equant on FreenodeNevermind... I think this is what I want.... wcs.dropaxis(3).dropaxis(2)