What's cooler than being sponsored by Google and mentored by NESCent for an entire summer of coding the project of my dreams? Nothing (p < 0.01). Google Summer of Code (GSoC) 2011!

Pageviews

Thursday, August 4, 2011

setup.py, github and segmentation faults

this morning i *think* i got a setup.py file working for downloading necessary components and installing on users' machines. what an amazing invention - the setup.py scripts are brilliant! i then radically reorganized my GitHub account to work with the setup.py script.
for the second half of today, i TRIED to get a popup window to display "Successful Import" when lociNGS imports data (using a tkMessageBox). this led to about a million segmentation faults (i think because the popup isn't connected to the appropriate frame or something. but i could be totally wrong about that because my brain ain't workin' so good right now).
plan for tomorrow is to take a fresh look at the popup issue (or make a work around) and continue to clean up code. and i should upload some test data for interested parties. tgi(almost)f.

1 comment:

Sarah;Great work on the reorganization; setup.py really is magic. To finish off getting things organized, you should create a locings folder, create a __init__.py file in it (which can be blank, it indicates that it is an importable module), then move constructionMDB.py, convertingLociNGS.py, and seqlite_mod.py in there.

Then find_packages will grab this and install it along with your lociNGS.py script. Then if you adjust imports to be `from locings.constructionMDB import` you will be able to pull these in and the lociNGS.py script will run without any path dependence. Sweet.

For the segfaults/window problem, another solution is to create a label (like label1 you've already got in the window) and the text for it as things get imported.