Re: [Mailman-Developers] Merging users
Actually merging two existing users is indeed a tricky thing because users link to so many other interesting bits and pieces. Two separate users have two separate memberships, linked addresses, preferred addresses, and yes, preferences. There are also the created_on, display_name, and (the mostly unused) password attributes. How deep does merging users go? Abhilash's fix is good but I need to actually merge users, so here's how I would do it. https://gitlab.com/mailman/mailman/merge_requests/32 The change sits on top of Abhilash's, so there's no conflict. I don't think I'm missing anything as far as users are concerned, but please have a look :-) Cheers, Aurélien ___ 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
Re: [Mailman-Developers] Why is postorius using python2?
On Aug 04, 2015, at 11:01 PM, f...@florianfuchs.com wrote: So the question would be: Go bilingual or py3 only? Bilingual was what we had agreed on before, for the reasons Barry stated above. But mabye this argument becomes less valid as time passes and Python 3 adoption is on the rise. Plus: If someone would want to integrate a py3-only Postorius/HK into an existing site *and* this site is not py3 compatible, it would still be possible to run both on the same server, using another VirtualHost/subdomain or similar. I'm thinking aloud here, not *necessarily* advocating to only support Python 3 soon. But I wonder if there are really that many people who would be negatively affected by it. And, as stated above, for those who are, there's always a way around it. Mabye it's worth giving it another thought. OTOH, supporting both py2+3 is probably not that much more work. But it doesn't make our code much nicer and is not exactly a strong satement in favor of Python 3 adoption. I can't really weigh in much because I don't know how typical Django users would want to set up their Mailman site. Would they expect to run all their Django apps in a single instance, and thus a single interpreter version? And if so, would they be blocked from installing and running Postorius and HyperKitty if they were Python 3 only? What do other Django apps typically do? I *can* say that you'll almost certainly prefer coding in Python 3! Also, that 3.4 makes a very excellent base version to support. And finally, in general it's not that difficult to support both versions, though I don't know how easy it is to support both versions in a Django app. Official bilingual support would have to at least be tested in both versions. 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
Re: [Mailman-Developers] Why is postorius using python2?
Am 2015-08-04 20:55, schrieb Barry Warsaw: Others have provided good answers, but I'll add one comment about what I consider to be policy regarding Python version support. Feedback welcome of course! On Aug 03, 2015, at 02:34 PM, Simon Hanna wrote: I was astonished to find out that postorius still uses python2 although mailman made the switch to python3. The Core can be Python 3-only because the official way to script it is through the REST API, which of course is not only Python-version independent, but actually only depends on you being able to speak HTTP+JSON. Of course mailman.client is the official Python binding to the REST API and that should remain bilingual (Python 2 3 compatible) for some time. Note that this did break HyperKitty at the time because it was importing from the 'mailman' package. That's of course since been fixed. I think both HyperKitty and Postorius should officially support Python 3, but remain Python 2 compatible. The reason for this is that they're both Django applications, so if they have to co-habitate with other Python 2-only Django apps, they'll need to also run in Python 2. They should be Python 3 compatible, because, well, Python 3 is much awesomer! We don't have any direct Python2-only dependencies in Postorius any more since we made the switch from django-social-auth to python-social-auth/django-browserid in April. I'm pretty sure the same is true for HyperKitty (Aurélien...?). So I guess there's no reason why we shouldn't start supporting Python 3 as well. So the question would be: Go bilingual or py3 only? Bilingual was what we had agreed on before, for the reasons Barry stated above. But mabye this argument becomes less valid as time passes and Python 3 adoption is on the rise. Plus: If someone would want to integrate a py3-only Postorius/HK into an existing site *and* this site is not py3 compatible, it would still be possible to run both on the same server, using another VirtualHost/subdomain or similar. I'm thinking aloud here, not *necessarily* advocating to only support Python 3 soon. But I wonder if there are really that many people who would be negatively affected by it. And, as stated above, for those who are, there's always a way around it. Mabye it's worth giving it another thought. OTOH, supporting both py2+3 is probably not that much more work. But it doesn't make our code much nicer and is not exactly a strong satement in favor of Python 3 adoption. Cheers, Florian ___ 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
Re: [Mailman-Developers] Mailman 3 Error some questions
Am 2015-07-30 07:54, schrieb Krinetzki, Stephan: Hello, 3. Is it possible to get Shibboleth ( https://www.shibboleth.net https://www.shibboleth.net) working with mailman3? I don't have any personal experience with shibboleth integration, but there seem to be some solutions out there to use it in combination with Django. There's even a ticket on github regarding adding it to python-social-auth[1] (which we use in mailman-bundler). The important point for us: If someone signs on using shibboleth, are we guaranteed to have access to their email address? Florian [1] https://github.com/omab/python-social-auth/issues/388 ___ 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
Re: [Mailman-Developers] Why is postorius using python2?
Others have provided good answers, but I'll add one comment about what I consider to be policy regarding Python version support. Feedback welcome of course! On Aug 03, 2015, at 02:34 PM, Simon Hanna wrote: I was astonished to find out that postorius still uses python2 although mailman made the switch to python3. The Core can be Python 3-only because the official way to script it is through the REST API, which of course is not only Python-version independent, but actually only depends on you being able to speak HTTP+JSON. Of course mailman.client is the official Python binding to the REST API and that should remain bilingual (Python 2 3 compatible) for some time. Note that this did break HyperKitty at the time because it was importing from the 'mailman' package. That's of course since been fixed. I think both HyperKitty and Postorius should officially support Python 3, but remain Python 2 compatible. The reason for this is that they're both Django applications, so if they have to co-habitate with other Python 2-only Django apps, they'll need to also run in Python 2. They should be Python 3 compatible, because, well, Python 3 is much awesomer! Those ports will happen, but I don't know whether they've been milestoned yet. Cheers, -Barry pgpKPugN1Ub9e.pgp Description: OpenPGP digital signature ___ 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
Re: [Mailman-Developers] Why is postorius using python2?
f...@florianfuchs.com writes: We don't have any direct Python2-only dependencies in Postorius any more since we made the switch from django-social-auth to python-social-auth/django-browserid in April. I'm pretty sure the same is true for HyperKitty (Aurélien...?). So I guess there's no reason why we shouldn't start supporting Python 3 as well. That would be very helpful. So the question would be: Go bilingual or py3 only? Bilingual was what we had agreed on before, for the reasons Barry stated above. But mabye this argument becomes less valid as time passes Less in terms of numbers. But remember than anybody who really is stuck on Python 2 for some reason is 100% stuck. The argument for bilingual is no less valid than ever for that system. Sure, it's usually possible to run a separate instance, but that would mean that they can't integrate Postorius or HyperKitty with the rest of their site. OTOH, supporting both py2+3 is probably not that much more work. But it doesn't make our code much nicer and is not exactly a strong satement in favor of Python 3 adoption. It seems to me that punishing folks who have a dependency on Python 2 is hardly a strong statement in favor of Python 3, while providing Python 3 support is the strongest statement in favor of Python 3 that a project can make. Since I'm unlikely to do much, if any, of the work, I have no objection to obsoleting Python 2 support if you think it's too much work. But I hope we can bear some ugliness for a while if that's the main objection to bilingual support. Regards, Steve ___ 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
