Install issues
tassieg opened this issue · comments
Anaconda for Mac didn't seem to have advanced option in latest version for Install to correct PATH? I did hit "Customize" and it said "Whether to modify the bash profile file to append Anaconda3 to the PATH variable. If you do not do this, you will need to add ~/anaconda3/bin to your PATH manually to run the commands, or run all Anaconda3 commands explicitly from that path" and left it checked. But the install fails "building wheel for vsm" and then tries before sending "Command "/Users/ctgniady/anaconda3/bin/python -u -c "import setuptools, tokenize;file='/private/var/folders/wp/29n9n2nx3pl9dnskvs5j7g_dkr96n6/T/pip-install-7f9qwt2u/vsm/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /private/var/folders/wp/29n9n2nx3pl9dnskvs5j7g_dkr96n6/T/pip-record-mvjf7bf6/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /private/var/folders/wp/29n9n2nx3pl9dnskvs5j7g_dkr96n6/T/pip-install-7f9qwt2u/vsm/"
I have had the same issue. Is there a workaround or update?
I'll investigate this on Tuesday evening, will provide an update here.
@kirtansakariya has been working on this issue, we think it has to do with XCode versions. In order to have a really fast topic modeling implementation, we mixed some C code into our Python for the vsm modeling library. The C code requires compilation on developer machines, but on user installs, the package should have a pre-compiled binary of the C code. It seems this is not working. Kirtan's got a fix for the compilation step, and we'll be working more on packagaing - targeting Friday to have this resolved.
Many thanks!
So @kirtansakariya and I debugged earlier today and believe we've isolated the bug. It broke a few unit tests, but should have the packages released tomorrow.
Thank you. I'm looking forward to the update.
Hi @adrealawrence, we ran into a few more issues, on track to release tomorrow evening.
I fixed some issues last night, and found hopefully the final root cause of some runtime errors.
I had refactored the config files to use a single parser in topicexplorer.config however, I didn't refactor a lot of the extensions or the import/export function, so we've been having lots of errors on recent builds.
I'm correcting those now and will push a new release by 6pm eastern.
@adrealawrence This issue has been resolved with topicexplorer 1.0b223
pip install topicexplorer==1.0b223 should get you the upgrade!
@JaimieMurdock Thank you!