Am 27.12.2014 um 05:18 schrieb Barry Warsaw:
> I tend to agree that a good design for any archiver is to be able to accept
> messages over an IPC channel. A site may for example want to run the core on
> one system and HK on another system (e.g. separate VMs perhaps). This would
> only really b
Barry Warsaw writes:
> Remember too that in MM3, messages only get fed to the registered
> IArchiver interfaces by a separate archive runner. So they aren't
> a bottleneck for delivery to the user, but on heavily trafficked
> sites, they can potential consume a lot of resources if the
> arch
Barry Warsaw writes:
> No more! See my other follow up. And there's no restriction on
> values. Sometimes generic is easier than specific (shouldn't that
> be a Zen of Python? :).
Uh-oh. Looks like somebody is using EggNog programming style! Or are
you just high on life? ;-)
___
On Dec 27, 2014, at 12:42 PM, Stephen J. Turnbull wrote:
>Remember, Mailman core is going to be distributing Internet mail.
>Except in the case where 100.00% of the users are on one host, that's
>going to be the bottleneck on message processing. Archiving simply
>does not need to be fast. The ar
On Dec 27, 2014, at 12:48 PM, Stephen J. Turnbull wrote:
>Let's please take some care to think about this. ISTM this is like
>the Nth time we've bumped into "you need to be core to access config
>data".
No more! See my other follow up. And there's no restriction on values.
Sometimes generic is
On Dec 26, 2014, at 11:02 PM, Aurelien Bompard wrote:
>> But there could be! I took a very quick look at HK (but not KittyStore)
>> and it doesn't look like you need much. What if I added a REST API to
>> access the core's system configuration settings?
>
>That would work.
It turned out to be a
Barry Warsaw writes:
> But there could be! I took a very quick look at HK (but not
> KittyStore) and it doesn't look like you need much. What if I
> added a REST API to access the core's system configuration
> settings? They would be read-only, and I would only start with the
> minimum of
Aurelien Bompard writes:
> Barry writes:
> > 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.
> I'm not exclusively using the REST API though. I'm importing a
> couple interfaces, m
On Dec 26, 2014, at 11:02 PM, Aurelien Bompard wrote:
>> But there could be! I took a very quick look at HK (but not KittyStore)
>> and it doesn't look like you need much. What if I added a REST API to
>> access the core's system configuration settings?
>
>That would work.
Cool, let me see what
> But there could be! I took a very quick look at HK (but not KittyStore)
> and
> it doesn't look like you need much. What if I added a REST API to access
> the
> core's system configuration settings?
>
That would work.
> Yep, I missed that. Is it possible to feed HK messages out-of-process?
On Dec 26, 2014, at 10:32 PM, Aurelien Bompard wrote:
>Right, I'm having issues too with the config file not being initalized.
>I'll have a closer look.
Awesome, thanks.
>I'm not exclusively using the REST API though. I'm importing a couple
>interfaces, mostly the archiver interface. I'm also us
On Dec 27, 2014, at 08:21 AM, Andrew Stuart wrote:
>If it is released to version 1.0 with support for Python 2 then it will need
>to support Python 2 for the forseeable future. It’ll be deployed all over the
>place with Python 2 - when would the Python 2 be removed ever after 1.0?
>David Murray ha
> 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.
>
Right, I'm
If it is released to version 1.0 with support for Python 2 then it will need to
support Python 2 for the forseeable future. It’ll be deployed all over the
place with Python 2 - when would the Python 2 be removed ever after 1.0? David
Murray has made substantial changes to email in Py3 - supporti
On Dec 27, 2014, at 08:26 AM, Andrew Stuart wrote:
>Is there anything I can do to help with these? If there’s a task list maybe I
>can work out what I could do.
Hi Andrew, if you're interested in helping port Postorious and HyperKitty,
I'll defer to Aurelien and Florian.
Cheers,
-Barry
_
Is there anything I can do to help with these? If there’s a task list maybe I
can work out what I could do.
>>This means I must now port HyperKitty and Kittystore to Python3, check that
>>we don't use Py2-only libraries, etc.
>>And mailman.client must be ported too, since it does import stuff fro
On Dec 26, 2014, at 08:48 PM, Geoff Shang wrote:
>On Fri, 26 Dec 2014, Pierre-Yves Chibon wrote:
>
>> This also means that mailman 3 will pretty much only not work on
>> server-oriented distro (except probably Debian that likely ships a python 3
>> version, although not being involved in Debian, I
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
acce
On Fri, 26 Dec 2014, Pierre-Yves Chibon wrote:
This also means that mailman 3 will pretty much only not work on server-oriented
distro (except probably Debian that likely ships a python 3 version, although
not being involved in Debian, I do not know for sure).
Debian Wheezy(aka Stable) ships P
On Fri, Dec 26, 2014 at 04:38:08PM +0100, Aurelien Bompard wrote:
> [...] 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.
> >
>
> Wow. I am very surprised.
> So we went from "Python3
> One of my top priorities has been to port Mailman 3 (core) to Python 3.
> This
> work is now complete, and ready to be merged into trunk. No doubt bugs
> still
> lurk, but at least the entire test suite is passing.
Congrats !
* A few database columns have changed from LargeBinary to Unicode.
21 matches
Mail list logo
