2010-09-29 19:37:12 Julien Jehannet napisał(a):
> > * Sylvain Thénault [29-sep-2010 18:11]:
> > On 29 septembre 18:08, Julien Jehannet wrote:
> > > > * Andrey Rahmatullin [29-sep-2010 10:03]:
> > > > On Wed, Sep 29, 2010 at 02:18:18AM +0200, Arfrever Frehtes Taifersar
> > > > Arahesis wrote:
> >
2010-09-29 08:32:45 Sylvain Thénault napisał(a):
> > > We can just do :
> > >
> > > -self.__exc_info = self._exc_info
> > > +self.__exc_info = sys.exc_info
> > >
> > > since _exc_info is doing nothing else.
> >
> > Could the changes required for compatibility with Python
On Wed, Sep 29, 2010 at 06:08:29PM +0200, Julien Jehannet wrote:
> > > test_knownValues_is_standard_module_4 always fails.
> > test_knownValues_is_standard_module_4 properly shows that
> > logilab.common.modutils.is_standard_module is broken on some x86_64
> > systems where Python distribution is i
> * Sylvain Thénault [29-sep-2010 18:11]:
> On 29 septembre 18:08, Julien Jehannet wrote:
> > > * Andrey Rahmatullin [29-sep-2010 10:03]:
> > > On Wed, Sep 29, 2010 at 02:18:18AM +0200, Arfrever Frehtes Taifersar
> > > Arahesis wrote:
> > > > test_knownValues_is_standard_module_4 always fails.
>
> * Arfrever Frehtes Taifersar Arahesis [29-sep-2010
> 09:16]:
> logilab-common 0.52.0 fails some tests:
> (...)
>
> test_knownValues_is_standard_module_4 always fails.
(see another thread about it)
>
> test_capture_core fails after disabling test_both_capture with similar error
> to this er
On 29 septembre 18:08, Julien Jehannet wrote:
> > * Andrey Rahmatullin [29-sep-2010 10:03]:
> > On Wed, Sep 29, 2010 at 02:18:18AM +0200, Arfrever Frehtes Taifersar
> > Arahesis wrote:
> > > test_knownValues_is_standard_module_4 always fails.
> > test_knownValues_is_standard_module_4 properly sho
> * Andrey Rahmatullin [29-sep-2010 10:03]:
> On Wed, Sep 29, 2010 at 02:18:18AM +0200, Arfrever Frehtes Taifersar Arahesis
> wrote:
> > test_knownValues_is_standard_module_4 always fails.
> test_knownValues_is_standard_module_4 properly shows that
> logilab.common.modutils.is_standard_module is
On 28/09/10 19:33, Sylvain Thénault wrote:
At the time of porting pylint to py3k, this will much probably be the latest
set of versions to use to get pylint working with python 2.3 code. And maybe,
unless you people think it would be a shame, also for python 2.4, so we
can drop support for the ol
Hi Terrence,
On Tuesday 28 September 2010 22:33:14 Terrence Cole wrote:
> This is all, of course, a long way off still. What I'm working on right
> now is basic linting for python3 so that I can add a lint step to our
> hudson server and start to get some graphs up.
Just in case, and for the rec
On Wed, Sep 29, 2010 at 02:18:18AM +0200, Arfrever Frehtes Taifersar Arahesis
wrote:
> test_knownValues_is_standard_module_4 always fails.
test_knownValues_is_standard_module_4 properly shows that
logilab.common.modutils.is_standard_module is broken on some x86_64
systems where Python distribution
On Tuesday 28 September 2010 23:49:27 Edward K. Ream wrote:
> On Tue, Sep 28, 2010 at 3:46 AM, Emile Anclin
wrote:
> > Usually, pylint / astng will have to parse most of the Python
> > Standard Library (which is around 20 Mb) on any bigger project (such
> > as a framework); plus the site-packages
logilab-common 0.52.0 fails some tests:
unittest_modutils.is_standard_module_tc.test_knownValues_is_standard_module_4
unittest_testlib.OutErrCaptureTC.test_both_capture
unittest_testlib.OutErrCaptureTC.test_capture_core
unittest_fileutils.ProtectedFileTC.test_mode_change
unittest_fileutil
On Tue, Sep 28, 2010 at 3:46 AM, Emile Anclin wrote:
> Usually, pylint / astng will have to parse most of the Python Standard
> Library (which is around 20 Mb) on any bigger project (such as a
> framework); plus the site-packages on my current workstation are around
> 100 Mb. (rough estimations b
13 matches
Mail list logo
