Yes, I did notice that wview.py in the schemas subdirectory - now a 
weewx.py in the schemas directory
$ pwd
/usr/share/weewx
$ ls schemas/
__init__.py  __init__.pyc  wview.py  wview.pyc

I did also notice a schemas.py in the users directory too - but I don't 
think that would be causing a conflict.

If I add in the print sys.path I get the following.

In user/extensions.py:
...
import sys
print sys.path
import schemas.wview
schema = schemas.wview.schema + [('appTemp', 'REAL')]
# END OF FILE

$ sudo wee_database
['/usr/share/weewx', '/usr/lib/python2.7', 
'/usr/lib/python2.7/plat-x86_64-linux-gnu', '/usr/lib/python2.7/lib-tk', 
'/usr/lib/python2.7/lib-old', '/usr/lib/python2.7/lib-dynload', 
'/usr/local/lib/python2.7/dist-packages', 
'/usr/lib/python2.7/dist-packages', 
'/usr/lib/python2.7/dist-packages/PILcompat', 
'/usr/lib/python2.7/dist-packages/gst-0.10', 
'/usr/lib/python2.7/dist-packages/gtk-2.0', '/usr/lib/pymodules/python2.7']
Traceback (most recent call last):
  File "/usr/bin/wee_database", line 18, in <module>
    import user.extensions      #@UnusedImport
  File "/usr/share/weewx/user/extensions.py", line 23, in <module>
    import schemas.wview
ImportError: No module named wview

So, this looks to confirm the "unique" circumstance that you have 
discovered.

Some background version info:
$ python --version
Python 2.7.6
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 14.04.5 LTS
Release:        14.04
Codename:       trusty

$ dpkg -l weewx
Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                Version        Architecture   Description
+++-===================-==============-==============-===========================================
ii  weewx               3.7.1-1        all            weather software

Regards,
Christopher

On Tuesday, 28 March 2017 23:33:39 UTC+11, Tom Keffer wrote:
>
> I had forgotten that!  
>
> Be sure to read the Nov 26 post in that thread and see if it applies to 
> you:
>
> Question: when you have this problem, do you by any chance have a file 
>> named weewx.py in the schemas subdirectory? I am finding that if I do, I 
>> get this error.
>> For reasons I don't quite understand, the presence of a module 
>> schemas.weewx, *even if you don't import it*, screws up everything else 
>> in schemas subdirectory. I suppose because it is confusing it with the 
>> *package* weewx, or .... mumble... something.
>
>
> -tk
>
> On Tue, Mar 28, 2017 at 5:27 AM, mwall <[email protected] 
> <javascript:>> wrote:
>
>> christopher,
>>
>> it looks like you might be suffering from this issue:
>>
>> https://github.com/weewx/weewx/issues/54
>>
>> there is a workaround, but it would be nice if we could find out the root 
>> cause and fix it once and for all.
>>
>> m
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to