You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I am wondering if JCSDA is still using jedi-tools-env. Back in the days when I was at JCSDA, we used jedi-tools-env to run some of the GitHub admin jobs, for example managing labels across GitHub repositories, collecting GitHub statistics, ...
I don't recall exactly for which of these tasks, but I had to add a +excel variant to py-pandas for one of them. Now, the +excel variant is becoming problematic, since newer versions of py-pandas require py-python-calamina -> py-maturin -> rust as dependencies. This is the full rust, not just rust-bootstrap. And py-maturin doesn't compile with Intel Classic or Intel LLVM either.
Describe the solution you'd like
If we don't need it anymore, I'd like to get rid of the +excel variant for py-pandas. Even better, if jedi-tools-env is no longer needed (maybe/hopefully @eap is handling all of these tasks differently with Terraform nowadays?), I'd like to get rid of it entirely.
If none of this is possible, then we should modify the common package definitions such that the +excel variant is only used with the GCC compiler (which is also the only compiler that triggers the build of jedi-tools-env).
Additional context
See #831 (comment) for the PR that added the +excel variant.
The text was updated successfully, but these errors were encountered:
jedi-tools-env is still being used for github reporting and a couple other cases. That said, it would be easy enough to use CSVs instead of excel sheets and it's only being done this way because of historical momentum. I'm entirely comfortable removing this variant.
jedi-tools-env is still being used for github reporting and a couple other cases. That said, it would be easy enough to use CSVs instead of excel sheets and it's only being done this way because of historical momentum. I'm entirely comfortable removing this variant.
That's awesome to hear, thanks very much. I'll do that. It will trim down the number of packages by at least 5 or 10 just because of that (and allow us to update pandas).
Is your feature request related to a problem? Please describe.
I am wondering if JCSDA is still using
jedi-tools-env
. Back in the days when I was at JCSDA, we usedjedi-tools-env
to run some of the GitHub admin jobs, for example managing labels across GitHub repositories, collecting GitHub statistics, ...I don't recall exactly for which of these tasks, but I had to add a
+excel
variant topy-pandas
for one of them. Now, the+excel
variant is becoming problematic, since newer versions ofpy-pandas
requirepy-python-calamina -> py-maturin -> rust
as dependencies. This is the fullrust
, not justrust-bootstrap
. Andpy-maturin
doesn't compile with Intel Classic or Intel LLVM either.Describe the solution you'd like
If we don't need it anymore, I'd like to get rid of the
+excel
variant forpy-pandas
. Even better, ifjedi-tools-env
is no longer needed (maybe/hopefully @eap is handling all of these tasks differently with Terraform nowadays?), I'd like to get rid of it entirely.If none of this is possible, then we should modify the common package definitions such that the
+excel
variant is only used with the GCC compiler (which is also the only compiler that triggers the build ofjedi-tools-env
).Additional context
See #831 (comment) for the PR that added the
+excel
variant.The text was updated successfully, but these errors were encountered: