-
Notifications
You must be signed in to change notification settings - Fork 92
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
Workaround for broken Nightly - ConfigParser.NoOptionError #70
Comments
@MichaelRColton can you raise a PR with this fix? It seems like a reasonable solution :) |
Is it? I don't really understand the original code well enough, so I just hard coded values that allowed me to get a Bom exported, but maybe we lose the ability to change the file name and type by doing this. More than anything, opening this issue was meant to be a heads up and a temporary work around for other people experiencing the issue. (It's not that I'm unwilling to do more, I just don't think I am really up to doing it right) |
This issue still exists: In the KiCad output, get: `Run command: Command error. Return code 1 I am not complaining, just adding info. I haven't tried the workaround or looked at the code. I did not create the bom.ini myself, KiBOM seems to have created it. I did look at the bom.ini and indeed there does not seem to be a 'output_file_name' field. |
Just a quick look at the commit in schneidersoft's clone seems like it might be more elegant. But I don't have deep knowledge about the code. |
But the fix in schneidersoft's clone also throws an exception: TypeError: get() got an unexpected keyword argument 'default' |
Now, schneidersoft's clone seems to have fixed this issue, and this repository seems to still have this issue. Schneidersoft's code seems to have significantly changed preferences.py. This repository seems to have made significant changes to ease installation (using pip instead of downloading and unzipping an archive.) Ideally, the repositories should be merged. Thanks to all parties. |
Added fallbacks to the current default values, avoiding an exception. Should close issue SchrodingersGat#70
This should now have been fixed in #121 |
At some point in the Nightly builds of KiCAD, something changed that seems to have broken KiBoM. I was getting ConfigParser.NoOptionErrors in two places.
I was able to work around the issue (in an inelegant way) by changing lines 143-144 preferences.py in bomlib to:
The text was updated successfully, but these errors were encountered: