diff options
| author | Joseph Hunkeler <jhunkeler@users.noreply.github.com> | 2016-09-23 09:46:02 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-09-23 09:46:02 -0400 |
| commit | cf1deed7a4474505ec6a645ba4e20e2aa76b63cd (patch) | |
| tree | 51eb2eabe94a7d2b29fe34ed421bfc277cb41f48 /source | |
| parent | c5379c5ae6a3679fd708f42c71d9440d6344cdff (diff) | |
| download | astroconda-cf1deed7a4474505ec6a645ba4e20e2aa76b63cd.tar.gz | |
Update faq.rst
Fix formatting
Diffstat (limited to 'source')
| -rw-r--r-- | source/faq.rst | 6 |
1 files changed, 2 insertions, 4 deletions
diff --git a/source/faq.rst b/source/faq.rst index b585f22..10bf718 100644 --- a/source/faq.rst +++ b/source/faq.rst @@ -94,8 +94,7 @@ If you are already using AstroConda under a Python 2 environment, you may simply Why is IRAF/PyRAF less functional under Python 3? ================================================= -The Python code in ``stsdas``, for example, is targeted specifically for Python 2.7 and earlier. If the demand for Python 3 support under IRAF is great enough we may be able to pull our resources to accommodate the community. It is recommended to install IRAF into its - own environment under Python 2.7: +The Python code in ``stsdas``, for example, is targeted specifically for Python 2.7 and earlier. If the demand for Python3 support under IRAF is great enough we may be able to pull our resources to accommodate the community. It is recommended to install IRAF into its own environment under Python 2.7: ``conda create -n iraf27 python=2.7 iraf pyraf stsci && source activate iraf27`` @@ -128,6 +127,5 @@ RHEL/CentOS >=6, Fedora >=14 Will AstroConda interfere with other scientific distributions (e.g. SciSoft)? ============================================================================= -**Probably**, however unlike Ureka, we do not impose any restrictions on your environment or issue compatibility -warnings at run-time. It is your responsibility to maintain a functional shell environment so [insert scientific distribution here] does not conflict with your Anaconda installation. +**Probably**, however unlike Ureka, we do not impose any restrictions on your environment or issue compatibility warnings at run-time. It is your responsibility to maintain a functional shell environment so [insert scientific distribution here] does not conflict with your Anaconda installation. |