On Wed, Sep 29, 2010 at 2:49 AM, Emile Anclin wrote:
>> Because the types of the objects in the library can be assumed to be
>> immutable,
>
> Can we assume that ?
> how would we deal with modifying modules in our cached data base ?
How about assuming it for a start :-)
Edward
_
estimations based on 'du' and considering that the size
> of .pyc files are similar to the .py)
>
> Given that, I am afraid we will have ~ 400 Mb for the only astng dumbs.
> So that seems to be the wrong road...
>
> Edward K Ream, did you have other ideas in mind to hand
fires
only once, when all needed data are available. The new-lint prototype
appears to handle these kinds of details properly.
Edward
--
E
Thanks.
Edward
------
Edward K. Ream email: edream...@gmail.com
Leo: http://webpages.charter.net/edreamleo/front.html
--
___
Python-Projects mailing list
Python-Projects@lists.l
able design.
Edward
----------
Edward K. Ream email: edream...@gmail.com
Leo: http://webpages.charter.net/
eamleo.blogspot.com/2009/12/converting-leo-to-python-3k-surprises.html
The short summary: given reasonable unit tests, porting is straightforward.
Edward
----------
Edward K. Ream email: edream...@gmail.com
Leo: http://webpag
energy and effectiveness. This group marks a new
phase in my life's work."
Edward
----------
Edward K. Ream email: edream...@gmail.com
Leo: http://webpages.charter.net/
ld modify this branch.
Edward
----------
Edward K. Ream email: edream...@gmail.com
Leo: http://webpages.charter.net/edreamleo/front.html
--
_
On Tue, Feb 16, 2010 at 8:04 AM, Emile Anclin wrote:
> I am since november working on a branch called 'rebuild' which indeed
> creates our own nodes so that monkey patching should eventually
> disappear.
I see a link to this branch at
http://www.logilab.org/cgi-bin/hgwebdir.cgi/logilab/astng/bra
On Tue, Feb 16, 2010 at 8:04 AM, Emile Anclin wrote:
> I started refactoring astng this summer;
> first I reduced the monkey patching (september 2009).
> I am since november working on a branch called 'rebuild' which indeed
> creates our own nodes so that monkey patching should eventually
> disap
On Tue, Feb 16, 2010 at 7:33 AM, Sylvain Thénault
wrote:
> Regarding the work you would like to do with pylint / astng, the best would
> probably to start discuss about them on this mailing list.
Good idea. I'll discuss what is mysterious to me, and ask whether
particular ideas make sense.
>
--
--
Edward K. Ream email: edream...@gmail.com
Leo: http://webpages.charter.net/edreamleo/front.html
ing
life--compilers. Many thanks, Sylvain, for this great work.
P.P.S. Is there a theory of operations document for pylint? I'm at
the point now in my study where it would be most useful.
EKR
----------
Edward K. Ream
computer programming.
----------
Edward K. Ream email: edream...@gmail.com
Leo: http://webpages.charter.net/edreamleo/front.html
--
__
d54d7
As you can see, the design has already been modified as it confronted
reality :-)
P.P.S. I suppose the best imaginable outcome would be to fold
improvements into the main pylint, that is assuming real improvements
do appear.
EKR
------
15 matches
Mail list logo