[petsc-dev] including PETSc4py (and Tao4py) inside PETSc repository

[Matthew Knepley]

On Tue, Sep 22, 2015 at 3:39 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:

>
>    Lisandro,
>
>     Now that everyone is using git and knows branches well can we move
> PETSc4py inside the PETSc repository as was done a couple of years ago with
> BuildSystem. Now when changes/additions are made to PETSc there is a slow
> inefficient, often forgotten manual process of bringing them over to
> petsc4py. If we put them all in one repository the updates happen quickly
> and far more efficiently, as would testing. We'll also get the ability to
> do bi-section.
>
>    I realize you want a PETSc4py release to be compatible with previous
> versions of PETSc; this property could still remain and we could easily
> have a tool that "pulls out" the petsc4py release material from the petsc
> repository.
>
>    I think once we make this change we'll wonder why we didn't do it log
> ago; just as when we changed BuildSystem.  Thoughts?
>

I agree with this. The biggest thing to work on (for me) is to make it
easier and less complex to add things, like classes,
to petsc4py. Right now we need to change 7 different places to add a class.

   Matt


>    Thanks
>
>     Barry
>
>


-- 
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20150922/c9f09818/attachment.html>