Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 20:38
    mingwandroid synchronize #3812
  • 19:55

    conda-bot on gh-pages

    remove old docs for 3816 docs for pr 3816 (compare)

  • 19:53

    conda-bot on gh-pages

    remove old docs for 3817 docs for pr 3817 (compare)

  • 19:53
    rrigdon assigned #3816
  • 19:53
    rrigdon assigned #3817
  • 18:09
    mingwandroid commented #3817
  • 18:03
    mingwandroid commented #3817
  • 17:57
    mingwandroid commented #3817
  • 17:46
    mingwandroid commented #3816
  • 17:46
    mingwandroid commented #3816
  • 17:41

    conda-bot on gh-pages

    remove old docs for 3817 docs for pr 3817 (compare)

  • 17:40

    conda-bot on gh-pages

    remove old docs for 3816 docs for pr 3816 (compare)

  • 17:39

    conda-bot on gh-pages

    docs for pr 3817 (compare)

  • 17:39
    cla-bot[bot] labeled #3817
  • 17:39
    rrigdon opened #3817
  • 17:39

    conda-bot on gh-pages

    docs for pr 3816 (compare)

  • 17:38
    cla-bot[bot] labeled #3816
  • 17:38
    rrigdon opened #3816
  • 16:09
    mingwandroid synchronize #3812
  • 15:40
    mingwandroid synchronize #3812
Duncan Macleod
@duncanmmacleod

on another topic, is there a way to disentagle a recipe called package with an output of the same name?

I would like to have a recipe where the top-level build gets split up into subpackages using outputs/files, where one output has the same name as the top-level package. That output’s requirements are a proper subset of the overall build requirements, but conda-build seems to preferentially select the output’s requirements list over the top-level list when building the environments to use for the top-level build stage. Is that bug, or am I just using conda-build and outputs incorrectly?

Ray Donnelly
@mingwandroid
Not really. I mean conda-build could do some icky code around that and likely does but that's edge-case stuff, mainly as we'll just stick -suite onto the end of the top level package name..
We should to be honest error out when the top level matches an output as it's more trouble than it is worth.
I know this can be a bit tricky for infra / tooling but cb provides enough render/listy things to help with that I hope.
Duncan Macleod
@duncanmmacleod
I’ve worked around it now by just renaming the top-level package
Ray Donnelly
@mingwandroid
ok cool
as I do each time too ;-)
Duncan Macleod
@duncanmmacleod
I’m just a pedant and would really like the conda-forge feedstock to be named for the output, rather than the modified recipe name
Ray Donnelly
@mingwandroid
Me too
PRs welcome that attempt to fix it I suppose!
Duncan Macleod
@duncanmmacleod
does conda-build support negative matches for outputs/files?
Andrew Annex
@AndrewAnnex
hey all, I was wondering if someone here can take a look at an issue I'm having with conda-build, I made a PR with a possible fix here conda/conda-build#3773, was curious to figure out how best to add a unit test also.
Ray Donnelly
@mingwandroid
It looks simple enough that it may not need one
Andrew Annex
@AndrewAnnex
I also noted an issue with the using the "fn" parameter in the meta.yaml to rename files on macos, should I submit a second issue for that?
Ray Donnelly
@mingwandroid
Sure!
Andrew Annex
@AndrewAnnex
this issue (well the first one) is blocking a fix for my conda-forge package which I would like to be fixed by the end of the month, about how often do conda build releases get made
Andrew Annex
@AndrewAnnex
okay I opened #3776 that has this other issue detailed
Matthew R. Becker
@beckermr
does anyone have hints on how I can go about solving this issue?
reading the source has been less than enlightening
for me
Andrew Annex
@AndrewAnnex
could someone give me some feedback on #3773 and respond to my issue #3776 ? I could also attempt to fix #3776 if someone can point me to the right place in the codebase
Dan Cotruta
@catmandi_twitter
hi all
i am having some trouble building a simple conda package to use in a local channel
but conda index is not picking up my package
Douglas Lowe
@douglowe
Can anyone tell me where I'm going wrong with my subpackages here: https://github.com/UoMResearchIT/staged-recipes/blob/prismatic_subpackages/recipes/prismatic/meta.yaml
I can't get the main package to load the subpackages as dependencies, nor do the subpackages load any dependencies other than libcxx. I've tried to follow the documentation (https://conda.io/projects/conda-build/en/latest/resources/define-metadata.html#outputs-section) but what is suggested there just doesn't seem to work.
Ray Donnelly
@mingwandroid
do you want the gui package to depend upon the cli one at runtime here?
look at the xgboot example
Matthew R. Becker
@beckermr
I have a very basic question about conda build
here is a snippet from pytest installed in the host section
#!/usr/bin/env python
# EASY-INSTALL-ENTRY-SCRIPT: 'pytest==3.6.2','console_scripts','pytest'
__requires__ = 'pytest==3.6.2'
import re
import sys
from pkg_resources import load_entry_point

if __name__ == '__main__':
    sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0])
    sys.exit(
        load_entry_point('pytest==3.6.2', 'console_scripts', 'pytest')()
    )
why is it using /usr/bin/env instead of the full host prefix here?
FWIW, on a normal install, this is simply the path of the env.
Matthew R. Becker
@beckermr
And my related question is whether or not I can somehow force conda to do that during conda-build
Matthew R. Becker
@beckermr
ah this is related to the length of the lines
the conda build ones are too long for most systems to deal with
the fun edge case here is that if you are working on a build on OSX that is doing somewhat dumb things with DYLD_LIBRARY_PATH, then you end up with the /usr/bin/env invoking SIP and breaking everything
blarg
Andrew Annex
@AndrewAnnex
thanks for merging in #3773, I believe that will fix my conda-forge feedstock once a new release is made, how soon until 3.8.11?
Ray Donnelly
@mingwandroid
Well, IMHO /usr/bin/env python is the correct invocation in that we respect and use PATH and not having to rewrite files per-env is a saving.
Jonathan J. Helmus
@jjhelmus
@beckermr That snippet is created by setuptools/pip not conda-build/conda. Entry points created by conda do not use pkg_resources, https://github.com/conda/conda/blob/4.7.12/conda/gateways/disk/create.py#L85-L106
Matthew R. Becker
@beckermr
Most of it is but not the shebang line
Let me show you from some packages
check out the pytest package here: https://anaconda.org/conda-forge/pytest/files
here is the contents of the command line util
(base) localhost:pytest-5.2.1-py37_0 Matt$ cd bin/
(base) localhost:bin Matt$ cat pytest 
#!/opt/anaconda1anaconda2anaconda3/bin/python

# -*- coding: utf-8 -*-
import re
import sys

from py.test import main

if __name__ == '__main__':
    sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0])
    sys.exit(main())
Notice that the #! line is the text that conda replaces with the prefix