-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Add FERC XBRL to SQLite data extractor #21261
Add FERC XBRL to SQLite data extractor #21261
Conversation
Merge upstream
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( I do have some suggestions for making it better though... For recipes/catalystcoop.arelle-mirror:
Documentation on acceptable licenses can be found here. |
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
I am willing to be listed as maintainer |
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/catalystcoop.arelle-mirror:
|
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/catalystcoop.arelle-mirror:
For recipes/catalystcoop.ferc-xbrl-extractor:
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/catalystcoop.arelle-mirror:
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Hi @xhochy just wanted to check-in and see if these recipes are good now. We can try to remove the lxml build dependency if need be, however we are trying to make as minimal changes to the Arelle library as possible. Thanks! |
@xhochy Do you have any additional pointers on what we need to do to get this merged in? |
@conda-forge-admin, please ping team |
Hi! This is the friendly automated conda-forge-webservice. I was asked to ping @conda-forge/staged-recipes and so here I am doing that. |
Things I could imagine being the issue with getting this merged... The The Windows builds are failing. I've previously had noarch packages on here where the Windows builds failed and there was some known problem that made that the expected behavior and it wasn't a problem (See #12902 and #18726) but I don't know if that's what's going on here. Isn't there some actual code compilation happening inside Arelle? It seems like it's intended to work on Windows from the We're packaging our fork of Arelle and not the official Arelle. This is more complex. Early this year when we started using Arelle it had fallen into disrepair, and wasn't even available via PyPI. We needed to make some very minor changes to deal with a locale bug (and maybe others? @zschira what changes other than packaging for release on PyPI did we end up making?). Since then it's been taken over by some company, and they've started doing some maintenance on the library, including modern packaging and releases on PyPI. Ultimately of course we would prefer to use the official Arelle release (assuming we can get our minor bugfixes integrated) but we are currently trying to do our own very delayed release, and are apprehensive about swapping out this low level dependency immediately beforehand. If this is a blocking concern that will prevent the package from getting released on Any direction y'all can provide would be much appreciated. This is the last thing preventing us from doing our own release and we'd really like to get it cleared up! Thank you for all your hard work! |
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
We've moved to using the official version of @conda-forge-admin, please ping team |
Hi! This is the friendly automated conda-forge-webservice. I was asked to ping @conda-forge/staged-recipes and so here I am doing that. |
It does seem like there's some platform-specific compilation going on in here, at least for Windows, with DLLs and binary outputs (maybe for the GUI or CLI tools they bundle alongside the python library?), so it seems a little weird that it would be So it seems like we need to do one of the following:
Looking at the end of the build outputs it seems like it might just be the case that it's failing because it generates a binary output (successfully?) but realizes that the package has been marked
|
@sagesmith-wf Do you happen to have any insight into what might be going on here with the Windows builds? |
@zaneselvans, I am unfamiliar with this error or the tooling, but the error seems indicative or an architecture mismatch. I would double check that you are using a 64bit python on 64bit windows because the error you posted is looking for system32 which seems wrong since the staged recipe says |
@zschira Can we just disclaim windows compatibility for the moment, since there are clearly some components that won't work without additional effort? I imagine the Python library portion itself will work fine and it's just the GUI + CLI tools that are running into OS-specific build issues. I.e. change the build section to: build:
skip: true # [win]
script: {{ PYTHON }} -m pip install . -vv
number: 1 |
❤️ Thank you! |
I suspect you need some entry_points to make conda-build happy with installing this as noarch on Windows. Should be an easy fix in the feedstock. |
build: | ||
noarch: python | ||
script: {{ PYTHON }} -m pip install . -vv | ||
number: 0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps add:
build:
# ... what's already there
entry_points:
- arelleCmdLine = arelle.CntlrCmdLine:main
- arelleGUI = arelle.CntlrWinMain:main
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- pip | ||
|
||
about: | ||
home: https://pypi.org/project/arelle-release/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
perhaps also add dev_url: https://github.com/Arelle/Arelle
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- pip | ||
|
||
about: | ||
home: https://github.com/catalyst-cooperative/ferc-xbrl-extract |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this appears to actually be:
https://github.com/catalyst-cooperative/ferc-xbrl-extractor # not "extract"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whoops, yes, will fix this.
about: | ||
home: https://github.com/catalyst-cooperative/ferc-xbrl-extract | ||
summary: A tool for extracting data from FERC XBRL Filings. | ||
dev_url: https://github.com/catalyst-cooperative/ferc-xbrl-extract |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if the home
is already github, this doesn't add much
Maybe we can turn these into issues on the respective feedstocks? Filed a couple, but please feel free to file more |
Checklist
url
) rather than a repo (e.g.git_url
) is used in your recipe (see here for more details).