oh boy... ;-)
was it painful?
Thanks!
On Sun, 22 Apr 2012, Tiziano Zito wrote:
Also since github PR accepted as merges, it would be best first to just
cherry pick mine on top of yours to avoid merges and then do rebase -i
done :)
--
was it painful?
not really, just a bit of vi gymnastics ;)
ciao,
tiziano
___
Pkg-ExpPsy-PyMVPA mailing list
Pkg-ExpPsy-PyMVPA@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-exppsy-pymvpa
may be some skype/shared screen
sprintee next week over remaining issues etc?
yes, if michael is around we could meet in berlin or magdeburg and
have get you on skype.
There is a bulk of changes in some guys feature branches and if we do not
merge now, later it might not be as easy ;) I
cool -- you can consider me now a contributor to this little project
;-) I have sent a pull request against your branch with few
changes, please review.
I merged your pull request, thank you :)
Also it might be nice to markup those commits which deal with python3
compatibility as PY3 (e.g.
On Sat, 21 Apr 2012, Tiziano Zito wrote:
I merged your pull request, thank you :)
glad to help ;)
that's a good idea. I fear my git foo stops at git rebase -i, to
do what you want we would need a git filter-branch, right?
I would prefer to rewrite history, if you give me a couple of hints
hi all,
with my today's efforts I got down to 13 errors and 15 failures out
of 284 tests, so it's getting better :)
on the same branch the same set of unittests passes without errors
or failures with python 2.7, so I assume I did not break anything
important.
I attach here the error logs in
thank you Tiziano!
I have started to glance over the changes -- lots of nice ones -- thanks again,
and we should finalize/merge asap - may be some skype/shared screen
sprintee next week over remaining issues etc?
There is a bulk of changes in some guys feature branches and if we do not
merge
if you push your work somewhere (I don't see your clone at
https://github.com/PyMVPA/PyMVPA/network) we will add it to daily
testing
I don't know why you don't see it, but I do have a fork on github:
https://github.com/otizonaizit/PyMVPA/
but please, slow down, this is very much work in
On Thu, 19 Apr 2012, Tiziano Zito wrote:
a first report of my efforts for a py3 version of PyMVPA. Put aside
a couple of incompatibilities in the swig wrappers and the usage of
some deprecated functions and modules that were easily fixable, my
PyMVPA port now runs succesfully 67 out of 127
My guess is that it is still related to how that AttributesCollector
injects those additional attributes into the freshly constructed
classes. I hope above clues would be of help
it helped indeed ;)
ciao,
tiziano
___
Pkg-ExpPsy-PyMVPA mailing
Hey,
On Wed, Apr 18, 2012 at 01:22:54PM +0200, Tiziano Zito wrote:
dear PyVMPA devs,
as I accumulated a bit of experience in migrating projects from py2 to py3,
I thought I could try to help doing this migration for PyMVPA too.
I know it may seem premature, but now that numpy and
MVPA_TESTS_QUICK=yes MVPA_TESTS_LOWMEM=yes make unittest-nonlabile
[...]
Let us know if that helps for a start.
yep, it works fine this way, thanks. it even finds more unit tests (326) ;)
ciao,
tiziano
___
Pkg-ExpPsy-PyMVPA mailing list
cool and thanks Tiziano,
I am branching from master on github as of now
(f0d900f1a1c715379dd716e3d4c87876b321ba9e).
if you push your work somewhere (I don't see your clone at
https://github.com/PyMVPA/PyMVPA/network) we will add it to daily
testing
- I got three failures and one error: are
On Wed, 18 Apr 2012, josef.p...@gmail.com wrote:
- how can I disable the matplotlib windows that pop up shortly
during testing? as there is still no python3-matplotlib I would
need to disable it for the moment
python3-matplotlib is available, I'm not getting any failures with
14 matches
Mail list logo
