-
Notifications
You must be signed in to change notification settings - Fork 621
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running BitcoinArmory on Mac OS #49
Comments
I took a look into ArmoryQt.py and saw that BDM_LoadBlockchainFile is never used. In my own script I am using instead now: And this appears to be working well. So I guess the unittest code is outdated? |
Indeed, many of those unit-tests were created during the initial development of Armory, which looked a lot different than it does now. I have updated some of the unit tests (and the sample code in the "extras" directory), but not all of the unit-tests. Now that you bring it up, I will spend some time looking at that and/or removing outdated pieces. Instead, I recommend using extras/sample_armory_code.py if you want example code for doing various things with the code base. |
Well, my script is running again, so I am fine right now. Anyways, thanks for your work on BitcoinArmory. Compared to other libs it's 2013/3/1 etotheipi notifications@github.com
|
I recenlty re-installed my MacBook and tried to reinstall Bitcoin Armory using WyseNynja's brew tap. Last time I did it on my own, but I remember that is was kind of a "mess" since I had some trouble with different Python versions.
The brew formula executed without any problems, but when I run "python unittest.py" or other scripts that ran before I get the following error:
"Traceback (most recent call last):
File "unittest.py", line 320, in
BDM_LoadBlockchainFile()
NameError: name 'BDM_LoadBlockchainFile' is not defined"
I also installed BitcoinArmory manually using make and so on. Same result.
Bitcoin client 0.8 is installed and up to date.
Is that a bug in the newest release?
The text was updated successfully, but these errors were encountered: