On 6/26/10 3:56 AM, John Pinner wrote:
On Jun 25, 11:14 pm, Steven D'Aprano 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 with a totally bogus accusation of "ru
On Jun 25, 11:14 pm, Steven D'Aprano 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 being rude here, and that's you
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 fix
Uhh...
On Fri, Jun 25, 2010 at 2:31 PM, GrayShark 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:
>
> ---
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.
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 yo
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 'string
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 t
On Fri, Jun 25, 2010 at 7: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.
>
Perhaps? Why perhaps? The warning is simply factually wrong-- therefore,
there's no reason in the world
On Fri, 25 Jun 2010 01:29:22 +, Benjamin Peterson wrote:
> GrayShark 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.
Thank
GrayShark 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
On 6/24/2010 1:50 PM, Ixokai wrote:
On Thu, Jun 24, 2010 at 10:39 AM, GrayShark
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 over-enthusiastic
message
On 06/24/2010 07:39 PM, GrayShark wrote:
> On Jun 24, 10:06 am, GrayShark 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 function
On Thu, Jun 24, 2010 at 10:39 AM, GrayShark 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 needed to des
On Jun 24, 10:06 am, GrayShark 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 the constants?
On Thu, Jun 24, 2010 at 10:06 AM, GrayShark 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 t
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
--
http://mail.python.org/mailman/list
17 matches
Mail list logo
