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
{{ message }}
Repository navigation
Error from Sphinx smart_resolver with ccd_proc #2418
For me for Astropy master (38e5ed8) build_sphinx now works, but for ccdproc mastr (b142c4c3cd36eae898611dd4c5689175a56e5a8e) I still see the error:
File "/Users/deil/Library/Python/2.7/lib/python/site-packages/astropy-0.4.dev8380-py2.7-macosx-10.9-x86_64.egg/astropy/sphinx/ext/smart_resolver.py", line 51, in missing_reference_handler
newnode['reftitle'] = reftarget
TypeError: 'NoneType' object does not support item assignment
Maybe you could also fix the smart_resolve.py to give a useful error message?
Then finding the reference that is causing this error in ccdproc will be trivial.
@cdeil -- I took a look at smart_resolve.py and haven't a clue how to get back to the underlying line that generates the error: the docs is being built from the auto-generated doc in docs/api.
On the bright side, @mdboom , I have a minimal example that demonstrates the error at https://github.com/mwcraig/ccdproc/tree/minimal . In short, the error comes up even if there is only one .py file for which docs are being generated and the contents of that file are
fromastropy.nddataimportNDDataclassCCDData(NDData):
"""A class describing basic CCD data """def__init__(self, *args, **kwd):
super(CCDData, self).__init__(*args, **kwd)
ifself.unitisNone:
raiseValueError("Unit for CCDData must be specified")
It is the subclassing from NDData that leads to the error; subclassing from, e.g. object gives me no error.
We haven't been porting the fixes to astropy.sphinx. @embray: I think I've been seeing you say somewhere we shouldn't be doing that, but maybe I misunderstood...
is astropy_helpers going to be on pypi in a way that allows the use of these extensions and tools without having to go whole hog into the build system and running everything through setup.py?
Activity
cdeil commentedon May 3, 2014
I also get this error if I try to run
python setup.py build_sphinxfor Astropy master:https://gist.github.com/cdeil/6d4748c336676fc0bdeb#file-gistfile1-txt-L68
mwcraig commentedon May 7, 2014
I believe this can be closed, fixed by #2430 (I can now build ccdproc docs with latest astropy-dev)
cdeil commentedon May 7, 2014
For me for Astropy master (38e5ed8)
build_sphinxnow works, but forccdprocmastr (b142c4c3cd36eae898611dd4c5689175a56e5a8e) I still see the error:Full log here: https://gist.github.com/cdeil/bf386b04299b6bc93301
@mwcraig Maybe you don't see the issue because you are not using
ccdprocmaster?mwcraig commentedon May 7, 2014
@cdeil -- good catch, you are correct. I'll try to chase down the reference that is causing the fail.
cdeil commentedon May 7, 2014
Maybe you could also fix the
smart_resolve.pyto give a useful error message?Then finding the reference that is causing this error in
ccdprocwill be trivial.Cut source down to bare minimum needed to reproduce astropy/astropy#2418
mwcraig commentedon May 8, 2014
@cdeil -- I took a look at
smart_resolve.pyand haven't a clue how to get back to the underlying line that generates the error: the docs is being built from the auto-generated doc indocs/api.On the bright side, @mdboom , I have a minimal example that demonstrates the error at https://github.com/mwcraig/ccdproc/tree/minimal . In short, the error comes up even if there is only one
.pyfile for which docs are being generated and the contents of that file areIt is the subclassing from
NDDatathat leads to the error; subclassing from, e.g.objectgives me no error.The output from
python setup.py build_sphinxis at https://gist.github.com/mwcraig/df1265bee9b8a9e6ff87astrofrog commentedon May 13, 2014
For the record, I'm getting the same error with APLpy now.
@mdboom - any ideas?
eteq commentedon May 27, 2014
@mdboom @astrofrog @embray - is this now an astropy-helpers issue? If so, should an issue be made there, and this closed?
astrofrog commentedon May 27, 2014
@eteq - yes, this issue should be moved to astropy-helpers. @cdeil, could you open it there?
cdeil commentedon Jun 2, 2014
I think this issue is now being tracked as the
astropy-helpersissue astropy/astropy-helpers#28 ?astrofrog commentedon Jun 2, 2014
@cdeil - is it the same issue? astropy/astropy-helpers#28 is specifically for classes that are decorated by
InheritDocstring.3 remaining items
Cadair commentedon Jun 3, 2014
Are you still porting fixes from astropy helpers into astropy.sphinx ?
mdboom commentedon Jun 3, 2014
We haven't been porting the fixes to
astropy.sphinx. @embray: I think I've been seeing you say somewhere we shouldn't be doing that, but maybe I misunderstood...Cadair commentedon Jun 3, 2014
is astropy_helpers going to be on pypi in a way that allows the use of these extensions and tools without having to go whole hog into the build system and running everything through
setup.py?mdboom commentedon Jun 3, 2014
Yes.
Cadair commentedon Jun 3, 2014
👍 to that.
Fix astropy/astropy#2418 -- fix crash in smart_resolver when lookup f…
Fix astropy#2418: Fix crash in smart resolver when the resolution doe…
astrofrog commentedon Jun 3, 2014
@mdboom @Cadair - in this case I think it makes sense to backport since it's affecting affiliated packages that don't use astropy-helpers yet.
Merge pull request #33 from mdboom/smart-resolver-fix-crash
Merge pull request #2591 from mdboom/docs/smart-resolver-fix-crash
Fix astropy/astropy#2418 -- fix crash in smart_resolver when lookup f…
Merge pull request astropy/astropy-helpers#33 from mdboom/smart-resol…
Fix astropy/astropy#2418 -- fix crash in smart_resolver when lookup f…
Merge pull request astropy/astropy-helpers#33 from mdboom/smart-resol…