Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Mar 05 08:15
    ax3l commented #1269
  • Mar 05 08:14
    ax3l commented #1269
  • Mar 05 08:13
    ax3l commented #1269
  • Mar 05 00:46
    jakirkham commented #1269
  • Mar 05 00:42
    ax3l commented #1269
  • Mar 05 00:41
    ax3l commented #1269
  • Mar 05 00:41
    ax3l commented #1269
  • Mar 05 00:16
    ax3l commented #1269
  • Mar 05 00:15
    ax3l commented #1269
  • Mar 05 00:14
    ax3l commented #1269
  • Mar 05 00:14
    ax3l commented #1269
  • Mar 05 00:13
    ax3l commented #1269
  • Mar 05 00:12
    ax3l commented #1269
  • Mar 05 00:11
    ax3l commented #1269
  • Mar 05 00:10
    ax3l commented #1269
  • Mar 04 20:41
    beckermr commented #1269
  • Mar 04 20:33
    jakirkham commented #1269
  • Mar 04 20:31
    jakirkham labeled #1269
  • Mar 04 20:31
    jakirkham opened #1269
  • Mar 03 20:59

    github-actions[bot] on gh-pages

    deploy: 2b0815f9c4dfd0f744e7816… (compare)

Chris Burr
@chrisburr
The conda-forge importlib-metadata package is available for Python 3.9 so you can make it dependency for all Python versions
Ben Mares
@bmares_gitlab
It's part of the standard library since 3.8, so it's unnecessary. But you think I should include it anyway?
Wolf Vollprecht
@wolfv
@bmares_gitlab sometimes these packages are empty, just to help with this exact problem
Ben Mares
@bmares_gitlab
Great, I'll simply include it then, thanks!
James Webber
@jamestwebber
hi all. just joined as maintainer for pyro-ppl-feedstock which depends on pytorch. Yesterday there was a new release of both packages and pyro-ppl depends on the latest release of pytorch, which is not yet on conda-forge (it is available on the pytorch channel). I updated the feedstock but I'm wondering if it will be available, given that the build fails?
Matthew R. Becker
@beckermr
if the build fails, then it likely won't get uploaded
you may be able to configure the feedstock to use the pytorch channel
I have lost track of this detail
someone else from core may be able to help
James Webber
@jamestwebber
ah it seemed like that was not recommended
but if it's possible that works
Wolf Vollprecht
@wolfv
@jamestwebber I think ideally you'd help out on the pytorch feedstock to get the new release into conda-forge
James Webber
@jamestwebber
:D fair enough
there are multiple outstanding PRs on pytorch-cpu-feedstock and I am not eager to become a maintainer there...but I can open a PR
James Webber
@jamestwebber
oh actually it looks like they are moving: conda-forge/pytorch-cpu-feedstock#36
1 reply
Matthew R. Becker
@beckermr
I agree with @wolfv
unfortunately if the pytorch builds timeout, then we have to build by hand
and that process is annoying
the pytorch maintainers are the best ppl to ask on this
BTW @jamestwebber we have jax so numpyro would be cool to have around if it is not already
James Webber
@jamestwebber
it looks like it's already up
i'm not sure who maintains it
oh it's one of the Pyro maintainers, that makes sense
Matthew R. Becker
@beckermr
+1
Bastian Zimmermann
@BastianZim
Question, based on the discussion further up: Is importlib-metadata actually empty for >3.7?
From what I can find in conda-forge/importlib_metadata-feedstock#47 there was an idea but I cannot find it implemented here: https://github.com/conda-forge/importlib_metadata-feedstock/blob/master/recipe/meta.yaml
Or am I missing something?
(I have the same problem as above so I was just looking this up :smile: )
Bradley Dice
@bdice
I just merged a PR to a Cython package, adding osx-arm64 builds. The builds passed but it appears that the osx-arm64 builds fail on import. I should mark as broken and remove build_platform: {osx_arm64: osx_64} from conda-forge.yml right? Just making sure I don't miss a step since I'm "un-migrating."
8 replies
Jan Janssen
@jan-janssen
Can somebody from core take a look at conda-forge/defusedxml-feedstock#6 - I opened a separate pull request to fix the failing tests conda-forge/defusedxml-feedstock#7 and another one for adding myself as a maintainer to continue updating the package in future conda-forge/defusedxml-feedstock#8
Kyle Gorman
@kylebgorman
Why does the Mac OS X automatically set -std=c++14 in CXXFLAGS? Anything I can do about that other than a magical regex to filter that out?
jakirkham
@jakirkham
Meaning you want C++17 support or do you want to use an older one?
Regarding C++17 on macOS please see conda-forge/clang-compiler-activation-feedstock#17
Axel Huebl
@ax3l
Does someone like to review a new Python package? :) conda-forge/staged-recipes#14175
Wolf Vollprecht
@wolfv
this could be a fun addition to conda-build / conda-forge linters: https://github.com/koalaman/shellcheck
Axel Huebl
@ax3l
Wuhu, ready for merge :) conda-forge/staged-recipes#14176
Wolf Vollprecht
@wolfv
ah cool, maybe we could use that in xtensor-blas to replace FLENS!
Axel Huebl
@ax3l
Got another one for LAPACK++ ready :) conda-forge/staged-recipes#14178
Axel Huebl
@ax3l
Don't hesitate to give their libs a try - ICL is definitely the authority for all things BLAS and LAPACK :D
There is more to come on their roadmap over the next months. Already includes batching and CUDA, HIP already in their development branch, SYCL IIRC as well planned, etc.
Ben Mares
@bmares_gitlab
I mistakenly published a release candidate of https://github.com/conda-forge/pyscaffold-feedstock to the main channel. Can I change the label to rc with repodata-patches, or should I mark it as broken?
Chris Burr
@chrisburr
@bmares_gitlab This one noarch/pyscaffold-4.0.1rc1-pyhd8ed1ab_0.tar.bz2? And which label did you intend to use?
Ben Mares
@bmares_gitlab
Exactly. It's a release candidate, so I think it should be the rc label, right?
Chris Burr
@chrisburr
(it will take a while for the CDN to update and it to be removed from the main channel)
Ben Mares
@bmares_gitlab
Thanks so much!!!!! (I was feeling bad for messing that up.)
Shortly before asking for help, I tried to solve the problem myself by creating a new rc branch, adding pyscaffold_rc as the channel target in recipe/conda_build_config.yaml, making an empty commit and corresponding pull request to request a rerender. Was I on the right track? Should I keep or delete this branch?
Chris Burr
@chrisburr
No worries, we've all done similar things :)
That's the right thing to do, but it doesn't have any affect one a build has already been uploaded. We have this repo for marking packages as "broken" but I don't think there is anything automated for moving things to dev or rc channels
Ben Mares
@bmares_gitlab
@chrisburr Wonderful, I think I'm slowly getting a sense for how all this stuff works. I really appreciate it. Since we're neighbors, I'll gladly pay for a beer once I'm vaccinated. ;)
1 reply
Brandon Andersen
@bandersen23
Could someone help me troubleshoot why conda-forge/pytkdocs-feedstock#7? I've documented a few things in conda-forge/pytkdocs-feedstock#9 as well. I'm encountering some odd errors that I don't understand. Thank you!
Axel Huebl
@ax3l
Hi, just in case someone is around, here is a new staged recipe ready for merging: conda-forge/staged-recipes#14178
This one (LAPACK++) is a follow-up of a similar one for BLAS++ merged yesterday