https://pantsbuild.org/ logo
Powered by
#general
  • d

    dry-analyst-73584

    01/26/2017, 8:41 PM
    Epic results 🙂
  • e

    enough-analyst-54434

    01/26/2017, 8:57 PM
    That's great to hear. Its nice to have big speedups to squash the baby bottlers with.
  • l

    loud-electrician-45072

    01/27/2017, 8:25 PM
    I'm seeing 
    FAILURE: setup-py target(s) must provide an artifact.
    but not seeing any documentation on how to configure artifacts for python builds. Any pointers? Am I making a stupid/noob mistake?
  • w

    witty-crayon-22786

    01/27/2017, 8:26 PM
    what does the target definition look like?
  • l

    loud-electrician-45072

    01/27/2017, 8:26 PM
    I'm looking to lift libraries out of a monolithic setup.py based repo so setup-py compat is important
  • w

    witty-crayon-22786

    01/27/2017, 8:26 PM
    and what command are you running
  • w

    witty-crayon-22786

    01/27/2017, 8:26 PM
    setup-py
    is only used for publishing
  • w

    witty-crayon-22786

    01/27/2017, 8:26 PM
    (in pants.)
  • l

    loud-electrician-45072

    01/27/2017, 8:26 PM
    ohhhhh
  • l

    loud-electrician-45072

    01/27/2017, 8:27 PM
    sorry
  • l

    loud-electrician-45072

    01/27/2017, 8:27 PM
    I thought generate meant like a project skeleton
  • l

    loud-electrician-45072

    01/27/2017, 8:27 PM
    not generate artifacts
  • l

    loud-electrician-45072

    01/27/2017, 8:27 PM
    I think that clears it up
  • w

    witty-crayon-22786

    01/27/2017, 8:27 PM
    see 
    ./pants help setup-py
  • l

    loud-electrician-45072

    01/27/2017, 8:27 PM
    Generate setup.py-based Python projects.
  • w

    witty-crayon-22786

    01/27/2017, 8:27 PM
    ...hah
  • l

    loud-electrician-45072

    01/27/2017, 8:27 PM
    oic
  • l

    loud-electrician-45072

    01/27/2017, 8:27 PM
    there are mentions of build artifacts
  • w

    witty-crayon-22786

    01/27/2017, 8:29 PM
    yea, sorry. the help isn't particularly helpful there. the expectation is that 
    setup-py
    is only used to publish to pypi, but that the 
    ./pants compile $target
    or 
    ./pants test $target
    goals are used within the repo
  • l

    loud-electrician-45072

    01/27/2017, 8:29 PM
    got it, thanks for the clarification
  • w

    witty-crayon-22786

    01/27/2017, 8:29 PM
  • w

    witty-crayon-22786

    01/27/2017, 8:29 PM
    ..ah, yea. it explains this.
  • l

    loud-electrician-45072

    01/27/2017, 8:30 PM
    indeed!
  • l

    loud-electrician-45072

    01/27/2017, 8:30 PM
    I looked it over already but it didnt click the first time
  • l

    loud-electrician-45072

    01/27/2017, 8:31 PM
    Copy code
    provides=setup_py(
    name='pantsbuild.pants.testinfra',
    version='0.0.24',
  • l

    loud-electrician-45072

    01/27/2017, 8:31 PM
    looks like the relevant piece
  • l

    loud-electrician-45072

    01/27/2017, 8:32 PM
    one obscure and advanced question that is relevant for me to migration
  • l

    loud-electrician-45072

    01/27/2017, 8:32 PM
    are there recommended workflows for having a vanilla setup.py python codebase depend on a pants repo "live"?
  • l

    loud-electrician-45072

    01/27/2017, 8:33 PM
    e.g., if I had two vanilla setup.py codebases , I would use 
    pip -e
  • w

    witty-crayon-22786

    01/27/2017, 8:34 PM
    not really... only as literal sources.
1...161216131614...2420Latest