[vtk-developers] Uploading Packages to PyPi

Matthew Brett matthew.brett at gmail.com
Fri Sep 22 16:25:54 EDT 2017


Hi,

On Fri, Sep 22, 2017 at 2:52 PM, Matt McCormick
<matt.mccormick at kitware.com> wrote:
> VTK's build is significantly longer than scipy's, but it could be tried :-).

I don't know whether it's possible for travis-ci - but I know for sure
that Appveyor will consider request to extend the build timeout on an
account if you can give a good justification,

Cheers,

Matthew

> On Thu, Sep 21, 2017 at 7:25 PM, Paul Dao <xoviat at gmail.com> wrote:
>> And on second thought, you can also have build phases, where you try to get
>> as far as possible before the timeout and then recommit the build artifacts
>> to the cache. It works quite well with build stages.
>>
>> 2017-09-21 18:12 GMT-05:00 Paul Dao <xoviat at gmail.com>:
>>>
>>> I should mention that scipy already has a travis.yml with the required
>>> commands:
>>>
>>>
>>> https://github.com/scipy/scipy/blob/04759f9d46541f1626232b2a44d16d00a10e530c/.travis.yml#L69
>>>
>>> 2017-09-21 18:11 GMT-05:00 Paul Dao <xoviat at gmail.com>:
>>>>
>>>> The solution to the timing problems on Travis is to use ccache. Then you
>>>> can enable a cron that builds daily. The cron will build the cache over time
>>>> until the build succeeds. For appveyor, it's the same except you need to use
>>>> "clcache," which is significantly more buggy.
>>>>
>>>> 2017-09-21 17:16 GMT-05:00 Matt McCormick <matt.mccormick at kitware.com>:
>>>>>
>>>>> Yes, in the ITKPythonPackage repository, the builds are happening on
>>>>> barebones machines (I will make a note in the documentation to clarify
>>>>> this). For large packages like ITK and VTK, TravisCI times out.
>>>>>
>>>>> On conda-forge, a VTK build with TravisCI was attempted, but it has
>>>>> not succeeded:
>>>>>
>>>>>
>>>>> https://github.com/conda-forge/vtk-feedstock/pull/34#issuecomment-331285697
>>>>>
>>>>> On Thu, Sep 21, 2017 at 5:48 PM, Paul Dao <xoviat at gmail.com> wrote:
>>>>> > Actually, I have no idea what is happening on the ITKPythonPackage
>>>>> > repository. It seems that Travis is only used to lint the build
>>>>> > scripts and
>>>>> > the actual builds are happening somewhere else. That's not how I would
>>>>> > have
>>>>> > approached the problem and it's also not how packages are built at
>>>>> > MacPython.
>>>>> >
>>>>> > 2017-09-21 16:21 GMT-05:00 Paul Dao <xoviat at gmail.com>:
>>>>> >>
>>>>> >> Step number one is to attach appveyor and Travis. Would you mind
>>>>> >> setting
>>>>> >> that up?
>>>>> >>
>>>>> >> On Sep 21, 2017 4:12 PM, "Jean-Christophe Fillion-Robin"
>>>>> >> <jchris.fillionr at kitware.com> wrote:
>>>>> >>>
>>>>> >>> Hi Paul,
>>>>> >>>
>>>>> >>> Thanks for the update.
>>>>> >>>
>>>>> >>> We started to work on infrastructure to build VTK wheels for all
>>>>> >>> platforms.
>>>>> >>>
>>>>> >>> The current repo is https://github.com/jcfr/VTKPythonPackage and the
>>>>> >>> plan
>>>>> >>> is to support "pip install vtk"
>>>>> >>>
>>>>> >>> It will be similar to what we have done for ITK. See [1] and [2]
>>>>> >>>
>>>>> >>> Hth
>>>>> >>> Jc
>>>>> >>>
>>>>> >>> [1] https://github.com/InsightSoftwareConsortium/ITKPythonPackage
>>>>> >>> [2] https://blog.kitware.com/itk-is-on-pypi-pip-install-itk-is-here/
>>>>> >>>
>>>>> >>> On Thu, Sep 21, 2017 at 4:16 PM, David E DeMarle
>>>>> >>> <dave.demarle at kitware.com> wrote:
>>>>> >>>>
>>>>> >>>> That's great, thanks Paul!
>>>>> >>>>
>>>>> >>>>
>>>>> >>>> David E DeMarle
>>>>> >>>> Kitware, Inc.
>>>>> >>>> Principal Engineer
>>>>> >>>> 21 Corporate Drive
>>>>> >>>> Clifton Park, NY 12065-8662
>>>>> >>>> Phone: 518-881-4909
>>>>> >>>>
>>>>> >>>> On Thu, Sep 21, 2017 at 4:13 PM, Paul Dao <xoviat at gmail.com> wrote:
>>>>> >>>>>
>>>>> >>>>> Hello:
>>>>> >>>>>
>>>>> >>>>> There's been some discussion on uploading a "VTK" package to the
>>>>> >>>>> Python
>>>>> >>>>> Package Index. The plan is to set this up at
>>>>> >>>>> https://github.com/MacPython. I
>>>>> >>>>> am not asking for any action on your part but I will grant you
>>>>> >>>>> rights to the
>>>>> >>>>> repository and you can participate in the process if you want
>>>>> >>>>> (it's your
>>>>> >>>>> project after all).
>>>>> >>>>>
>>>>> >>>>> _______________________________________________
>>>>> >>>>> Powered by www.kitware.com
>>>>> >>>>>
>>>>> >>>>> Visit other Kitware open-source projects at
>>>>> >>>>> http://www.kitware.com/opensource/opensource.html
>>>>> >>>>>
>>>>> >>>>> Search the list archives at:
>>>>> >>>>> http://markmail.org/search/?q=vtk-developers
>>>>> >>>>>
>>>>> >>>>> Follow this link to subscribe/unsubscribe:
>>>>> >>>>> http://public.kitware.com/mailman/listinfo/vtk-developers
>>>>> >>>>>
>>>>> >>>>>
>>>>> >>>>
>>>>> >>>
>>>>> >>>
>>>>> >>>
>>>>> >>> --
>>>>> >>> +1 919 869 8849
>>>>> >
>>>>> >
>>>>> >
>>>>> > _______________________________________________
>>>>> > Powered by www.kitware.com
>>>>> >
>>>>> > Visit other Kitware open-source projects at
>>>>> > http://www.kitware.com/opensource/opensource.html
>>>>> >
>>>>> > Search the list archives at:
>>>>> > http://markmail.org/search/?q=vtk-developers
>>>>> >
>>>>> > Follow this link to subscribe/unsubscribe:
>>>>> > http://public.kitware.com/mailman/listinfo/vtk-developers
>>>>> >
>>>>> >
>>>>
>>>>
>>>
>>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Search the list archives at: http://markmail.org/search/?q=vtk-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/vtk-developers
>


More information about the vtk-developers mailing list