On Dec 26, 2014, at 04:38 PM, Aurelien Bompard wrote: >This should be pretty easy, something like the following command should work: >alembic -c src/mailman/config/alembic.cfg revision --autogenerate -m "python3 >port"
I'm having some trouble with this because the system alembic doesn't have access to the mailman source tree, which it needs (you get import errors). I tried to run alembic out of the .tox virtualenv, but that fails because the mailman config system needs to be initialized. Early on in the SA branch, there was an alembic subcommand to the mailman command. I don't think I want that, but I think we need something that calls into alembic programmatically, but with sys.path set up correctly, and the mailman system properly initialized. Maybe a 'withlist' script will do the trick. Anyway, I'll spend some time working on this and follow up here if needed. > >[...] then I'll merge this to trunk and do a 3.0b5 release as a > Python >3-only application. Mailman 3 will not be bilingual so Python 2 > support >will be dropped. > >This means I must now port HyperKitty and Kittystore to Python3 Oh gosh, no! I'm sorry I was imprecise, but I meant only that Mailman 3 *core* would be Python 3. I certainly would never make you guys do all that busy work without consulting you first. So for the record, HyperKitty and Postorious can absolutely port on their own time frame, and that need not at all block a release of the full suite. One of the advantages of accessing the core through the REST API is that it doesn't matter what clients like HyperKitty and Postorious are written in. >verified (I believe it imports the testing framework from mailman.client and >thus must be ported too). We've always said that mailman.client should be bilingual. It should be usable in either Python 2 or Python 3 scripts. I took a quick look at the current mailman.client trunk, and yes its test suite will have to be fixed, but I will take it upon myself to do that. If that's the only hangup, then I'm not worried. >And I thought the 3.0 release was almost there. I must say this is rather >discouraging. Hopefully the above provides some clarity and dis-disencouragement ;). Cheers, -Barry _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
