Seems ok.
Barry
On Sep 16, 2010, at 6:20 PM, Lisandro Dalcin wrote:
> On 16 September 2010 20:09, Barry Smith wrote:
>>>
>>> How could I know? If any of my codes works in Apple, I would say it is
>>> just for accident :-). Anyway, I expect to workaround any issue.
>>
>> How shall I tes
On 16 September 2010 20:09, Barry Smith wrote:
>>
>> How could I know? If any of my codes works in Apple, I would say it is
>> just for accident :-). Anyway, I expect to workaround any issue.
>
> ?How shall I test it? Remember I need line by line instructions :-)
>
Give me some time to push my ne
On 16 September 2010 19:43, Aron Ahmadia wrote:
> Lisandro,
> I think this is going to depend on what your release cycle looks like over
> the next year in comparison with the PETSc team.
PETSc 3.1 was released March 25, petsc4py-1.1 was released April 6.
Is that too much delay?.
>?If the two t
On 16 September 2010 19:53, Barry Smith wrote:
>
> On Sep 16, 2010, at 5:18 PM, Lisandro Dalcin wrote:
>
>> I've managed to backport setup.py to release-3.1. It does not require
>> any change to BuildSystem or install.py, as I'm simply using
>> os.system() to spawn configure, make and install. Mat
I've managed to backport setup.py to release-3.1. It does not require
any change to BuildSystem or install.py, as I'm simply using
os.system() to spawn configure, make and install. Matt agreed that we
could add setup.py to release-3.1 (as it would not break anything),
and then get the beast working
ext part --
An HTML attachment was scrubbed...
URL:
<http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100916/5069b17f/attachment.html>
On Sep 16, 2010, at 6:06 PM, Lisandro Dalcin wrote:
> On 16 September 2010 19:53, Barry Smith wrote:
>>
>> On Sep 16, 2010, at 5:18 PM, Lisandro Dalcin wrote:
>>
>>> I've managed to backport setup.py to release-3.1. It does not require
>>> any change to BuildSystem or install.py, as I'm simply
On Sep 16, 2010, at 5:18 PM, Lisandro Dalcin wrote:
> I've managed to backport setup.py to release-3.1. It does not require
> any change to BuildSystem or install.py, as I'm simply using
> os.system() to spawn configure, make and install. Matt agreed that we
> could add setup.py to release-3.1 (a
...
URL:
<http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100916/30820f8f/attachment.html>
