[Mailman-Developers] Re: Development setup confusion
Do note that these two commands, from the Vagrantfile, work if you run them in the venv only (not sure why) pip3 install --upgrade pip pip3 install -U setuptools Just noticed now because I've nuked my local folder and tried with a clean git clone again On Sun, Feb 21, 2021 at 1:52 AM Marius Ghita wrote: > > > On Sun, Feb 21, 2021 at 1:28 AM Mark Sapiro wrote: > >> On 2/20/21 3:07 PM, Marius Ghita wrote: >> > I think a setup step might be missing from the developer's docs >> > https://docs.mailman3.org/en/latest/devsetup.html >> > >> > If I go through the venv setup and when I call mailman info, the >> following >> > error shows up (missing dependency). >> > >> > ... >> > File "/home/_/Workspace/personal/mailman/src/mailman/__init__.py", >> line >> > 38, in >> > from mailman.core.i18n import initialize >> > File "/home/_/Workspace/personal/mailman/src/mailman/core/i18n.py", >> line >> > 22, in >> > from flufl.i18n import PackageStrategy, registry >> > ModuleNotFoundError: No module named 'flufl.i18n' >> >> >> How did you install Mailman core in your venv? Mailman core's setup >> includes flufl.i18n>=2.0 in it's requirements. >> >> > I have a folder ~/Workspace/personal where I ran: > > $ python3 -m venv venv3 > $ source ./venv3/bin/activate > $ cd mailman > $ python setup.py develop > > > For a second there I considered that the issue might have been that the > dependency expects and older Python version. I have 3.9 on my desktop, so I > spun up a Vagrant box which has python3.6 with the same issue. > > Vagrantfile to reproduce the issue > https://gist.github.com/mhitza/4dbec7d0efc6a94e658b5dd085e411ef > > ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Re: Development setup confusion
On Sun, Feb 21, 2021 at 1:28 AM Mark Sapiro wrote: > On 2/20/21 3:07 PM, Marius Ghita wrote: > > I think a setup step might be missing from the developer's docs > > https://docs.mailman3.org/en/latest/devsetup.html > > > > If I go through the venv setup and when I call mailman info, the > following > > error shows up (missing dependency). > > > > ... > > File "/home/_/Workspace/personal/mailman/src/mailman/__init__.py", line > > 38, in > > from mailman.core.i18n import initialize > > File "/home/_/Workspace/personal/mailman/src/mailman/core/i18n.py", > line > > 22, in > > from flufl.i18n import PackageStrategy, registry > > ModuleNotFoundError: No module named 'flufl.i18n' > > > How did you install Mailman core in your venv? Mailman core's setup > includes flufl.i18n>=2.0 in it's requirements. > > I have a folder ~/Workspace/personal where I ran: $ python3 -m venv venv3 $ source ./venv3/bin/activate $ cd mailman $ python setup.py develop For a second there I considered that the issue might have been that the dependency expects and older Python version. I have 3.9 on my desktop, so I spun up a Vagrant box which has python3.6 with the same issue. Vagrantfile to reproduce the issue https://gist.github.com/mhitza/4dbec7d0efc6a94e658b5dd085e411ef ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Development setup confusion
I think a setup step might be missing from the developer's docs https://docs.mailman3.org/en/latest/devsetup.html If I go through the venv setup and when I call mailman info, the following error shows up (missing dependency). ... File "/home/_/Workspace/personal/mailman/src/mailman/__init__.py", line 38, in from mailman.core.i18n import initialize File "/home/_/Workspace/personal/mailman/src/mailman/core/i18n.py", line 22, in from flufl.i18n import PackageStrategy, registry ModuleNotFoundError: No module named 'flufl.i18n' However, when I run just run tox, the .tox/qa/bin/mailman info command works without any issues. ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Re: Feature request, selective participatory threads
"Used to be" seems to be the operative sentence, unfortunately. I have browsed various sources around the "Systers organization" keyword and what public repositories there might be, but no luck finding anything that includes the dynamic sublists implementation. I have found the document that describes the implementation, on (the old wiki?) wiki.list.org https://archive.vn/NLyl2 Based on that document I assumed the following rpm to contain the changes, but no luck. https://ftp.osuosl.org/pub/osl/systers-mailman/ (unpacked with "rpm2cpio ../mailman-systers-2.1.12-2012.12.27.el6.src.rpm| cpio -idmv") I think the document in itself can be a starting point for the implementation. If you have a contact email to someone that's part of the Systers group, it might be worth reaching out in order to upstream this feature. But I also have no issue with just diving into the codebase and building the functionality along the lines of the aforementioned document. On Sun, Feb 14, 2021 at 6:00 AM Stephen J. Turnbull < turnb...@sk.tsukuba.ac.jp> wrote: > Marius Ghita writes: > > > To that end, I would propose a new feature for Mailman to allow the > > user to be more selective with the emails it receives. > > This sounds a lot like the "dynamic sublist" feature that has been > implemented in the Systers' fork of Mailman. (They use Mailman as a > front-end for a lot of Systers-specific process, so upstreaming the > dynamic sublist part is not trivial.) > > Their repository used to be at g...@github.com:systers/mailman3.git if > you want to take a look. (Note: I haven't been involved there for > several years. Their Mailman apparently was mature enough for them, > and their GSoC goals moved toward mobile app development, so they > didn't push to get GSoC students and we drifted apart). > > ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Feature request, selective participatory threads
Greetings. I'm generally a Mailman user through all the open-source projects that require a user to join a mailing list before contributing to a project. As a user that occasionally contributes patches/PRs to random repositories, my mailing list subscriptions are short-lived because I always get more emails than I need. To that end, I would propose a new feature for Mailman to allow the user to be more selective with the emails it receives. The following scenarios are those that would work best for me. 1. If I send an email to a mailing list, any follow-up emails to that thread are sent to my inbox as well. 2. If a user sends an email through the mailing list that CCs/BCCs me I get all the follow-up emails in that thread as well. 3. Maybe -- and this one is more of an idea than something that I would actually use -- a generated email in the mail archive web view for each thread, to which I could send an email and be subscribed to any follow-up emails to that thread. For me, this feature would make emails more manageable, and have them behave like subscriptions to individual issues on issue trackers. My Python is rusty, at best, but I would be happy to help implement this feature in Mailman. ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
