On Sep 8, 2010, at 6:46 AM, SourceForge.net wrote:
> I've just pushed a new build fixing that, so, if you update to the latest it
> should work again (it's still version 1.6.2 as the only change was in the
> build
> process).
Hey Fabio,
In the future, for changes like this, would you mind adding at least some small
indication to the version number that something has changed? Like, 1.6.2.1 or
1.6.2a or something like that? Having been confused by the
different-bits-but-same-version problem in the past, I know that this can come
back to bite you :).
Thanks,
-glyph
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Pydev-users mailing list
Pydev-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pydev-users