Eric Firing wrote:
> Ryan May wrote:
>
>> Eric Firing wrote:
>>
>>> rcsetup can't get it from backends/__init__.py because that would set
>>> a backend selection in stone. But backends/__init__.py can get it
>>> from rcsetup, and I am in the process of making that change on the
>>> tr
Ryan May wrote:
> Eric Firing wrote:
>> rcsetup can't get it from backends/__init__.py because that would set
>> a backend selection in stone. But backends/__init__.py can get it
>> from rcsetup, and I am in the process of making that change on the
>> trunk. This duplication had annoyed me earl
Eric Firing wrote:
> rcsetup can't get it from backends/__init__.py because that would set a
> backend selection in stone. But backends/__init__.py can get it from
> rcsetup, and I am in the process of making that change on the trunk.
> This duplication had annoyed me earlier, but I didn't do a
Ryan May wrote:
> Hi,
>
> Is there any reason that adding a backend requires modifying both
> rcsetup.py and the __init__.py in the backends subdirectory? Couldn't
> rcsetup.py fetch the list from the __init__.py (or vice-versa)?
>
> Thanks,
>
> Ryan
>
Ryan,
rcsetup can't get it from backe
Hi,
Is there any reason that adding a backend requires modifying both
rcsetup.py and the __init__.py in the backends subdirectory? Couldn't
rcsetup.py fetch the list from the __init__.py (or vice-versa)?
Thanks,
Ryan
--
Ryan May
Graduate Research Assistant
School of Meteorology
University o
