On 16 juin 13:27, John Fawcett wrote:
> actually, I think you should drop it from the reports. it isn't useful in
> static reports, really it only helps in the context of an IDE where you can
> do something with the offset information. so maybe you should just send it
> to add_message so custom rep
actually, I think you should drop it from the reports. it isn't useful in
static reports, really it only helps in the context of an IDE where you can
do something with the offset information. so maybe you should just send it
to add_message so custom reporters like mine can use it, but people needn'
On 16 juin 12:35, John Fawcett wrote:
> I think I have it working - I submitted two patches: one to add the column
> offset to astng nodes, and then another for pylint to report on it.
>
> In the pylint patch, I left the parseable format unchanged, because I
> thought there may be compatibility is
Hi,
I think I have it working - I submitted two patches: one to add the column
offset to astng nodes, and then another for pylint to report on it.
In the pylint patch, I left the parseable format unchanged, because I
thought there may be compatibility issues for users of parseable. selfishly,
i j
hehe, i was looking around in the pylint project, not the astng project
(blush). i'm on the right track now
thanks,
fawce
On Thu, Jun 16, 2011 at 10:38 AM, Sylvain Thénault <
sylvain.thena...@logilab.fr> wrote:
> On 16 juin 09:51, John Fawcett wrote:
> > Hi,
>
> re
>
> > Thanks for the speedy rep
On 16 juin 09:51, John Fawcett wrote:
> Hi,
re
> Thanks for the speedy reply. I'd love to write the patch!
great,
> I actually read most of the code yesterday, and I have to admit that I
> couldn't find any references to _ast -- could you give me a nudge in the
> right direction?
start by lo
Hi,
Thanks for the speedy reply. I'd love to write the patch!
I actually read most of the code yesterday, and I have to admit that I
couldn't find any references to _ast -- could you give me a nudge in the
right direction?
thanks,
fawce
On Thu, Jun 16, 2011 at 7:40 AM, Sylvain Thénault <
sylvai
On 16 juin 13:31, Amaury Forgeot d'Arc wrote:
> Hi,
>
> 2011/6/16 Sylvain Thénault :
> > ASTNG is using the python ast representation as basis. A don't think
> > there is such column offset information there. Either I'm wrong, then
> > we could easily have a pylint reporter that display this infor
Hi,
2011/6/16 Sylvain Thénault :
> ASTNG is using the python ast representation as basis. A don't think
> there is such column offset information there. Either I'm wrong, then
> we could easily have a pylint reporter that display this information,
> or I'm right, and this should be added as a feat
On 15 juin 10:23, John Fawcett wrote:
> Hi,
Hi,
> I was wondering if you have considered adding column offsets to your message
> information? I've been working on a really simple IDE that uses pylint to
> find problems and then highlight the code (red-squiggly like spellcheck). It
> would be real
Hi,
I was wondering if you have considered adding column offsets to your message
information? I've been working on a really simple IDE that uses pylint to
find problems and then highlight the code (red-squiggly like spellcheck). It
would be really useful to receive more information about the locat
On 20/09/10 22:10, Emile Anclin wrote:
hello,
On Monday 20 September 2010 13:21:38 Michael wrote:
I can't find the submit ticket button for pylint, so I am hoping this
gets noticed here.
I use PyLint on a code base that used a lots of Unicode. This means
the line count check is always get
hello,
On Monday 20 September 2010 13:21:38 Michael wrote:
> I can't find the submit ticket button for pylint, so I am hoping this
> gets noticed here.
>
> I use PyLint on a code base that used a lots of Unicode. This means
> the line count check is always getting messed up, as pylint does not
>
I can't find the submit ticket button for pylint, so I am hoping this
gets noticed here.
I use PyLint on a code base that used a lots of Unicode. This means the
line count check is always getting messed up, as pylint does not
understand unicode files correctly. Is it possible to add this usi
14 matches
Mail list logo
