Re: [Mailman-Developers] Mailman 3.0 fresh install - problems from python interpreter

2012-11-14 Thread Chris Cargile
In case others might be interested and appreciating a bit of help recalling what the search feature's development status is at the moment, this email spawned from a thread in June 2012, here: http://www.mail-archive.com/mailman-developers@python.org/msg12921.html On Mon, Nov 12, 2012 at 2:36

Re: [Mailman-Developers] Mailman 3.0 fresh install - problems from python interpreter

2012-06-11 Thread Richard Wackerbarth
Jessy, Yes, there are plans (and activity) related to the presentation of list archives within the django framework. In fact, Aamir, one of our GSoC interns, is working on that very subject as his project for the summer. In keeping with the django philosophy of combining many special purpose

Re: [Mailman-Developers] Mailman 3.0 fresh install - problems from python interpreter

2012-06-11 Thread Jessy Kate Schingler
good to know, look forward to seeing it! On Mon, Jun 11, 2012 at 6:21 AM, Richard Wackerbarth rich...@nfsnet.orgwrote: Jessy, Yes, there are plans (and activity) related to the presentation of list archives within the django framework. In fact, Aamir, one of our GSoC interns, is working on

Re: [Mailman-Developers] Mailman 3.0 fresh install - problems from python interpreter

2012-06-10 Thread Jessy Kate Schingler
hello again, and thanks for the response. What I've always thought is that overview, architectural, and other useful higher level documentation should go in src/mailman/docs. Still using the reST format, but they needn't necessarily be doctests. So I think an overview page about interacting

Re: [Mailman-Developers] Mailman 3.0 fresh install - problems from python interpreter

2012-06-10 Thread Jessy Kate Schingler
hi richard, Good end-user documentation always seems to be something that gets shorted by the developers intimately related to the implementation aspect of the code. And, even when they make the effort, I'm not sure that they are the most qualified to write that kind of documentation. Someone

Re: [Mailman-Developers] Mailman 3.0 fresh install - problems from python interpreter

2012-06-07 Thread Jessy Kate Schingler
thanks mark and barry. i've been traveling so apologies for the delayed reply... using `bin/mailman shell` command does indeed work flawlessly, thank you! should the docs be updated perhaps? something either under getting started with GNU Maiman or even a specific page on interacting with

Re: [Mailman-Developers] Mailman 3.0 fresh install - problems from python interpreter

2012-06-07 Thread Barry Warsaw
On Jun 07, 2012, at 09:31 AM, Jessy Kate Schingler wrote: should the docs be updated perhaps? something either under getting started with GNU Maiman or even a specific page on interacting with mailman through the python interpreter? i am happy to add something or contribute to that; i think it

Re: [Mailman-Developers] Mailman 3.0 fresh install - problems from python interpreter

2012-06-07 Thread Richard Wackerbarth
Jessy, I'm sure that any additions to the documentation will be welcomed. Good end-user documentation always seems to be something that gets shorted by the developers intimately related to the implementation aspect of the code. And, even when they make the effort, I'm not sure that they are

Re: [Mailman-Developers] Mailman 3.0 fresh install - problems from python interpreter

2012-06-05 Thread Barry Warsaw
Hi Jessy, You're doing everything right, but there's one conceptual step that you're missing, and which isn't evident from the docs. As Mark says, `mailman shell` is the best way to get a Python interactive interpreter shell to play with the internal Mailman API. Why is this better than just

[Mailman-Developers] Mailman 3.0 fresh install - problems from python interpreter

2012-06-04 Thread Jessy Kate Schingler
hello! i am setting up mailman 3.0 on ubuntu 12.04. but getting errors when i try to work with mailman through the python interpreter. i hope this is the correct list to post to. here are the steps i took: - installed mailman 3.0.0.b1 in a fresh virtualenv - install is happy, all tests pass