Get repoze.sendmail into the buildout

[Paul Everitt]

This is a very simple task whose only purpose is to get ChrisR familiar with the KARL3 codebase, directory layout, etc.

After this task is closed, developer sandboxes should see:

- A buildout that fetches repoze.sendmail and puts it in eggs. (Whether this is done in buildout.cfg or src/osi/setup.py dependencies is up to ChrisR and ChrisM.)

- The correct console scripts appearing in bin that drain a queue, though they won't work as there won't yet be a queue.

- All tests still pass. (cd src/karl; ./test runs all the tests)

Completing this task does not mean editing any of the code in KARL3. That's the next task.

[Paul Everitt (paul-agendaless)]

This task isn't yet about changing KARL code, it's more about learning your way around the codebase. My guess is, this is under 1 hour to complete.

[Paul Everitt (paul-agendaless)]

Moving out of M2. ChrisR will let me know on Monday how much availability he has next week.

[Chris Rossi (chris-archimedeanco)]

It would appear that this is going to require a release of repoze.sendmail so setuptools can grab it. Not sure if I can do that. Will need to discuss with Chris M, probably.

[Chris McDonough (chrism-plope)]

No, I'll need to update the index. If the trunk or a branch or tag is in shape for that, let me know and I'll do that.

[Chris Rossi (chris-archimedeanco)]

I'll tag a 1.0 release. I haven't really messed with a lot of the metadata
in setup.py. It's still ZPL. And I haven't touched existing comment
headers. If you want it to be a particular way for repoze let me know.

Chris

On Tue, Feb 24, 2009 at 9:40 AM, Chris McDonough <email address hidden> wrote:

> No, I'll need to update the index. If the trunk or a branch or tag is
> in shape for that, let me know and I'll do that.
>
> --
> Get repoze.sendmail into the buildout
> https://bugs.launchpad.net/bugs/331030
> You received this bug notification because you are a member of KARL3
> Developers, which is the registrant for KARL3.
>
> Status in Porting KARL to a new architecture: In Progress
>
> Bug description:
> This is a very simple task whose only purpose is to get ChrisR familiar
> with the KARL3 codebase, directory layout, etc.
>
> After this task is closed, developer sandboxes should see:
>
> - A buildout that fetches repoze.sendmail and puts it in eggs. (Whether
> this is done in buildout.cfg or src/osi/setup.py dependencies is up to
> ChrisR and ChrisM.)
>
> - The correct console scripts appearing in bin that drain a queue, though
> they won't work as there won't yet be a queue.
>
> - All tests still pass. (cd src/karl; ./test runs all the tests)
>
> Completing this task does not mean editing any of the code in KARL3.
> That's the next task.
>

[Chris Rossi (chris-archimedeanco)]

Tagged!

[Chris McDonough (chrism-plope)]

r.sendmail 1.0 is now in the "lemonade" (OSI) index and thus can be added to the
OSI buildout at will.

- C

Chris Rossi wrote:
> I'll tag a 1.0 release. I haven't really messed with a lot of the metadata
> in setup.py. It's still ZPL. And I haven't touched existing comment
> headers. If you want it to be a particular way for repoze let me know.
>
> Chris
>
>
> On Tue, Feb 24, 2009 at 9:40 AM, Chris McDonough <email address hidden> wrote:
>
>> No, I'll need to update the index. If the trunk or a branch or tag is
>> in shape for that, let me know and I'll do that.
>>
>> --
>> Get repoze.sendmail into the buildout
>> https://bugs.launchpad.net/bugs/331030
>> You received this bug notification because you are a member of KARL3
>> Developers, which is the registrant for KARL3.
>>
>> Status in Porting KARL to a new architecture: In Progress
>>
>> Bug description:
>> This is a very simple task whose only purpose is to get ChrisR familiar
>> with the KARL3 codebase, directory layout, etc.
>>
>> After this task is closed, developer sandboxes should see:
>>
>> - A buildout that fetches repoze.sendmail and puts it in eggs. (Whether
>> this is done in buildout.cfg or src/osi/setup.py dependencies is up to
>> ChrisR and ChrisM.)
>>
>> - The correct console scripts appearing in bin that drain a queue, though
>> they won't work as there won't yet be a queue.
>>
>> - All tests still pass. (cd src/karl; ./test runs all the tests)
>>
>> Completing this task does not mean editing any of the code in KARL3.
>> That's the next task.
>>
>

[Chris Rossi (chris-archimedeanco)]

Queue processor will appear in 'bin/qp' after buildout. Invoke with no arguments to see usage.

[Chris Rossi (chris-archimedeanco)]

Potentially we might like to have qp parse paster ini files to cut down on number of arguments on command line. Let me know if that is desirable.

[Paul Everitt (paul-agendaless)]

If you can get this in under an hour, then yes, desirable.

--Paul

On Feb 24, 2009, at 11:14 AM, Chris Rossi wrote:

> Potentially we might like to have qp parse paster ini files to cut
> down
> on number of arguments on command line. Let me know if that is
> desirable.