[Python-Dev] python3k vs _ast
hello everybody, migrating Pylint to python3.x, we encounter a little problem : in the tree generated by _ast, if we consider a args node (representing an argument of a function), the lineno (and the col_offset) information disappeared from those nodes. Is there a particular reason for that ? In python2.x, the args nodes were just Name nodes, and as for now we keep them as AssName nodes in astng/pylint and would like to know where it was defined. thx for any information -- Emile Anclin emile.anc...@logilab.fr http://www.logilab.fr/ http://www.logilab.org/ Informatique scientifique et gestion de connaissances ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] python3k vs _ast
Seems to be rather a usage question, not a development question (python-dev is about *developing* python, not *using* it). On Wed, Nov 17, 2010 at 01:48:06PM +0100, Emile Anclin wrote: hello everybody, migrating Pylint to python3.x, we encounter a little problem : in the tree generated by _ast, if we consider a args node (representing an argument of a function), the lineno (and the col_offset) information disappeared from those nodes. Is there a particular reason for that ? In python2.x, the args nodes were just Name nodes, and as for now we keep them as AssName nodes in astng/pylint and would like to know where it was defined. thx for any information -- Emile Anclin emile.anc...@logilab.fr http://www.logilab.fr/ http://www.logilab.org/ Informatique scientifique et gestion de connaissances Oleg. -- Oleg Broytmanhttp://phd.pp.ru/p...@phd.pp.ru Programmers don't die, they just GOSUB without RETURN. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] python3k vs _ast
2010/11/17 Oleg Broytman p...@phd.pp.ru: Seems to be rather a usage question, not a development question (python-dev is about *developing* python, not *using* it). Well, technically I think it's a feature request. On Wed, Nov 17, 2010 at 01:48:06PM +0100, Emile Anclin wrote: hello everybody, migrating Pylint to python3.x, we encounter a little problem : in the tree generated by _ast, if we consider a args node (representing an argument of a function), the lineno (and the col_offset) information disappeared from those nodes. Is there a particular reason for that ? In python2.x, the args nodes were just Name nodes, and as for now we keep them as AssName nodes in astng/pylint and would like to know where it was defined. I wouldn't object to adding them back if you want to file a bug report. -- Regards, Benjamin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] python3k vs _ast
On Wednesday 17 November 2010 14:36:37 Benjamin Peterson wrote: I wouldn't object to adding them back if you want to file a bug report. Ok, thank you for quick reply. here is the issue : http://bugs.python.org/issue10445 -- Emile Anclin emile.anc...@logilab.fr http://www.logilab.fr/ http://www.logilab.org/ Informatique scientifique et gestion de connaissances ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] python3k vs _ast
On Wed, 17 Nov 2010 07:36:37 -0600, Benjamin Peterson benja...@python.org wrote: 2010/11/17 Oleg Broytman p...@phd.pp.ru: Seems to be rather a usage question, not a development question (python-dev is about *developing* python, not *using* it). Well, technically I think it's a feature request. On Wed, Nov 17, 2010 at 01:48:06PM +0100, Emile Anclin wrote: hello everybody, migrating Pylint to python3.x, we encounter a little problem : in the tree generated by _ast, if we consider a args node (representing an argument of a function), the lineno (and the col_offset) information disappeared from those nodes. Is there a particular reason for that ? In python2.x, the args nodes were just Name nodes, and as for now we keep them as AssName nodes in astng/pylint and would like to know where it was defined. I wouldn't object to adding them back if you want to file a bug report. It also seems to me that it was a perfectly appropriate question for this list. The question was why did you developers drop this (obscure) feature that we depend on in Python3? I don't think that question would make sense on python-list. Granted, there's a fuzzy line there, but pylint is really development infrastructure :) The python-porting list would have been a good alternate choice. -- R. David Murray www.bitdance.com ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] python3k vs _ast
On Wed, Nov 17, 2010 at 09:19:35AM -0500, R. David Murray wrote: On Wed, 17 Nov 2010 07:36:37 -0600, Benjamin Peterson benja...@python.org wrote: 2010/11/17 Oleg Broytman p...@phd.pp.ru: Seems to be rather a usage question, not a development question (python-dev is about *developing* python, not *using* it). Well, technically I think it's a feature request. On Wed, Nov 17, 2010 at 01:48:06PM +0100, Emile Anclin wrote: hello everybody, migrating Pylint to python3.x, we encounter a little problem : in the tree generated by _ast, if we consider a args node (representing an argument of a function), the lineno (and the col_offset) information disappeared from those nodes. Is there a particular reason for that ? In python2.x, the args nodes were just Name nodes, and as for now we keep them as AssName nodes in astng/pylint and would like to know where it was defined. I wouldn't object to adding them back if you want to file a bug report. It also seems to me that it was a perfectly appropriate question for this list. The question was why did you developers drop this (obscure) feature that we depend on in Python3? The problem for me is the wording. A question like why did you developers drop a feature? is certainly a development question, while like to know where it was defined seems more like a usage question. I apologize for misunderstanding. I don't think that question would make sense on python-list. Granted, there's a fuzzy line there, but pylint is really development infrastructure :) The python-porting list would have been a good alternate choice. -- R. David Murray www.bitdance.com Oleg. -- Oleg Broytmanhttp://phd.pp.ru/p...@phd.pp.ru Programmers don't die, they just GOSUB without RETURN. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
