It wasn't.
On 3 June 2010 13:05, Wichert Akkerman wrote:
> On 6/3/10 11:27 , Malthe Borch wrote:
>>
>> We should try and consolidate all these different bug trackers. It's a
>> mess. Too bad we don't have the proper top-level name for this. I
>> don't know that I agree with the name "chameleon-te
Fergus said:
> Gustavo: If you submit a r.who / plugin sprint, I'll sign up! We have a few
> apps running behind r.who so I have a bit of a vested interest in seeing
> it stay up to date.
Sounds like a plan. I'll try to do it today.
--
Gustavo Narea .
| Tech blog: =Gustavo/(+blog)/tech ~ About
On 3 Jun 2010, at 12:06, Charlie Clark wrote:
But I do like the idea of a general WSGI get together.
+1
Gustavo: If you submit a r.who / plugin sprint, I'll sign up! We have
a few apps running behind r.who so I have a bit of a vested interest
in seeing it stay up to date.
__
Am 03.06.2010, 13:13 Uhr, schrieb Gustavo Narea :
>> But I do like the idea of a general WSGI get together.
> We should probably propose it on Web-SIG mailing list then.
Sure. Like I said, I won't be sticking around for any sprints in
Birmingham (got to see the family and stuff). I am going to
Charlie said:
> But I do like the idea of a general WSGI get together.
We should probably propose it on Web-SIG mailing list then.
--
Gustavo Narea .
| Tech blog: =Gustavo/(+blog)/tech ~ About me: =Gustavo/about |
___
Repoze-dev mailing list
Repoze-de
Am 28.05.2010, 16:01 Uhr, schrieb Fergus Doyle
:
> Hi,
> Is anyone planning any Repoze EuroPython sprints?
While I will be giving an introductory talk on BFG on Wednesday afternoon
(looks like it's been scheduled to suit my offer of free beer afterwards)
I won't be around for any sprints. F
Hello,
I'm pleased to announce that a new release of the repoze.who LDAP plugin is
available:
http://code.gustavonarea.net/repoze.who.plugins.ldap/
The following features have been implemented by Lorenzo Catucci of the
University of Rome Tor Vergata:
- Changed the license to the Repoze license.
On 6/3/10 11:27 , Malthe Borch wrote:
> We should try and consolidate all these different bug trackers. It's a
> mess. Too bad we don't have the proper top-level name for this. I
> don't know that I agree with the name "chameleon-template-engine".
Hm, wasn't it you who created that tracker? Odd!
Malthe Borch wrote:
> On 3 June 2010 12:37, Chris Withers wrote:
>> How do you run the tests?
>
> python setup.py nosetests
Ah, okay, didn't know about that. That works fine.
It was the following that caused the problems:
python setup.py test
I'll use your suggestion from now on, no need for
On 6/3/10 11:37 , Chris Withers wrote:
> Malthe Borch wrote:
>> Really that's odd;
>
> How do you run the tests?
Same as all (non-Zope) python packages: python setup.py test
> Hmm, it occurs to me that even if the [test] extra_requires was there, I
> don't know how to feed that into:
>
> python s
On 3 June 2010 12:37, Chris Withers wrote:
> How do you run the tests?
python setup.py nosetests
> Hmm, it occurs to me that even if the [test] extra_requires was there, I
> don't know how to feed that into:
>
> python setup.py develop
>
> Any ideas?
Not really right now; let me think it over.
Malthe Borch wrote:
> Really that's odd;
How do you run the tests?
> we can definitely add a [test] on next release; or
> please go ahead and commit it if you can.
Hmm, it occurs to me that even if the [test] extra_requires was there, I
don't know how to feed that into:
python setup.py develop
We should try and consolidate all these different bug trackers. It's a
mess. Too bad we don't have the proper top-level name for this. I
don't know that I agree with the name "chameleon-template-engine".
\malthe
On 3 June 2010 00:49, Wichert Akkerman wrote:
> On 2010-6-2 23:48, Chris Withers wro
Really that's odd; we can definitely add a [test] on next release; or
please go ahead and commit it if you can.
Thanks,
On 3 June 2010 09:50, Chris Withers wrote:
> Malthe Borch wrote:
>>
>> This has to do with lxml; it currently worksforme, but I don't know
>> why. Try Stephan's static build an
14 matches
Mail list logo
