Author terry.reedy
Recipients ADataGman, brett.cannon, docs@python, eric.snow, ncoghlan, terry.reedy
Date 2019-02-13.04:35:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1550032536.55.0.41841593392.issue35927@roundup.psfhosted.org>
In-reply-to
Content
AData> You log and output show that you problem is as described: package 'sound' is in directory "C:/" and "C:/" is not is sys.path.  Possible remedies:
1. Add "C:/" to sys.path at the top of each module that imports sound.  This is a nuisance.
2. Move the sound package to 'C:\\Users\\user\\AppData\\Local\\Programs\\Python\\Python37\\lib\\site-packages'.  This can also a nuisance.
3. Add a file named 'C.pth' and containing "C:/" to the site-packages.  ('pth' abbreviates 'path'.)  This makes C:/ an extension of site-packages.  But all the non-python stuff in C: likely makes this a bad idea.
4 (3 improved). Add a directory such as "C:/pyprojects", make the contents of the .pth file "C:/pyprojects", and move sound to pyprojects.  
This is what I have done.  When I install a new version of Python, I copy the .pth file to the new site-packeges directory.  Works great.
History
Date User Action Args
2019-02-13 04:35:36terry.reedysetrecipients: + terry.reedy, brett.cannon, ncoghlan, docs@python, eric.snow, ADataGman
2019-02-13 04:35:36terry.reedysetmessageid: <1550032536.55.0.41841593392.issue35927@roundup.psfhosted.org>
2019-02-13 04:35:36terry.reedylinkissue35927 messages
2019-02-13 04:35:36terry.reedycreate