Re: [Pytables-users] 2.3 roadmap (proposal)
Hola Francesc, Il 05/08/2011 08:42, Francesc Alted ha scritto: > 2011/8/4, Antonio Valentino : [CUT] >> * leave out, for the moment, advanced packaging #70 and #71 (unless >> anyone has already the job done). The debian directory sould be >> removed from the master branch IMHO. > > OK. And yes, debian directory should be removed (it is a > responsibility of the debian maintainer only). Francesc some time ago I tried to contact the maintained of the debian package (Wen Heping if I'm not wrong) but without success. Do you know him? Since PyTables version currently in debian is outdated (2.1.2) my idea was to maintain a temporary debian branch (on PyTabes or on my personal area) to update the package an migrate it to dh7 and dh_python2. In this way it should be easier for debian developers to push 2.3 in the main archive when it will be ready. [CUT] >> * perform some testing with numpy 1.6.1 > > Would be great. Well, I performed a quick test (not --heavy) with numpy 1.6.1 on ubuntu 11.04 amd64 and all seems to work. >> * update docs for release > > Yes, specially ANNOUNCE.txt and RELEASE_NOTES.txt.in I remember I've seen somewhere a summary of additional features provided by PyTables Pro but I can't find it anymore. Do you have some pointer? >> * beta release > > Beta? Hmm, the PyTables sources are based on a previous stable > PyTables Pro 2.2.1, and you only made slight changes, so I'd go > directly with 2.3rc1 (but this is up to you). Ok for me, +1 for rc1 >> * full test on all platforms > > Yeah, at least with Windows and Linux (MacOSX is similar enough to > Linux to not have to check it too frequently). Also, the purpose of a > release candidate will allow people to check it before a final > release. Do we also need to test various combination of python version and libraries? python 2.6/2.7 hdf5 1.8.x/1.6.10 (maybe only 1.8) numpy 1.4.x/1.5.x/1.6.x No more testing for numarry and Numeric since they are deprecated. OK, PyTables Pro was already well tested so maybe we don't have to worry too much in this case but it is useful to know for future releases. regards -- Antonio Valentino -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Pytables-users mailing list Pytables-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytables-users
Re: [Pytables-users] Francesc Alted ceasing activities with PyTables + numexpr maintenance
Hi, On Wed, Jun 1, 2011 at 18:41, Francesc Alted wrote: > After more than 8 years since the first public version of PyTables > (October 2002) and almost 4 years since the first release of PyTables > Pro (July 2007), it is time for me to start new challenges in my > career. Sorry for the slow reply, I was busy on other stuff for a while... I'm sorry to hear that. You were doing a amazing job. Thanks a lot for all the effort and time you put into it. > The reason for this change is that I have found a new job [...] I wish you all the best for your new job and hope you enjoyed your first months. > Also, I'm committing myself to maintain the pytables.org web site for > at least one additional year (up to May 2012), and I'd glad to help > transferring it (or part of it) to anyone who wants to become a future > maintainer. I don't have enough time to help here, but I would like to offer my help for one of the satellite projects, namely numexpr. As far as I understand, you were the de facto maintainer for numexpr, so I fear that without you it will go unmaintained... And since I have a vested interest in keeping numexpr alive (at least until PyPy can be used as a replacement), I would like to be added to the list of maintainers for numexpr (preferably along with other people, as the other persons currently having commit rights seem inactive too). Thanks again for everything, -- Gaëtan de Menten -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Pytables-users mailing list Pytables-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytables-users
Re: [Pytables-users] 2.3 roadmap (proposal)
2011/8/5, Antonio Valentino : >> OK. And yes, debian directory should be removed (it is a >> responsibility of the debian maintainer only). > > Francesc some time ago I tried to contact the maintained of the debian > package (Wen Heping if I'm not wrong) but without success. > Do you know him? No, I don't know him. A couple of years ago I decided to not maintain the Debian package anymore (I had switched to another distro), and asked for a new maintainer. I suppose this is when Wen enter into play, but unfortunately we never interchanged a single message. > Since PyTables version currently in debian is outdated (2.1.2) my idea > was to maintain a temporary debian branch (on PyTabes or on my personal > area) to update the package an migrate it to dh7 and dh_python2. > > In this way it should be easier for debian developers to push 2.3 in the > main archive when it will be ready. > Another possibility is to keep the debian directory in the repo, but remove it from the source tarball (i.e. remove debian/ from MANIFEST.in). Wait... I've just check this and the debian directory is not included anymore. I suppose this should be fine, right? > Well, I performed a quick test (not --heavy) with numpy 1.6.1 on ubuntu > 11.04 amd64 and all seems to work. Nice, the NumPy crew usually do a very good job ensuring backwards compatibility :) > I remember I've seen somewhere a summary of additional features provided > by PyTables Pro but I can't find it anymore. > Do you have some pointer? Sure: http://www.pytables.org/moin/PyTablesPro There there are listed mainly three capabilities: OPSI indexes, the improved cache subsystem, and the professional installer. You want to mention only the first two, and OPSI is, by far, the most exciting one :) > Do we also need to test various combination of python version and libraries? > > python 2.6/2.7 > hdf5 1.8.x/1.6.10 (maybe only 1.8) > numpy 1.4.x/1.5.x/1.6.x No, I usually test just for latest releases of everything. In case of backward incompatibilities, users usually complain during the "release candidate" stage. > OK, PyTables Pro was already well tested so maybe we don't have to worry > too much in this case but it is useful to know for future releases. Sure. Luck! -- Francesc Alted -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Pytables-users mailing list Pytables-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytables-users
Re: [Pytables-users] Francesc Alted ceasing activities with PyTables + numexpr maintenance
2011/8/5, Gaetan de Menten : > Hi, > > On Wed, Jun 1, 2011 at 18:41, Francesc Alted wrote: > >> After more than 8 years since the first public version of PyTables >> (October 2002) and almost 4 years since the first release of PyTables >> Pro (July 2007), it is time for me to start new challenges in my >> career. > > Sorry for the slow reply, I was busy on other stuff for a while... I'm > sorry to hear that. You were doing a amazing job. Thanks a lot for all > the effort and time you put into it. Thanks Gaëtan :) > I don't have enough time to help here, but I would like to offer my > help for one of the satellite projects, namely numexpr. As far as I > understand, you were the de facto maintainer for numexpr, so I fear > that without you it will go unmaintained... And since I have a vested > interest in keeping numexpr alive (at least until PyPy can be used as > a replacement), I would like to be added to the list of maintainers > for numexpr (preferably along with other people, as the other persons > currently having commit rights seem inactive too). Sure. I remember you contributing some patches that were not trivial, so I've put you as a new owner of the project. Just remember than with more power, you should be more careful on what you do :) Mind that Mark Wiebe (mwwiebe) had been working with a completely revamped version of numexpr, mainly to adapt to the new iterator introduced in NumPy 1.6 series. His work is in "newiter" branch, and IMO, now that NumPy 1.6 has been out for a few months, I think it is a good time to release it. As the changes Mark done were very significant, I suggested this new version to be labeled 2.0, but it is up to you to decide now! Finally, I'll write Mark and propose him to become a new owner too. This way you could benefit of each other opinions ;) Thanks for wanting to become the next numexpr maintainer and good luck! -- Francesc Alted -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Pytables-users mailing list Pytables-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytables-users
Re: [Pytables-users] 2.3 roadmap (proposal)
Hi Francesc, Il 05/08/2011 17:52, Francesc Alted ha scritto: > 2011/8/5, Antonio Valentino : [CUT] >> Since PyTables version currently in debian is outdated (2.1.2) my idea >> was to maintain a temporary debian branch (on PyTabes or on my personal >> area) to update the package an migrate it to dh7 and dh_python2. >> >> In this way it should be easier for debian developers to push 2.3 in the >> main archive when it will be ready. >> > > Another possibility is to keep the debian directory in the repo, but > remove it from the source tarball (i.e. remove debian/ from > MANIFEST.in). Wait... I've just check this and the debian directory > is not included anymore. I suppose this should be fine, right? oh sorry, I've just pushed the change. I can revert it if you prefer. Anyway my idea was to point the wach file to github so to start packaging from a pure source distribution (no pre-built doc and no cythonized files) an make packaging easier. In this case having a debian directory around is not a good thing. thanks -- Antonio Valentino -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Pytables-users mailing list Pytables-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytables-users
Re: [Pytables-users] 2.3 roadmap (proposal)
2011/8/5, Antonio Valentino : >> Another possibility is to keep the debian directory in the repo, but >> remove it from the source tarball (i.e. remove debian/ from >> MANIFEST.in). Wait... I've just check this and the debian directory >> is not included anymore. I suppose this should be fine, right? > > oh sorry, I've just pushed the change. I can revert it if you prefer. > > Anyway my idea was to point the wach file to github so to start > packaging from a pure source distribution (no pre-built doc and no > cythonized files) an make packaging easier. > In this case having a debian directory around is not a good thing. No, it is fine with me. After all, you are the 'capo' now ;) -- Francesc Alted -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Pytables-users mailing list Pytables-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytables-users
Re: [Pytables-users] 2.3 roadmap (proposal)
Chiming in late On Aug 4, 2011, at 10:17 AM, Antonio Valentino wrote: > Hi list, hi developers, > it seems to me that the PyTables development is a little stalled at the > moment. Certainly no thanks to the summer lull. Thanks for giving us a kick! > I think that it is important to have PyTables 2.3 as soon as possible. > Some job has already been done and new features coming from the PyTables > Pro IMHO justify a new release. > > So my proposal is to: > * merge the pro_liberation branch #1 > * leave out, for the moment, advanced packaging #70 and #71 (unless > anyone has already the job done). The debian directory sould be > removed from the master branch IMHO. > * proceed with deprecations #68 and #76 > * merge all the work already done (#66, #77 TBC, ...) > * perform some testing with numpy 1.6.1 > * update docs for release > * beta release > * full test on all platforms > * final release All sounds fine. I'll certainly test on my Mac 10.6, and can do so in a virtual environment depending on what kind of coverage there is. > I think I have addressed issues #66, #68 and #77 in branches on my > personal fork (https://github.com/avalentino/PyTables). It is only > needed review and merge. You're going faster than I can review, which is great. I've pushed a few minor fixes, but otherwise all looks fine. > I'm going to start working on #76. > > Job on #1 is almost complete. IMHO pro_liberation branch is ready for > merge even if XSL stylesheets still need some cleanup (see #1). > Unfortunately I don't know XSL enough to put my hands in. I can take on stripping out the XSL, but as all comments on that issue have said, it's not a priority. > OK, any feedback is welcome and, most of all, I would appreciate a lot > an OK from someone before starting to merge the various changes. > > > [#1] https://github.com/PyTables/PyTables/issues/1 > [#66] https://github.com/PyTables/PyTables/issues/66 > [#68] https://github.com/PyTables/PyTables/issues/68 > [#70] https://github.com/PyTables/PyTables/issues/70 > [#71] https://github.com/PyTables/PyTables/issues/71 > [#76] https://github.com/PyTables/PyTables/issues/76 Added comment about deprecation warning. > [#77] https://github.com/PyTables/PyTables/issues/77 One other small thing which is mostly noticeable thanks to git's whitespace highlighting is that ^M line endings are creeping in. Finally, I'm going through https://github.com/PyTables/PyTables/wiki/ReleaseProcedure now, but am fumbling a bit with XSL on Mac (https://github.com/PyTables/PyTables/issues/82). Nothing major. > best regards > Antonio Valentino Cheers, ~Josh. P.S. Do we want to rename/close/merge the 2.3b1 milestone? https://github.com/PyTables/PyTables/issues?milestone=1&state=open PGP.sig Description: This is a digitally signed message part -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1___ Pytables-users mailing list Pytables-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytables-users
Re: [Pytables-users] 2.3 roadmap (proposal)
Hello All, On Fri, Aug 5, 2011 at 2:51 PM, Josh Moore wrote: > Chiming in late > Also chiming in late. > > On Aug 4, 2011, at 10:17 AM, Antonio Valentino wrote: > > > Hi list, hi developers, > > it seems to me that the PyTables development is a little stalled at the > > moment. > > Certainly no thanks to the summer lull. Thanks for giving us a kick! > Ditto! > > > I think that it is important to have PyTables 2.3 as soon as possible. > > Some job has already been done and new features coming from the PyTables > > Pro IMHO justify a new release. > > > > So my proposal is to: > > * merge the pro_liberation branch #1 > > * leave out, for the moment, advanced packaging #70 and #71 (unless > > anyone has already the job done). The debian directory sould be > > removed from the master branch IMHO. > > * proceed with deprecations #68 and #76 > > * merge all the work already done (#66, #77 TBC, ...) > > * perform some testing with numpy 1.6.1 > > * update docs for release > > * beta release > > * full test on all platforms > > * final release > > All sounds fine. I'll certainly test on my Mac 10.6, and can do so in a > virtual environment depending on what kind of coverage there is. > I can try to work on the docs this weekend. I have been deep in docs on another project. Sphinx FTW! > > > I think I have addressed issues #66, #68 and #77 in branches on my > > personal fork (https://github.com/avalentino/PyTables). It is only > > needed review and merge. > > You're going faster than I can review, which is great. I've pushed a few > minor fixes, but otherwise all looks fine. > I'll try to look at any edits or pull requests that come in as well. Thanks for giving us a kick Antonio! Be Well Anthony > > > I'm going to start working on #76. > > > > Job on #1 is almost complete. IMHO pro_liberation branch is ready for > > merge even if XSL stylesheets still need some cleanup (see #1). > > Unfortunately I don't know XSL enough to put my hands in. > > I can take on stripping out the XSL, but as all comments on that issue have > said, it's not a priority. > > > OK, any feedback is welcome and, most of all, I would appreciate a lot > > an OK from someone before starting to merge the various changes. > > > > > > [#1] https://github.com/PyTables/PyTables/issues/1 > > [#66] https://github.com/PyTables/PyTables/issues/66 > > [#68] https://github.com/PyTables/PyTables/issues/68 > > [#70] https://github.com/PyTables/PyTables/issues/70 > > [#71] https://github.com/PyTables/PyTables/issues/71 > > [#76] https://github.com/PyTables/PyTables/issues/76 > > Added comment about deprecation warning. > > > [#77] https://github.com/PyTables/PyTables/issues/77 > > One other small thing which is mostly noticeable thanks to git's whitespace > highlighting is that ^M line endings are creeping in. > > Finally, I'm going through > https://github.com/PyTables/PyTables/wiki/ReleaseProcedure now, but am > fumbling a bit with XSL on Mac ( > https://github.com/PyTables/PyTables/issues/82). Nothing major. > > > best regards > > Antonio Valentino > > Cheers, > ~Josh. > > P.S. Do we want to rename/close/merge the 2.3b1 milestone? > https://github.com/PyTables/PyTables/issues?milestone=1&state=open > > -- > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save! > http://p.sf.net/sfu/rim-blackberry-1 > ___ > Pytables-users mailing list > Pytables-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/pytables-users > > -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1___ Pytables-users mailing list Pytables-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytables-users
