Repository navigation
Narrative doc for new enable_deprecations_as_exceptions() options - #259
Conversation
|
Um... Is |
|
Nope, cookiecutter branch is the one we supposed to do any development. "master" is the legacy branch, and rendered is the rendered cookiecutter one. |
|
Although, I think we still have all the affiliated docs in astropy core. |
|
In the affiliated doc in the core, it says, "The package template has comments in the I'll resolve the conflicts here then. |
|
@pllim - I've changed your based branch, but sadly it didn't automatically realized that your changes should apply to ``{{ cookiecutter.package_name }}/{{ cookiecutter.module_name }}/conftest.py |
|
Rebased to the right "upstream". |
| ## exceptions. For Astropy v2.0 or later, there are 2 additional keywords, | ||
| ## as follow. | ||
| ## To ignore some modules that produce deprecation warnings on import, add: | ||
| ## modules_to_ignore_on_import=['module_1', 'module_2'] |
There was a problem hiding this comment.
aren't these packages rather than modules? maybe list the ones that are currently ignored.
There was a problem hiding this comment.
I guess you are right as far as user is concerned although technically it can be either package or module. Sure, I'll list them.
|
Thanks, this looks good to me. |
Narrative doc for astropy/astropy#6223