Re: deprecated string module issue

2010-06-26 Thread John Pinner
On Jun 25, 11:14 pm, Steven D'Aprano st...@remove-this- cybersource.com.au wrote: On Fri, 25 Jun 2010 16:31:17 -0500, GrayShark wrote: Why the rudness Terry Jan Reedy? Get up on the wrong side of the bed? Or worse luck, no one on the other side to create a wrong side? I see only one person

Re: deprecated string module issue

2010-06-26 Thread Stephen Hansen
On 6/26/10 3:56 AM, John Pinner wrote: On Jun 25, 11:14 pm, Steven D'Apranost...@remove-this- cybersource.com.au wrote: Terry made the very reasonable observation that you would serve the community, and thank us, by posting a bug report to pylint, rather than just ignoring it, and you respond

Re: deprecated string module issue

2010-06-25 Thread GrayShark
On Fri, 25 Jun 2010 01:29:22 +, Benjamin Peterson wrote: GrayShark howe.steven at gmail.com writes: Sorry, I meant from string import lowercase, uppercase Technically, you should use ascii_lowercase and ascii_uppercase, though I don't know if that's the cause of pylint's complaints.

Re: deprecated string module issue

2010-06-25 Thread Stephen Hansen
On Fri, Jun 25, 2010 at 7:02 AM, GrayShark howe.ste...@gmail.com wrote: Thanks for the suggestion. I gave it a quick try. Same 'warning'. No, using the string module is the issue. Perhaps I'll just ignore it. Perhaps? Why perhaps? The warning is simply factually wrong-- therefore, there's no

Re: deprecated string module issue

2010-06-25 Thread Terry Reedy
On 6/25/2010 10:02 AM, GrayShark wrote: Thanks for the suggestion. I gave it a quick try. Same 'warning'. No, using the string module is the issue. Perhaps I'll just ignore it. And what about the next naive user of pylint? Submitting a bug report to the author of pylint would take much less

Re: deprecated string module issue

2010-06-25 Thread GrayShark
Why the rudness Terry Jan Reedy? Get up on the wrong side of the bed? Or worse luck, no one on the other side to create a wrong side? As to your comment about Logilab's pylint. I'v seen a ticket similar to this from three months back. I assume they're not fixing it because if you review

Re: deprecated string module issue

2010-06-25 Thread Steven D'Aprano
On Fri, 25 Jun 2010 16:31:17 -0500, GrayShark wrote: Why the rudness Terry Jan Reedy? Get up on the wrong side of the bed? Or worse luck, no one on the other side to create a wrong side? I see only one person being rude here, and that's you. Terry made the very reasonable observation that you

Re: deprecated string module issue

2010-06-25 Thread Mark Lawrence
First up please don't top post. Second (although I'm sure Terry Reedy can speak for himself) said TJR has put more into Python than I've drunk pints of beer, and that's saying something, so you accusing him of being rude to me stinks!!! Please apologise or get off of this ng/ml. Disgusted.

Re: deprecated string module issue

2010-06-25 Thread Stephen Hansen
Uhh... On Fri, Jun 25, 2010 at 2:31 PM, GrayShark howe.ste...@gmail.com wrote: As to your comment about Logilab's pylint. I'v seen a ticket similar to this from three months back. I assume they're not fixing it because if you review 'string' via pydoc you'd read this:

Re: deprecated string module issue

2010-06-25 Thread Robert Kern
On 6/25/10 4:31 PM, GrayShark wrote: Why the rudness Terry Jan Reedy? Get up on the wrong side of the bed? Or worse luck, no one on the other side to create a wrong side? As to your comment about Logilab's pylint. I'v seen a ticket similar to this from three months back. I assume they're not

deprecated string module issue

2010-06-24 Thread GrayShark
In my code I have: from string import lower, upper When I use pylint on the program I get just one warning: Uses of a deprecated module 'string'. Iv'e noted that many if not all string functions are now in _builtin_. Where are the constants? Thanks Steven --

Re: deprecated string module issue

2010-06-24 Thread Stephen Hansen
On Thu, Jun 24, 2010 at 10:06 AM, GrayShark howe.ste...@gmail.com wrote: In my code I have: from string import lower, upper When I use pylint on the program I get just one warning: Uses of a deprecated module 'string'. Iv'e noted that many if not all string functions are now in _builtin_.

Re: deprecated string module issue

2010-06-24 Thread GrayShark
On Jun 24, 10:06 am, GrayShark howe.ste...@gmail.com wrote: In my code I have: from string import lower, upper When I use pylint on the program I get just one warning: Uses of a deprecated module 'string'. Iv'e noted that many if not all string functions are now in _builtin_. Where are

Re: deprecated string module issue

2010-06-24 Thread Ixokai
On Thu, Jun 24, 2010 at 10:39 AM, GrayShark howe.ste...@gmail.com wrote: Sorry, I meant from string import lowercase, uppercase As I was joining these two, I just changed the import to 'letters' So if the constants are not deprecated, why is the module? Is some other state then deprecated

Re: deprecated string module issue

2010-06-24 Thread Thomas Jollans
On 06/24/2010 07:39 PM, GrayShark wrote: On Jun 24, 10:06 am, GrayShark howe.ste...@gmail.com wrote: In my code I have: from string import lower, upper When I use pylint on the program I get just one warning: Uses of a deprecated module 'string'. Iv'e noted that many if not all string

Re: deprecated string module issue

2010-06-24 Thread Terry Reedy
On 6/24/2010 1:50 PM, Ixokai wrote: On Thu, Jun 24, 2010 at 10:39 AM, GrayShark howe.ste...@gmail.com So if the constants are not deprecated, why is the module? Is some Again: the string module is not deprecated. It simply is not. GrayShark, pylint has a bug. Tell the author that its

Re: deprecated string module issue

2010-06-24 Thread Benjamin Peterson
GrayShark howe.steven at gmail.com writes: Sorry, I meant from string import lowercase, uppercase Technically, you should use ascii_lowercase and ascii_uppercase, though I don't know if that's the cause of pylint's complaints. -- http://mail.python.org/mailman/listinfo/python-list