Create __init__.py files on install about six-library HOT 6 CLOSED

I'm kind of surprised but it actually worked for me. I just built it with W7, whatever compiler Visual Studio Express 2013 ships with, and python 2.7.9 from anaconda. Until this is figured out you can probably get away with making the files by hand.

from six-library.

I needed to add this to my PYTHONPATH to get it to work, but also was surprised no __init__.py was required. I think its worth adding the __init__.py because its standard in module creation. We should also consider creating a setup.py installer (directly into the python library) or creating a mechanism for installing the egg from the geohub page using pip or something similar. Having a "pip install/update six-library" or "conda install/update six-library" would be very beneficial to us and our users. I'd use it.

from six-library.

I'm getting an __init__.py when I built and installed - it's definitely intended to be there.

I did look into methods of packaging and creating a setup.py a long time ago, but I haven't had the time to follow through.

from six-library.

I just checked my recent six install and the __init__.py are populated as expected. \Lib\site-packages\pysix and \Lib\site-packages\coda. It has been some time since I last checked.

I perform one call for my build sequence:
waf configure --prefix ..\six64.release -o target64.release --disable-warnings install

from six-library.

The init.py files are populating for me now, as well. If I did anything differently, I am not aware of it.

From: mbojrab [mailto:[email protected]]
Sent: Thursday, January 21, 2016 10:48 AM
To: ngageoint/six-library [email protected]
Cc: Jonathan Means [email protected]
Subject: Re: [six-library] Create init.py files on install (#43)

I just checked my recent six install and the init.py are populated as expected. \Lib\site-packages\pysix and \Lib\site-packages\coda. It has been some time since I last checked.

I perform one call for my build sequence:
waf configure --prefix ..\six64.release -o target64.release --disable-warnings install

—
Reply to this email directly or view it on GitHubhttp://cp.mcafee.com/d/k-Kr4xAe6zqb3Xb9EVhjvodTdIIczxNEVvvdLzCm6kjhOqejqdTHLe6zCVEVudEEIEFLCzBNxYS8RxIOuMVnZxg5aEqTjBPqG6JQVsSUqek7rWU_R-76zAttx7HTbFFFIsy-CeKYVR4kRHFGTujVkffGhBrwqrhdECXYOqemmmkTDDD3tPpesRG9px6kOrp3BYwhQzZpgDB91Vs-h2eNbpaB6_Fz386iFhLRRvxcKyepshjjvpdAaJMJZ00Lcfc8IBSm4tbydorcDIel_okelgRKDbwGx4jUzapdIxOVJwsqehNI5-Aq83iTigunfAgzIiNFtd40B7ZDVEw5hmk9j5hnByNEwtAvZ3h1m1EwB2AZffd41EE0NxAQkCTPhOrKJga.

The information contained in this communication is confidential, is intended only for the use of the recipient(s) named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message or any copy of it from your computer system.

from six-library.

@JonathanMeans

I just managed to reproduce this problem. I had an issue in a swig binding that caused the build to fail. After fixing that issue, subsequent ./waf installs would not create the __init__.py. A distclean and reconfigure seems to put everything back in working order, but something is not working quite as intended so I'm reopening this issue.

ed: This was on linux, so I'm guessing the problem is not platform specific.

from six-library.