[issue12326] Linux 3: code should avoid using sys.platform == 'linux2'

[Boštjan Mejak]

Boštjan Mejak  added the comment:

I have a better idea... Why don't we change the "linux2" string into just 
"linux". That way we will never run into this kind of issue, even in the future 
when Linux kernel version 4 is going to exist. Any thoughts on this?

--
nosy: +Retro

___
Python tracker 
<http://bugs.python.org/issue12326>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12277] Missing comma in os.walk docs

[Boštjan Mejak]

Boštjan Mejak  added the comment:

Yes, Eric, please fix this already. :)

--

___
Python tracker 
<http://bugs.python.org/issue12277>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12277] Missing comma in os.walk docs

[Boštjan Mejak]

Changes by Boštjan Mejak :


--
status: closed -> open
versions: +Python 2.6 -Python 2.7, Python 3.2, Python 3.3

___
Python tracker 
<http://bugs.python.org/issue12277>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12277] Missing comma in os.walk docs

[Boštjan Mejak]

Boštjan Mejak  added the comment:

http://docs.python.org/release/2.6.7/library/os.html?highlight=os.walk#os.walk

Please fix Python 2.6 branch of docs as well. Thanks.

--

___
Python tracker 
<http://bugs.python.org/issue12277>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10562] Change 'j' for imaginary unit into an 'i'

[Boštjan Mejak]

Boštjan Mejak  added the comment:

What's up with that now? Any interests in changing the imaginary unit from "j" 
to "i" ?

--

___
Python tracker 
<http://bugs.python.org/issue10562>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10621] >>> 1 + 2j --> (1 + 2j) and not (1+2j)

[Boštjan Mejak]

Changes by Boštjan Mejak :


--
resolution: wont fix -> remind
status: closed -> open
versions: +Python 3.3 -Python 2.7, Python 3.1, Python 3.2

___
Python tracker 
<http://bugs.python.org/issue10621>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10621] >>> 1 + 2j --> (1 + 2j) and not (1+2j)

[Boštjan Mejak]

Changes by Boštjan Mejak :


--
versions: +Python 2.6, Python 2.7, Python 3.1, Python 3.2 -Python 3.3

___
Python tracker 
<http://bugs.python.org/issue10621>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10621] >>> 1 + 2j --> (1 + 2j) and not (1+2j)

[Boštjan Mejak]

Changes by Boštjan Mejak :


--
versions: +Python 3.3, Python 3.4

___
Python tracker 
<http://bugs.python.org/issue10621>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10562] Change 'j' for imaginary unit into an 'i'

[Boštjan Mejak]

Boštjan Mejak  added the comment:

Come on, let's do this.

--
resolution: wont fix -> remind
status: closed -> open
versions: +Python 3.3 -Python 3.2

___
Python tracker 
<http://bugs.python.org/issue10562>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12277] Missing comma in os.walk docs

[Boštjan Mejak]

Boštjan Mejak  added the comment:

That is simply idiotic. Your way of fixing things is idiotic. When you
clearly see the missing comma and you fix it everywhere else but 2.6
because "2.6 only receives security fixes" as if adding a comma to the
documentation would create a big security hole. That's an act of an idiot.
I am sorry, but that is how I see it.

--

___
Python tracker 
<http://bugs.python.org/issue12277>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10562] Change 'j' for imaginary unit into an 'i'

[Boštjan Mejak]

Boštjan Mejak  added the comment:

It's stupid that the imaginary unit in Python is denoted by a "j" just for 
ambiguity reasons that "i" can be mistaken with a "1" or an "l". It's true that 
"1" and "l" can look the same in some fonts, but that is *certainly not true* 
for the small letter "i".

Just fix the "j" into an "i" already.

--
resolution: wont fix -> remind
status: closed -> open

___
Python tracker 
<http://bugs.python.org/issue10562>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10562] Change 'j' for imaginary unit into an 'i'

[Boštjan Mejak]

Boštjan Mejak  added the comment:

Please fix this in Python 3.3 and don't forget to fix the complex() 
function/method as well.

--

___
Python tracker 
<http://bugs.python.org/issue10562>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10562] Change 'j' for imaginary unit into an 'i'

[Boštjan Mejak]

Changes by Boštjan Mejak :


--
resolution: wont fix -> remind
status: closed -> open

___
Python tracker 
<http://bugs.python.org/issue10562>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10562] Change 'j' for imaginary unit into an 'i'

[Boštjan Mejak]

Changes by Boštjan Mejak :


--
nosy: +gvanrossum

___
Python tracker 
<http://bugs.python.org/issue10562>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10621] >>> 1 + 2j --> (1 + 2j) and not (1+2j)

[Boštjan Mejak]

Boštjan Mejak  added the comment:

Make the output of a complex expression include spaces around the operator. So, 
for example, (1+2j) should be outputted as (1 + 2j). Make this happen in Python 
3.3.

--
nosy: +gvanrossum
resolution: wont fix -> remind
status: closed -> open

___
Python tracker 
<http://bugs.python.org/issue10621>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue13695] "type specific" to "type-specific"

[Boštjan Mejak]

New submission from Boštjan Mejak :

Please visit the following link and fix the below text:

http://docs.python.org/library/unittest.html#unittest.TestCase.assertEqual

Changed in version 2.7: Added the automatic calling of >>>type-specific<<< 
equality function.

Just add the hyphen. Thanks.

--
assignee: docs@python
components: Documentation
messages: 150451
nosy: Retro, docs@python
priority: normal
severity: normal
status: open
title: "type specific" to "type-specific"
versions: Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4

___
Python tracker 
<http://bugs.python.org/issue13695>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue13695] "type specific" to "type-specific"

[Boštjan Mejak]

Boštjan Mejak  added the comment:

Also

http://guide.python-distribute.org/quickstart.html#lay-out-your-project

needs to have the first sentence fixed: "python" to "Python"


and

http://docs.python.org/library/functools.html#functools.cmp_to_key

needs to have the word "Py3.x" fixed to "Python 3" (note: not to "Python 3.x" 
because functools.reduce() function also has the word "Python 3", so be 
consistent)

--
nosy: +georg.brandl

___
Python tracker 
<http://bugs.python.org/issue13695>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12277] Missing comma in os.walk docs

[Boštjan Mejak]

New submission from Boštjan Mejak :

http://docs.python.org/release/2.6.6/library/os.html?highlight=os.walk#os.walk

Click the above link and note the 5th paragraph which goes "By default errors 
from the listdir() call are ignored."

Please fix it to "By default, errors from the listdir() call are ignored."

So add a comma after "By default," Thanks.

--
assignee: docs@python
components: Documentation
messages: 137795
nosy: Retro, docs@python
priority: normal
severity: normal
status: open
title: Missing comma in os.walk docs
versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4

___
Python tracker 
<http://bugs.python.org/issue12277>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10073] calendar.isleap() not checking parameter type

[Boštjan Mejak]

Boštjan Mejak  added the comment:

Let me fix this function a little bit...

def isleap(year):
"""Return True for leap years, False for non-leap years."""
if year == 0:
raise ValueError('year 0 does not exist')
return (year % 4 == 0) and (year % 100 != 0) or (year % 400 == 0)

This function, however, does not mind if you give it a negative number. But I 
think we can leave this option to mean B.C. (Before Christ), so 
calendar.isleap(-240) would mean 240 B.C., which was a leap year.

About the  if year == 0  check... Well, read Wikipedia's article  
http://en.wikipedia.org/wiki/0_(year)  which clearly states that "Year zero 
does not exist in the widely used Gregorian calendar or in its predecessor, the 
Julian calendar."  So we raise a ValueError if this value is used in the 
calendar.isleap() function.

I have uploaded a patch that fixes this function. Please apply it to the trunk 
and also to the maintenance brances.

--
keywords: +patch
Added file: http://bugs.python.org/file19255/calendar-isleap.patch

___
Python tracker 
<http://bugs.python.org/issue10073>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10135] Format specifier 'n' not working

[Boštjan Mejak]

New submission from Boštjan Mejak :

Have your default locale set to 'Slovenian' which uses a comma for the decimal 
symbol, like 2.76 is written as 2,76. Observe that the format specifier 'n' 
does not work for the default 'Slovenian' locale setting.

Then try running this in the Python interpreter:
'{number:.3n}'.format(number=2.76)

You get this:
>>> '{number:.3n}'.format(number=2.76)
'2.76'

Excepted the is the return value '2,76'. Please fix this bug.

--
components: Interpreter Core
messages: 119003
nosy: Retro
priority: normal
severity: normal
status: open
title: Format specifier 'n' not working
type: behavior
versions: 3rd party, Python 2.5, Python 2.6, Python 2.7, Python 3.1, Python 
3.2, Python 3.3

___
Python tracker 
<http://bugs.python.org/issue10135>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10135] Format specifier 'n' not working

[Boštjan Mejak]

Boštjan Mejak  added the comment:

{'mon_decimal_point': '', 'int_frac_digits': 127, 'p_sep_by_space': 127,
'frac_digits': 127, 'thousands_sep': '', 'n_sign_posn': 127,
'decimal_point': '.', 'int_curr_symbol': '', 'n_cs_precedes': 127,
'p_sign_posn': 127, 'mon_thousands_sep': '', 'negative_sign': '',
'currency_symbol': '', 'n_sep_by_space': 127, 'mon_grouping': [],
'p_cs_precedes': 127, 'positive_sign': '', 'grouping': []}

'2.760'

And the output of locale.format() in this case should be
'2,760'

On Mon, Oct 18, 2010 at 2:00 PM, Eric Smith  wrote:

>
> Eric Smith  added the comment:
>
> Oops, I meant "locale.format('%.3f', 2.76)", although of course the number
> shouldn't matter.
>
> --
>
> ___
> Python tracker 
> 
> ___
>

--
Added file: http://bugs.python.org/file19265/unnamed

___
Python tracker 

___>>> import locale>>> locale.localeconv()
{'mon_decimal_point': '', 'int_frac_digits': 
127, 'p_sep_by_space': 127, 'frac_digits': 127, 
'thousands_sep': '', 'n_sign_posn': 127, 
'decimal_point': '.', 'int_curr_symbol': '', 
'n_cs_precedes': 127, 'p_sign_posn': 127, 
'mon_thousands_sep': '', 'negative_sign': '', 
'currency_symbol': '', 'n_sep_by_space': 127, 
'mon_grouping': [], 'p_cs_precedes': 127, 
'positive_sign': '', 'grouping': []}


 
It prints this:
>>> import locale>>> locale.format('%.3f', 
2.76)'2.760'
 
And the output of locale.format() in this case should be
'2,760'
On Mon, Oct 18, 2010 at 2:00 PM, Eric Smith rep...@bugs.python.org> wrote:

Eric Smith e...@trueblade.com> added the 
comment:Oops, I meant "locale.format('%.3f', 
2.76)", although of course the number shouldn't matter.

--


___Python tracker rep...@bugs.python.org>http://bugs.python.org/issue10135>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10135] Format specifier 'n' not working

[Boštjan Mejak]

Boštjan Mejak  added the comment:

So do I need additional things to set in my code if I use the 'n' format
specifier in order for it to be locale-aware? So using just the 'n' format
specifier is not enough? Please explain in depth.

On Mon, Oct 18, 2010 at 7:32 PM, Eric Smith  wrote:

>
> Eric Smith  added the comment:
>
> It looks like the float.__format__ code is correctly using the value of
> decimal_point = '.'. It also agrees with locale.format().
>
> How are you setting the locale? The problem appears to be either how you
> are setting the locale or the contents of the locale, not in the formatting
> code.
>
> --
>
> ___
> Python tracker 
> 
> ___
>

--
Added file: http://bugs.python.org/file19266/unnamed

___
Python tracker 

___So do I need additional things to set in my code if I use the 'n' 
format specifier in order for it to be locale-aware? So using just the 
'n' format specifier is not enough? Please explain in 
depth.
On Mon, Oct 18, 2010 at 7:32 PM, Eric Smith rep...@bugs.python.org> 
wrote:

Eric Smith e...@trueblade.com> 
added the comment:

It looks like the float.__format__ code is correctly using the value of 
decimal_point = '.'. It also agrees with locale.format().

How are you setting the locale? The problem appears to be either how you are 
setting the locale or the contents of the locale, not in the formatting 
code.

--

___
Python tracker rep...@bugs.python.org>
http://bugs.python.org/issue10135>
___

___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10073] calendar.isleap() not checking parameter type

[Boštjan Mejak]

Boštjan Mejak  added the comment:

Also, your "pedantic" version of isleap() is not pedantic at all.

return date(year, 3, 1) - date(year, 2, 1) == timedelta(29)
does not seem readable at all. Readability counts!

return date(year, 3, 1) is not understandable. What are the arguments 3 and
1 in the date() function for?

On Mon, Oct 18, 2010 at 8:06 PM, Boštjan Mejak wrote:

> else:
> -->ndays = (date(year, month + 1, 1) - first).days
> return first.weekday(), ndays
>
> Oh my God! The line with a pointer is so ugly!
>
> On Mon, Oct 18, 2010 at 7:59 PM, Alexander Belopolsky <
> rep...@bugs.python.org> wrote:
>
>>
>> Alexander Belopolsky  added the
>> comment:
>>
>> The most pedantic implementation of calendar.isleap() would be
>>
>> from datetime import date, timedelta
>> def isleap(year):
>>return date(year, 3, 1) - date(year, 2, 1) == timedelta(29)
>>
>> Since python calendar only supports years in the range [1, ], the
>> above will properly raise ValueError: year is out of range on negative or
>> zero year.  This also guarantees that calendar module's notion of leap year
>> is the same as that of datetime module.
>>
>> If this is found to be a worthwhile change, I would also rewrite
>> monthrange as
>>
>> def monthrange(year, month):
>>first = date(year, month, 1)
>>if month == 12:
>>ndays = 31
>>else:
>>ndays = (date(year, month + 1, 1) - first).days
>>return first.weekday(), ndays
>>
>> --
>>
>> ___
>> Python tracker 
>> 
>> ___
>>
>
>

--
Added file: http://bugs.python.org/file19267/unnamed

___
Python tracker 

___Also, your "pedantic" version of isleap() is not pedantic at 
all.return 
date(year, 3, 1) - date(year, 2, 1) == timedelta(29)
does not seem 
readable at all. Readability counts!
return 
date(year, 3, 1) is not understandable. What are the arguments 3 and 1 in the 
date() function for?
On Mon, Oct 18, 2010 
at 8:06 PM, Boštjan Mejak bostjan.me...@gmail.com> 
wrote:
    else:-->   
 ndays = (date(year, month + 1, 1) - first).days    return 
first.weekday(), ndays
Oh my God! The 
line with a pointer is so ugly!

On 
Mon, Oct 18, 2010 at 7:59 PM, Alexander Belopolsky rep...@bugs.python.org> wrote:


Alexander Belopolsky belopol...@users.sourceforge.net> added the comment:

The most pedantic implementation of calendar.isleap() would be

from datetime import date, timedelta
def isleap(year):
    return date(year, 3, 1) - date(year, 2, 1) == timedelta(29)

Since python calendar only supports years in the range [1, ], the above 
will properly raise ValueError: year is out of range on negative or zero year. 
 This also guarantees that calendar module's notion of leap year is the 
same as that of datetime module.



If this is found to be a worthwhile change, I would also rewrite monthrange 
as

def monthrange(year, month):
    first = date(year, month, 1)
    if month == 12:
        ndays = 31
    else:
        ndays = (date(year, month + 1, 1) - first).days
    return first.weekday(), ndays

--

___
Python tracker rep...@bugs.python.org>
http://bugs.python.org/issue10073>
___


___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10073] calendar.isleap() not checking parameter type

[Boštjan Mejak]

Boštjan Mejak  added the comment:

else:
-->ndays = (date(year, month + 1, 1) - first).days
return first.weekday(), ndays

Oh my God! The line with a pointer is so ugly!

On Mon, Oct 18, 2010 at 7:59 PM, Alexander Belopolsky <
rep...@bugs.python.org> wrote:

>
> Alexander Belopolsky  added the comment:
>
> The most pedantic implementation of calendar.isleap() would be
>
> from datetime import date, timedelta
> def isleap(year):
>return date(year, 3, 1) - date(year, 2, 1) == timedelta(29)
>
> Since python calendar only supports years in the range [1, ], the above
> will properly raise ValueError: year is out of range on negative or zero
> year.  This also guarantees that calendar module's notion of leap year is
> the same as that of datetime module.
>
> If this is found to be a worthwhile change, I would also rewrite monthrange
> as
>
> def monthrange(year, month):
>first = date(year, month, 1)
>if month == 12:
>ndays = 31
>else:
>ndays = (date(year, month + 1, 1) - first).days
>return first.weekday(), ndays
>
> --
>
> ___
> Python tracker 
> 
> ___
>

--
Added file: http://bugs.python.org/file19268/unnamed

___
Python tracker 

___    else:-->    ndays 
= (date(year, month + 1, 1) - first).days    return first.weekday(), 
ndays
Oh my God! The line with a pointer is so ugly!
On Mon, Oct 18, 2010 at 7:59 PM, 
Alexander Belopolsky rep...@bugs.python.org> 
wrote:

Alexander Belopolsky belopol...@users.sourceforge.net>
 added the comment:

The most pedantic implementation of calendar.isleap() would be

from datetime import date, timedelta
def isleap(year):
    return date(year, 3, 1) - date(year, 2, 1) == timedelta(29)

Since python calendar only supports years in the range [1, ], the above 
will properly raise ValueError: year is out of range on negative or zero year. 
 This also guarantees that calendar module's notion of leap year is the 
same as that of datetime module.


If this is found to be a worthwhile change, I would also rewrite monthrange 
as

def monthrange(year, month):
    first = date(year, month, 1)
    if month == 12:
        ndays = 31
    else:
        ndays = (date(year, month + 1, 1) - first).days
    return first.weekday(), ndays

--

___
Python tracker rep...@bugs.python.org>
http://bugs.python.org/issue10073>
___

___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10135] Format specifier 'n' not working

[Boštjan Mejak]

Boštjan Mejak  added the comment:

I thought having "Slovenian" locale set in Windows OS is the way the 'n'
format specifier works. So I must set the locale in the app. Now we're
cookin'! ;) Thanks Georg.

On Mon, Oct 18, 2010 at 8:14 PM, Georg Brandl wrote:

>
> Georg Brandl  added the comment:
>
> You need to call setlocale() in your program.  For more in-depth
> explanations, please refer to the docs at <
> http://docs.python.org/library/locale>.
>
> --
> nosy: +georg.brandl
>
> ___
> Python tracker 
> 
> ___
>

--
Added file: http://bugs.python.org/file19269/unnamed

___
Python tracker 

___I thought having "Slovenian" locale set in Windows OS is the way the 
'n' format specifier works. So I must set the locale in the app. Now 
we're cookin'! ;) Thanks Georg.
On Mon, Oct 18, 2010 at 8:14 PM, Georg Brandl rep...@bugs.python.org> 
wrote:

Georg Brandl ge...@python.org> 
added the comment:

You need to call setlocale() in your program.  For more in-depth explanations, 
please refer to the docs at http://docs.python.org/library/locale>.


--
nosy: +georg.brandl

___
Python tracker rep...@bugs.python.org>
http://bugs.python.org/issue10135>
___

___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10073] calendar.isleap() not checking parameter type

[Boštjan Mejak]

Changes by Boštjan Mejak :


Removed file: http://bugs.python.org/file19255/calendar-isleap.patch

___
Python tracker 
<http://bugs.python.org/issue10073>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10073] calendar.isleap() not checking parameter type

[Boštjan Mejak]

Boštjan Mejak  added the comment:

I have uploaded a new patch. It removes the  if year == 0  nonsense. Check it 
out. I hope you like it now.

When you were organizing the Standard Library, you didn't fix flaws in the 
calendar module. What I have in mind is, for example, the isleap() function 
which should be defined as is_leap(). But now it's all too late for that fixes.

Please apply my patch for calendar.isleap() to the trunk. Thanks.

--
Added file: http://bugs.python.org/file19275/calendar-isleap.patch

___
Python tracker 
<http://bugs.python.org/issue10073>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10073] calendar.isleap() not checking parameter type

[Boštjan Mejak]

Boštjan Mejak  added the comment:

I have read the Zen of PYthon before. I have also written a typo report. But
got rejected. No one listens to my ideas. So why do you have a bug tracker
anyway?

On Tue, Oct 19, 2010 at 6:46 AM, Éric Araujo  wrote:

>
> Éric Araujo  added the comment:
>
> > for example, the isleap() function which should be defined as is_leap()
> Who says that?  Not PEP 8: “Function names should be lowercase, with words
> separated by underscores *as necessary to improve readability*” (emphasis
> mine).  isleap is perfectly readable.
>
> > But now it's all too late for that fixes.
> You’ll find that Python has a balance between readability/ease of use and
> pragmatism.  In some cases, changes can’t be made, but it’s best to accept
> it and move on to the next issue.  Working on feature requests instead of
> style issues is great.
>
> On a closing note, I’ll let you enjoy the Zen of Python:
> $ python -m this
>
> --
>
> ___
> Python tracker 
> 
> ___
>

--
Added file: http://bugs.python.org/file19283/unnamed

___
Python tracker 

___I have read the Zen of PYthon before. I have also written a typo report. But 
got rejected. No one listens to my ideas. So why do you have a bug tracker 
anyway?On Tue, Oct 19, 2010 at 6:46 AM, Éric 
Araujo rep...@bugs.python.org> 
wrote:

Éric Araujo mer...@netwok.org> 
added the comment:

> for example, the isleap() function which should be defined as is_leap()
Who says that?  Not PEP 8: “Function names should be lowercase, with 
words separated by underscores *as necessary to improve readability*” 
(emphasis mine).  isleap is perfectly readable.

> But now it's all too late for that fixes.
You’ll find that Python has a balance between readability/ease of use 
and pragmatism.  In some cases, changes can’t be made, but it’s best to 
accept it and move on to the next issue.  Working on feature requests instead 
of style issues is great.


On a closing note, I’ll let you enjoy the Zen of Python:
$ python -m this

--

___
Python tracker rep...@bugs.python.org>
http://bugs.python.org/issue10073>
___

___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10073] calendar.isleap() not checking parameter type

[Boštjan Mejak]

Boštjan Mejak  added the comment:

>
> your change to the parentheses changes the semantics. (Georg Brandl)

How does adding those parens change semantics? The behaviour of the function
isleap() is the same. I have throughtly tested this function and found no
semantic errors in it. So the parens don't matter for behaviour, only for
clarity they matter. But since you decided not to fix this, I won't push the
envelope. At least fix the docstrings to match the return value. Please fix
the docstrings to """Return True for leap years, False for non-leap
years."""

On Tue, Oct 19, 2010 at 7:02 PM, Alexander Belopolsky <
rep...@bugs.python.org> wrote:

>
> Alexander Belopolsky  added the comment:
>
> On Tue, Oct 19, 2010 at 12:34 PM, Boštjan Mejak 
> wrote:
> > I have also written a typo report. But
> > got rejected. No one listens to my ideas. So why do you have a bug
> tracker
> > anyway?
>
> Bug tracker is not the place to discuss ideas.  We have python-ideas
> mailing list for that.
>
> I searched the tracker and found four documentation issues that you
> submitted in the past: #4389, #4648, #4649, and #6475.  In each case,
> your issue received attention from the most senior python developers.
> In each case the issue was closed with a detailed comment explaining
> the reasons for rejection.
>
> I think if you search the tracker for issues with "accepted" or
> "fixed" resolution, you will understand why we have the bug tracker.
> Reading successful reports may also help you to submit better reports
> in the future.
>
> --
>
> ___
> Python tracker 
> 
> ___
>

--
Added file: http://bugs.python.org/file19284/unnamed

___
Python tracker 

___
your change to the parentheses changes the semantics. (Georg 
Brandl)How does adding those parens change 
semantics? The behaviour of the function isleap() is the same. I have 
throughtly tested this function and found no semantic errors in it. So the 
parens don't matter for behaviour, only for clarity they matter. But since 
you decided not to fix this, I won't push the envelope. At least fix the 
docstrings to match the return value. Please fix the docstrings to 
"""Return True for leap years, False for non-leap 
years."""
On Tue, Oct 19, 2010 at 7:02 PM, 
Alexander Belopolsky rep...@bugs.python.org> 
wrote:

Alexander Belopolsky belopol...@users.sourceforge.net>
 added the comment:

On Tue, Oct 19, 2010 at 12:34 PM, Boštjan Mejak rep...@bugs.python.org> wrote:
> I have also written a typo report. But
> got rejected. No one listens to my ideas. So why do you have a bug 
tracker
> anyway?

Bug tracker is not the place to discuss ideas.  We have python-ideas
mailing list for that.

I searched the tracker and found four documentation issues that you
submitted in the past: #4389, #4648, #4649, and #6475.  In each case,
your issue received attention from the most senior python developers.
In each case the issue was closed with a detailed comment explaining
the reasons for rejection.

I think if you search the tracker for issues with "accepted" or
"fixed" resolution, you will understand why we have the bug 
tracker.
Reading successful reports may also help you to submit better reports
in the future.

--

___
Python tracker rep...@bugs.python.org>
http://bugs.python.org/issue10073>
___

___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10073] calendar.isleap() not checking parameter type

[Boštjan Mejak]

Changes by Boštjan Mejak :


Removed file: http://bugs.python.org/file19284/unnamed

___
Python tracker 
<http://bugs.python.org/issue10073>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10073] calendar.isleap() not checking parameter type

[Boštjan Mejak]

Changes by Boštjan Mejak :


Removed file: http://bugs.python.org/file19275/calendar-isleap.patch

___
Python tracker 
<http://bugs.python.org/issue10073>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10073] calendar.isleap() not checking parameter type

[Boštjan Mejak]

Boštjan Mejak  added the comment:

I am applying a patch that only fixes the docstrings to match the return value 
of calendar.isleap(). The return value of isleap() is not 1 or 0 -- it is True 
or False. Please apply the patch. Thank you.

--
Added file: http://bugs.python.org/file19285/isleap-docstrings.patch

___
Python tracker 
<http://bugs.python.org/issue10073>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10073] calendar.isleap() not checking parameter type

[Boštjan Mejak]

Boštjan Mejak  added the comment:

Thank you for applying my patch. Glad to help. Please apply it to the trunk and 
other branches as well.

--

___
Python tracker 
<http://bugs.python.org/issue10073>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10092] calendar does not restore locale properly

[Boštjan Mejak]

Boštjan Mejak  added the comment:

It seems that calendar.LocaleTextCalendar() changes the locale for the current 
interpreter session to the one you pass to argument 'locale'. This is a bug to 
be fixed.

--
nosy: +Retro

___
Python tracker 
<http://bugs.python.org/issue10092>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10092] calendar does not restore locale properly

[Boštjan Mejak]

Boštjan Mejak  added the comment:

>
> Would you like to try to make a patch for Python 3.2?

I'm not that geeky. :)

On Tue, Oct 19, 2010 at 8:36 PM, Éric Araujo  wrote:

>
> Éric Araujo  added the comment:
>
> Indeed.  Would you like to try to make a patch for Python 3.2?  Help is
> here: http://www.python.org/dev/ (especially
> http://www.python.org/dev/patches/ ) and here:
> http://docs.pythonsprints.com/core_development/beginners.html
>
> --
>
> ___
> Python tracker 
> 
> ___
>

--
Added file: http://bugs.python.org/file19286/unnamed

___
Python tracker 

___
Would you like to try to make a 
patch for Python 3.2?I'm not that geeky. 
:) 
On Tue, Oct 19, 2010 at 8:36 PM, Éric Araujo 
rep...@bugs.python.org> 
wrote:

Éric Araujo mer...@netwok.org> 
added the comment:

Indeed.  Would you like to try to make a patch for Python 3.2?  Help is 
here: http://www.python.org/dev/"; 
target="_blank">http://www.python.org/dev/ (especially http://www.python.org/dev/patches/"; 
target="_blank">http://www.python.org/dev/patches/ ) and here: http://docs.pythonsprints.com/core_development/beginners.html"; 
target="_blank">http://docs.pythonsprints.com/core_development/beginners.html


--

___
Python tracker rep...@bugs.python.org>
http://bugs.python.org/issue10092>
___

___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10147] Python Documentation bugs

[Boštjan Mejak]

New submission from Boštjan Mejak :

Please read the docs here: 
http://docs.python.org/py3k/reference/expressions#boolean-operations

This is the last sentence in the '5.10. Boolean operations' text):
([...] Because not has to >>>invent<<< a value anyway, it does not bother to 
return a value of the same type as its argument, so e.g., not 'foo' yields 
False, not ''.)

Fix to:
([...] Because not has to >>>invert<<< a value anyway, it does not bother to 
return a value of the same type as its argument, so e.g., not 'foo' yields 
False, not ''.)

--
assignee: d...@python
components: Documentation
messages: 119160
nosy: Retro, d...@python
priority: normal
severity: normal
status: open
title: Python Documentation bugs
versions: 3rd party, Python 2.5, Python 2.6, Python 2.7, Python 3.1, Python 
3.2, Python 3.3

___
Python tracker 
<http://bugs.python.org/issue10147>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10147] Python Documentation bugs

[Boštjan Mejak]

Boštjan Mejak  added the comment:

There is one more typo bug I noted in the documentation. Please go here: 
http://docs.python.org/library/locale#locale.setlocale

Fix this text...
setlocale() is not >>>thread safe<<< on most systems.

...like this:
setlocale() is not >>>thread-safe<<< on most systems.

--

___
Python tracker 
<http://bugs.python.org/issue10147>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10092] calendar does not restore locale properly

[Boštjan Mejak]

Boštjan Mejak  added the comment:

>>> import calendar
>>> calendar.LocaleTextCalendar(locale='fr_FR').formatmonthname(2010,10,10)
Traceback (most recent call last):
  File "", line 1, in 
  File "C:\Python27\lib\calendar.py", line 522, in formatmonthname
with TimeEncoding(self.locale) as encoding:
  File "C:\Python27\lib\calendar.py", line 489, in __enter__
self.oldlocale = _locale.setlocale(_locale.LC_TIME, self.locale)
  File "C:\Python27\lib\locale.py", line 531, in setlocale
return _setlocale(category, locale)
locale.Error: unsupported locale setting

Is it just my machine or is this a common thing on most machines? If I do a 
test and I try to set a locale with the setlocale() method, I get this 
"locale.Error: unsupported locale setting". So I gather that the method 
setlocale() is broken and we should fix it before fixing the 
Locale{Text,HTML}Calendar ones.


The way setlocale() is implemented, is this:

def setlocale(category, value=None):
""" setlocale(integer,string=None) -> string.
Activates/queries locale processing.
"""
if value not in (None, '', 'C'):
raise Error, '_locale emulation only supports "C" locale'
return 'C'


Please note that the online documentation documents its API like this:
locale.setlocale(category[, locale])  See 
http://docs.python.org/library/locale.html#locale.setlocale

So you can see that the implementation differs from the documentation in that 
it documents the 2nd argument as 'locale' where in the implementation there is 
'value'. If that's a bug, I don't know.

Anyway, please fix the implementation. I found out some very interesting 
thing... Note the line  "if value not in (None, '', 'C')"  in the 
implementation. This is the faulty thing in the function because NoneType is 
not iterable.

Test it for yourself in the interpreter:
>>> value = None
>>> value not in None
Traceback (most recent call last):
  File "", line 1, in 
TypeError: argument of type 'NoneType' is not iterable

So this setlocale() always raises an error. Please fix this.

Of course, this is valid:
>>> value = None
>>> value is not None
False

No error here. So try to combine this into a workable patch. Thanks.

--

___
Python tracker 
<http://bugs.python.org/issue10092>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10092] calendar does not restore locale properly

[Boštjan Mejak]

Boštjan Mejak  added the comment:

Thank you so much for your answer. The
locale.setlocale(category=locale.LC_NUMERIC,
locale="Slovenian")  works like a charm in my application. Now the 'n'
format specifier works as I want. But tell me whether the 'n' format
specifier can be forced to round the float to just one decimal place. I know
that the 'f' format specifier does that by specifying ".1f", but 'f' is not
locale-aware. I have set the 'n' format specifier in my application like
".3n", which is okay if the returned number is two integers and one decimal,
but is not okay if the returned number is one integer and two decimals,
because I want just one decimal, always. How can I make that by using the
'n' format specifier?

On Wed, Oct 20, 2010 at 11:37 AM, Tim Golden  wrote:

>
> Tim Golden  added the comment:
>
> Boštjan, the code segment you quote is the *fallback* if the
> C module hasn't been built for some reason. The module simply
> calls through to the underlying C Library. I notice you're
> running on Windows, so this is a useful MS page:
>
> http://msdn.microsoft.com/en-us/library/x99tb11d%28VS.71%29.aspx
>
> and you can see there that a call of setlocale (LC_ALL, "English")
> is valid (of "French" if you prefer):
>
> Python 3.1.2 (r312:79149, Mar 21 2010, 00:41:52) [MSC v.1500 32 bit
> (Intel)] on win32
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import locale
> >>> locale.setlocale (locale.LC_ALL, "French")
> 'French_France.1252'
> >>>
>
> --
> nosy: +tim.golden
>
> ___
> Python tracker 
> 
> ___
>

--
Added file: http://bugs.python.org/file19306/unnamed

___
Python tracker 

___Thank you so much for your answer. The  locale.setlocale(category=locale.LC_NUMERIC,
 locale="Slovenian")  works like a charm in my application. Now the 
'n' format specifier works as I want. But tell me whether the 
'n' format specifier can be forced to round the float to just one 
decimal place. I know that the 'f' format specifier does that by 
specifying ".1f", but 'f' is not locale-aware. I have set the 
'n' format specifier in my application like ".3n", which is 
okay if the returned number is two integers and one decimal, but is not okay if 
the returned number is one integer and two decimals, because I want just one 
decimal, always. How can I make that by using the 'n' format 
specifier?

On Wed, Oct 20, 2010 at 11:37 AM, Tim 
Golden rep...@bugs.python.org> wrote:


Tim Golden m...@timgolden.me.uk> added the comment:

Boštjan, the code segment you quote is the *fallback* if the
C module hasn't been built for some reason. The module simply
calls through to the underlying C Library. I notice you're
running on Windows, so this is a useful MS page:

http://msdn.microsoft.com/en-us/library/x99tb11d%28VS.71%29.aspx"; 
target="_blank">http://msdn.microsoft.com/en-us/library/x99tb11d%28VS.71%29.aspx

and you can see there that a call of setlocale (LC_ALL, "English")
is valid (of "French" if you prefer):

Python 3.1.2 (r312:79149, Mar 21 2010, 00:41:52) [MSC v.1500 32 bit
(Intel)] on win32
Type "help", "copyright", "credits" or 
"license" for more information.
>>> import locale
>>> locale.setlocale (locale.LC_ALL, "French")
'French_France.1252'
>>>

--
nosy: +tim.golden

___
Python tracker rep...@bugs.python.org>
http://bugs.python.org/issue10092>
___


___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10092] calendar does not restore locale properly

[Boštjan Mejak]

Boštjan Mejak  added the comment:

Please respond...

On Wed, Oct 20, 2010 at 7:05 PM, Boštjan Mejak wrote:

>
> Boštjan Mejak  added the comment:
>
> Thank you so much for your answer. The
> locale.setlocale(category=locale.LC_NUMERIC,
> locale="Slovenian")  works like a charm in my application. Now the 'n'
> format specifier works as I want. But tell me whether the 'n' format
> specifier can be forced to round the float to just one decimal place. I
> know
> that the 'f' format specifier does that by specifying ".1f", but 'f' is not
> locale-aware. I have set the 'n' format specifier in my application like
> ".3n", which is okay if the returned number is two integers and one
> decimal,
> but is not okay if the returned number is one integer and two decimals,
> because I want just one decimal, always. How can I make that by using the
> 'n' format specifier?
>
> On Wed, Oct 20, 2010 at 11:37 AM, Tim Golden 
> wrote:
>
> >
> > Tim Golden  added the comment:
> >
> > Boštjan, the code segment you quote is the *fallback* if the
> > C module hasn't been built for some reason. The module simply
> > calls through to the underlying C Library. I notice you're
> > running on Windows, so this is a useful MS page:
> >
> > http://msdn.microsoft.com/en-us/library/x99tb11d%28VS.71%29.aspx
> >
> > and you can see there that a call of setlocale (LC_ALL, "English")
> > is valid (of "French" if you prefer):
> >
> > Python 3.1.2 (r312:79149, Mar 21 2010, 00:41:52) [MSC v.1500 32 bit
> > (Intel)] on win32
> > Type "help", "copyright", "credits" or "license" for more information.
> > >>> import locale
> > >>> locale.setlocale (locale.LC_ALL, "French")
> > 'French_France.1252'
> > >>>
> >
> > --
> > nosy: +tim.golden
> >
> > ___
> > Python tracker 
> > 
> > ___
> >
>
> --
> Added file: http://bugs.python.org/file19306/unnamed
>
> ___
> Python tracker 
> 
> ___
>

--
Added file: http://bugs.python.org/file19316/unnamed

___
Python tracker 

___Please respond...On Wed, Oct 20, 2010 at 7:05 
PM, Boštjan Mejak rep...@bugs.python.org> 
wrote:

Boštjan Mejak bostjan.me...@gmail.com> added the 
comment:

Thank you so much for your answer. The
locale.setlocale(category=locale.LC_NUMERIC,
locale="Slovenian")  works like a charm in my application. Now the 
'n'
format specifier works as I want. But tell me whether the 'n' format
specifier can be forced to round the float to just one decimal place. I know
that the 'f' format specifier does that by specifying ".1f", 
but 'f' is not
locale-aware. I have set the 'n' format specifier in my application 
like
".3n", which is okay if the returned number is two integers and one 
decimal,
but is not okay if the returned number is one integer and two decimals,
because I want just one decimal, always. How can I make that by using the
'n' format specifier?

On Wed, Oct 20, 2010 at 11:37 AM, Tim Golden rep...@bugs.python.org> wrote:

>
> Tim Golden m...@timgolden.me.uk> added the 
comment:
>
> Boštjan, the code segment you quote is the *fallback* if the
> C module hasn't been built for some 
reason. The module simply
> calls through to the underlying C Library. I notice you're
> running on Windows, so this is a useful MS page:
>
> http://msdn.microsoft.com/en-us/library/x99tb11d%28VS.71%29.aspx"; 
target="_blank">http://msdn.microsoft.com/en-us/library/x99tb11d%28VS.71%29.aspx
>
> and you can see there that a call of setlocale (LC_ALL, 
"English")
> is valid (of "French" if you prefer):
>
> Python 3.1.2 (r312:79149, Mar 21 2010, 00:41:52) [MSC v.1500 32 bit
> (Intel)] on win32
> Type "help", "copyright", "credits" or 
"license" for more information.
> >>> import locale
> >>> locale.setlocale (locale.LC_ALL, "French")
> 'French_France.1252'
> >>>
>
> --
> nosy: +tim.golden
>
> ___
> Python tracker rep...@bugs.python.org>
> http://bugs.python.org/issue10092>
> ___
>

--
Added file: http://bugs.python.org/file19306/unnamed"; 
target="_blank">http://bugs.python.org/file19306/unnamed

___
Python tracker rep...@bugs.python.org>
http://bugs.python.org/issue10092>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/pyth

[issue10147] Python Documentation bugs

[Boštjan Mejak]

Boštjan Mejak  added the comment:

All the words that Georg Brandl fixed for this issue are okay as they stand.
Please leave them as they are written. Thank you.

On Fri, Oct 22, 2010 at 1:19 AM, Marc-Andre Lemburg
wrote:

>
> Marc-Andre Lemburg  added the comment:
>
> Éric Araujo wrote:
> >
> > Éric Araujo  added the comment:
> >
> > Adjectives require hyphens but nouns do not.  “thread-safety” should be
> reverted to “thread safety”.  I haven’t searched for a grammar 
> reference,
> but you can take Wikipedia as an example: “Thread safety is a computer
> programming concept applicable in the context of multi-threaded programs. A
> piece of code is thread-safe if it functions correctly during simultaneous
> execution by multiple threads.”
>
> Are you sure ?
>
> http://en.wikipedia.org/wiki/English_compound#Types_of_compound_nouns
>
> This appears to be more a question of personal style than a
> grammar rule.
>
> --
> nosy: +lemburg
>
> ___
> Python tracker 
> 
> ___
>

--
Added file: http://bugs.python.org/file19333/unnamed

___
Python tracker 

___All the words that Georg Brandl fixed for this issue are okay as they stand. 
Please leave them as they are written. Thank you.On Fri, Oct 22, 2010 at 1:19 AM, Marc-Andre Lemburg rep...@bugs.python.org> 
wrote:

Marc-Andre Lemburg m...@egenix.com> 
added the comment:

Éric Araujo wrote:
>
> Éric Araujo mer...@netwok.org> added the comment:
>
> Adjectives require hyphens but nouns do not.  “thread-safety” should 
be reverted to “thread safety”.  I haven’t searched for a grammar 
reference, but you can take Wikipedia as an example: “Thread safety is a 
computer programming concept applicable in the context of multi-threaded 
programs. A piece of code is thread-safe if it functions correctly during 
simultaneous execution by multiple threads.”


Are you sure ?

http://en.wikipedia.org/wiki/English_compound#Types_of_compound_nouns"; 
target="_blank">http://en.wikipedia.org/wiki/English_compound#Types_of_compound_nouns

This appears to be more a question of personal style than a
grammar rule.

--
nosy: +lemburg

___
Python tracker rep...@bugs.python.org>
http://bugs.python.org/issue10147>
___

___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10200] Documentation: "link use"?

[Boštjan Mejak]

New submission from Boštjan Mejak :

There's a bug in the docs at
http://docs.python.org/library/locale.html#access-to-message-catalogs in a
statement before the last. "A known exception to this rule are applications
that >>link use<< additional C libraries which internally invoke gettext()
 or dcgettext(). "

Either use the word "link" or "use" in that statement.

--
files: unnamed
messages: 119614
nosy: Retro
priority: normal
severity: normal
status: open
title: Documentation: "link use"?
Added file: http://bugs.python.org/file19370/unnamed

___
Python tracker 

___There's a bug in the docs at http://docs.python.org/library/locale.html#access-to-message-catalogs";>http://docs.python.org/library/locale.html#access-to-message-catalogs in
 a statement before the last. "A known 
exception to this rule are applications that >>link use<< 
additional C libraries which internally invoke gettext() or dcgettext(). "
Either use the word "link" or "use" in that 
statement.
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10200] Documentation: "link use"?

[Boštjan Mejak]

Changes by Boštjan Mejak :


Removed file: http://bugs.python.org/file19370/unnamed

___
Python tracker 
<http://bugs.python.org/issue10200>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10200] Documentation: "link use"?

[Boštjan Mejak]

Changes by Boštjan Mejak :


--
assignee:  -> d...@python
components: +Documentation
nosy: +d...@python
versions: +3rd party, Python 2.5, Python 2.6, Python 2.7, Python 3.1, Python 
3.2, Python 3.3

___
Python tracker 
<http://bugs.python.org/issue10200>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10200] Documentation: "link use"?

[Boštjan Mejak]

Boštjan Mejak  added the comment:

...Also, please fix a typo here: 
http://docs.python.org/library/string.html#string.Formatter.parse

"This is used by vformat() to break the string >>in to<< either literal text, 
or replacement fields."

Please fix "in to" to "into".

--

___
Python tracker 
<http://bugs.python.org/issue10200>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10200] Documentation: "link use"?

[Boštjan Mejak]

Boštjan Mejak  added the comment:

There's also a possible typo here: 
http://docs.python.org/library/string.html#format-specification-mini-language

format_spec ::=  
>>>[<<<[fill>>>]<<>>|<<
<http://bugs.python.org/issue10200>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10200] Documentation: "link use"?

[Boštjan Mejak]

Boštjan Mejak  added the comment:

Please fix all of those things. Thanks.

--

___
Python tracker 
<http://bugs.python.org/issue10200>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10200] Documentation: "link use"?

[Boštjan Mejak]

Boštjan Mejak  added the comment:

I am terribly sorry for the red alarm. I didn't mean to. But since the typos 
are all listed here, I don't want to copy&paste the reports to d...@python.org. 
Just please fix them. Thanks.

--

___
Python tracker 
<http://bugs.python.org/issue10200>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10200] Documentation: "link use"?

[Boštjan Mejak]

Boštjan Mejak  added the comment:

I forgot to mention to remove the comma in the text "This is used by
vformat()
to
break the string into either literal text, or replacement fields." found at
http://docs.python.org/library/string.html#string.Formatter.parse. to be "This
is used by 
vformat()
to
break the string into either literal text or replacement fields." Please
revisit this and remove the comma.

On Tue, Oct 26, 2010 at 9:58 PM, Georg Brandl wrote:

>
> Georg Brandl  added the comment:
>
> Fixed in r85849, r85850, and the third one isn't a typo.
>
> --
> nosy: +georg.brandl
> resolution:  -> fixed
> status: open -> closed
>
> ___
> Python tracker 
> 
> ___
>

--
Added file: http://bugs.python.org/file19375/unnamed

___
Python tracker 

___I forgot to mention to remove the comma in the text "This is used by http://docs.python.org/library/string.html#string.Formatter.vformat"; 
style="color: rgb(53, 95, 124); text-decoration: none; ">vformat() to break the 
string into either literal text, or replacement fields." found 
at http://docs.python.org/library/string.html#string.Formatter.parse";>http://docs.python.org/library/string.html#string.Formatter.parse.
 to be "This is used by http://docs.python.org/library/string.html#string.Formatter.vformat"; 
style="color: rgb(53, 95, 124); text-decoration: none; ">vformat() to break the 
string into either literal text or replacement fields." Please 
revisit this and remove the comma.
On Tue, Oct 26, 2010 at 9:58 PM, Georg Brandl 
rep...@bugs.python.org> 
wrote:

Georg Brandl ge...@python.org> 
added the comment:

Fixed in r85849, r85850, and the third one isn't a typo.

--
nosy: +georg.brandl
resolution:  -> fixed
status: open -> closed

___
Python tracker rep...@bugs.python.org>
http://bugs.python.org/issue10200>
___

___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7351] Documentation typos found in "zipfile — Work with ZIP archives"

[Boštjan Mejak]

Boštjan Mejak  added the comment:

I'm reopening this and I am making it a feature request for Python 3.2

--
components: +Interpreter Core -Documentation
resolution: wont fix -> 
status: closed -> open
type:  -> feature request
versions:  -Python 2.6, Python 2.7, Python 3.1

___
Python tracker 
<http://bugs.python.org/issue7351>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7351] Rename BadZipfile to BadZipFile for consistency

[Boštjan Mejak]

Boštjan Mejak  added the comment:

I am -1 for the alias. I want that this gets renamed in Python 3.2, not
aliased. I don't care about old pickles. Anyway, who has BadZipfile object
pickled? Just incorporate my patch and fix the docs and any test
cases/units. Thanks.

On Wed, Oct 27, 2010 at 10:43 PM, Éric Araujo wrote:

>
> Éric Araujo  added the comment:
>
> Boštjan, you need to update your patch to add the missing alias to the old
> name, as well as docs and test updates.
>
> I’m +0 on the change.
>
> --
> stage: committed/rejected -> patch review
> title: Documentation typos found in "zipfile — Work with ZIP archives" ->
> Rename BadZipfile to BadZipFile for consistency
>
> ___
> Python tracker 
> 
> ___
>

--
Added file: http://bugs.python.org/file19387/unnamed

___
Python tracker 

___I am -1 for the alias. I want that this gets renamed in Python 3.2, not 
aliased. I don't care about old pickles. Anyway, who has BadZipfile object 
pickled? Just incorporate my patch and fix the docs and any test cases/units. 
Thanks.
On Wed, Oct 27, 2010 at 10:43 PM, Éric 
Araujo rep...@bugs.python.org> 
wrote:

Éric Araujo mer...@netwok.org> 
added the comment:

Boštjan, you need to update your patch to add the missing alias to the old 
name, as well as docs and test updates.

I’m +0 on the change.

--
stage: committed/rejected -> patch review
title: Documentation typos found in "zipfile — Work with ZIP 
archives" -> Rename BadZipfile to BadZipFile for consistency

___
Python tracker rep...@bugs.python.org>
http://bugs.python.org/issue7351>
___

___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7351] Rename BadZipfile to BadZipFile for consistency

[Boštjan Mejak]

Changes by Boštjan Mejak :


Removed file: http://bugs.python.org/file19387/unnamed

___
Python tracker 
<http://bugs.python.org/issue7351>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7351] Rename BadZipfile to BadZipFile for consistency

[Boštjan Mejak]

Boštjan Mejak  added the comment:

No alias. Be stubborn and let the stdlib die in inconsistency.

On Thu, Oct 28, 2010 at 2:11 AM, Stephen Hansen wrote:

>
> Stephen Hansen > added the
> comment:
>
> You may "not care" about backwards compatibility, but introducing a
> breaking change in 3.2 for mere style-conformity is not OK, IMO. If the
> patcher insists on it being a breaking change, it should be rejected.
>
> FWIW, this casing is sufficiently bizarre and inconsistent in the module
> itself, that it seems clearly wrong and likely to produce difficulties for
> people using it-- so although I'm not upgrading to Python3 anytime soon, I'd
> really like to change my code to be BadZipFile when I do, so I'd be +1 with
> an alias. :)
>
> --
> nosy: +ixokai
>
> ___
> Python tracker 
> 
> ___
>

--
Added file: http://bugs.python.org/file19388/unnamed

___
Python tracker 

___No alias. Be stubborn and let the stdlib die in inconsistency.On Thu, Oct 28, 2010 at 2:11 AM, Stephen Hansen rep...@bugs.python.org> 
wrote:

Stephen Hansen me+pyt...@ixokai.io> added the 
comment:

You may "not care" about backwards compatibility, but introducing a 
breaking change in 3.2 for mere style-conformity is not OK, IMO. If the patcher 
insists on it being a breaking change, it should be rejected.


FWIW, this casing is sufficiently bizarre and inconsistent in the module 
itself, that it seems clearly wrong and likely to produce difficulties for 
people using it-- so although I'm not upgrading to Python3 anytime soon, 
I'd really like to change my code to be BadZipFile when I do, so I'd be 
+1 with an alias. :)


--
nosy: +ixokai

___
Python tracker rep...@bugs.python.org>
http://bugs.python.org/issue7351>
___

___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7351] Rename BadZipfile to BadZipFile for consistency

[Boštjan Mejak]

Boštjan Mejak  added the comment:

Is the trailing whitespace problem solved? Please make sure everything is
correct and that no more typos occur for this issue. And I am the original
patch author, so mention my name (Boštjan Mejak) in the NEWS file. Thanks.

On Thu, Oct 28, 2010 at 8:42 AM, Georg Brandl wrote:

>
> Georg Brandl  added the comment:
>
> Applied after review in r85874. (Please make sure your patches don't have
> trailing whitespace.)
>
> --
>
> ___
> Python tracker 
> 
> ___
>

--
Added file: http://bugs.python.org/file19397/unnamed

___
Python tracker 

___Is the trailing whitespace problem solved? Please make sure everything is 
correct and that no more typos occur for this issue. And I am the original 
patch author, so mention my name (Boštjan Mejak) in the NEWS file. Thanks.
On Thu, Oct 28, 2010 at 8:42 AM, Georg 
Brandl rep...@bugs.python.org> wrote:

Georg Brandl ge...@python.org> added the comment:

Applied after review in r85874. (Please make sure your patches don't 
have trailing whitespace.)

--

___
Python tracker rep...@bugs.python.org>
http://bugs.python.org/issue7351>
___


___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7351] Rename BadZipfile to BadZipFile for consistency

[Boštjan Mejak]

Boštjan Mejak  added the comment:

Then disable the tracker's ability to post messages via POP/IMAP. Just block
those protocols in the tracker and you won't see any gibberish anymore. ;)

On Thu, Oct 28, 2010 at 4:05 PM, Éric Araujo  wrote:

>
> Éric Araujo  added the comment:
>
> > Is the trailing whitespace problem solved?
> You can follow the link to the revision to see that it is.  Georg’s message
> implied this, too.
>
> > Please make sure everything is correct and that no more typos occur for
> this issue.
> We do.
>
> > And I am the original patch author, so mention my name (Boštjan Mejak) in
> the NEWS file. Thanks.
> We don’t add names for very small patches like this one.
>
> (P.S. Would you be so kind as to follow some netiquette in the tracker?
>  HTML email creates noisy unnamed attachments, and top-posting is redundant
> and hard to read.  Thanks in advance.)
>
> --
>
> ___
> Python tracker 
> 
> ___
>

--
Added file: http://bugs.python.org/file19399/unnamed

___
Python tracker 

___Then disable the tracker's ability to post messages via POP/IMAP. Just 
block those protocols in the tracker and you won't see any gibberish 
anymore. ;)On Thu, Oct 28, 2010 at 
4:05 PM, Éric Araujo rep...@bugs.python.org> 
wrote:

Éric Araujo mer...@netwok.org> 
added the comment:

> Is the trailing whitespace problem solved?
You can follow the link to the revision to see that it is.  Georg’s 
message implied this, too.

> Please make sure everything is correct and that no more typos occur for 
this issue.
We do.

> And I am the original patch author, so mention my name (Boštjan Mejak) in 
the NEWS file. Thanks.
We don’t add names for very small patches like this one.

(P.S. Would you be so kind as to follow some netiquette in the tracker?  HTML 
email creates noisy unnamed attachments, and top-posting is redundant and hard 
to read.  Thanks in advance.)

--

___
Python tracker rep...@bugs.python.org>
http://bugs.python.org/issue7351>
___

___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11318] Python 3.2 FAQ example code typo?

[Boštjan Mejak]

New submission from Boštjan Mejak :

I have found a possible typo in an example code of Python 3.2. It's located on 
page 32 in the PDF version of the FAQ document. The code is:

class C:
count = 0 # number of times C.__init__ called

def __init__(self):
C.count = C.count + 1

def getcount(self):
return C.count # or return self.count

The code block of the __init__ method is the thing that has the typo. Shouldn't 
 C.count = C.count + 1  be  c.count = C.count + 1 ?  Because the text after 
this code example says:

c.count also refers to C.count for any c such that isinstance(c, C) holds /.../.

How can c.count also refer to C.count if there is no c.count in the present 
code example in the FAQ of Python 3.2?

If this is a typo, please fix it for Python 3.2 and also for other Python 
versions with the same typo.

Else if this is not a typo, explain how can c.count refer to C.count if there 
is no c.count in the code example.

--
assignee: docs@python
components: Documentation
messages: 129357
nosy: Retro, docs@python
priority: normal
severity: normal
status: open
title: Python 3.2 FAQ example code typo?
versions: Python 3.2

___
Python tracker 
<http://bugs.python.org/issue11318>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10516] Add list.clear() and list.copy()

[Boštjan Mejak]

Boštjan Mejak  added the comment:

I have installed Python 3.2 final on my Windows machine and I get an
exception when doing list.copy or list.clear in the interpreter. Why is that
so?

--
Added file: http://bugs.python.org/file20886/unnamed

___
Python tracker 

___I have installed Python 3.2 final on my Windows machine and I get an exception 
when doing list.copy or list.clear in the interpreter. Why is that so?
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10516] Add list.clear() and list.copy()

[Boštjan Mejak]

Boštjan Mejak  added the comment:

Right, right. My bad. Can't wait for Python 3.3! ;)

--
Added file: http://bugs.python.org/file20887/unnamed

___
Python tracker 

___Right, right. My bad. Can't wait for Python 3.3! ;)
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11318] Python 3.2 FAQ example code typo?

[Boštjan Mejak]

Boštjan Mejak  added the comment:

>
> Caution: within a method of C, an assignment like ``self.count = 42``
> creates a new and unrelated instance named "count" in ``self``'s own dict.

More clear is to say *Caution: within a method of class C, an assignment
like ``self.count = 42`` creates a new and unrelated instance named "count"
in ``self``'s own dict.*
*
*

--
Added file: http://bugs.python.org/file20888/unnamed

___
Python tracker 

___
Caution: within a method of C, an assignment like ``self.count = 42`` creates 
a new and unrelated instance named "count" in ``self``'s own 
dict.
More clear is to say Caution: within 
a method of class C, an assignment like ``self.count = 42`` creates a new and 
unrelated instance named "count" in ``self``'s own 
dict.

___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11318] Python 3.2 FAQ example code typo?

[Boštjan Mejak]

Boštjan Mejak  added the comment:

So you're saying that if a class' name is C, then c.count is the same as
C.count? I thought Python is case-sensitive. You know: c (small letter c) is
not equal to C (big letter C) in Python. I don't understand what you mean by
c.count because my intepreter always throws an exception that c is not
defined if I feed it with this code example and do   >>> c.count

--
Added file: http://bugs.python.org/file20890/unnamed

___
Python tracker 

___So you're saying that if a class' name is C, then c.count is the same 
as C.count? I thought Python is case-sensitive. You know: c (small letter c) is 
not equal to C (big letter C) in Python. I don't understand what you mean 
by c.count because my intepreter always throws an exception that c is not 
defined if I feed it with this code example and do   >>> c.count
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11318] Python 3.2 FAQ example code typo?

[Boštjan Mejak]

Boštjan Mejak  added the comment:

I don't understand it. My bad. Please explain to me exactly what "c" refers
to.

--
Added file: http://bugs.python.org/file20891/unnamed

___
Python tracker 

___I don't understand it. My bad. Please explain to me exactly what 
"c" refers to.
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11318] Python 3.2 FAQ example code typo?

[Boštjan Mejak]

Boštjan Mejak  added the comment:

How awful! A little pointer to the tutorial where this is explained would be
also quite smashing.

--
Added file: http://bugs.python.org/file20893/unnamed

___
Python tracker 

___How awful! A little pointer to the tutorial where this is explained would be 
also quite smashing.
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11318] Python 3.2 FAQ example code typo?

[Boštjan Mejak]

Boštjan Mejak  added the comment:

"c.count also refers to C.count"  Where in the code is "c.count"? Please
explain this for the sake of really closing this issue.

--
Added file: http://bugs.python.org/file20896/unnamed

___
Python tracker 

___"c.count also refers to C.count"  Where in the code is 
"c.count"? Please explain this for the sake of really closing this 
issue.
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11318] Python 3.2 FAQ example code typo?

[Boštjan Mejak]

Boštjan Mejak  added the comment:

Eric, the thing I don't understand is why is there that "c.count" thing. How is 
it possible for "c.count" to be the same reference as "C.count"? Where is "c" 
defined?

--

___
Python tracker 
<http://bugs.python.org/issue11318>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11318] Python 3.2 FAQ example code typo?

[Boštjan Mejak]

Boštjan Mejak  added the comment:

Understood. Now I get it. If you create an instance "c" of the class "C" (so c 
= C() ) and try to get the variable "count" from that class, then "c.count" is 
the same reference as "C.count".

Please make that clearer in the FAQ by saying "If you create an instance "c" of 
the class "C", then "c.count" is the same reference as "C.count".

--

___
Python tracker 
<http://bugs.python.org/issue11318>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11373] Fix 2 new typos in the docs

[Boštjan Mejak]

New submission from Boštjan Mejak :

Try to fix this in every Python documentation that you can.

The typo was found here: http://docs.python.org/library/stdtypes.html#memoryview

"Create a memoryview that references obj. obj must support the buffer protocol. 
Builtin objects that /.../."

Fix this to "Create a memoryview that references obj, which must support the 
buffer protocol. Built-in objects that /.../."

Thank you.

--
assignee: docs@python
components: Documentation
messages: 129886
nosy: Retro, docs@python
priority: normal
severity: normal
status: open
title: Fix 2 new typos in the docs
versions: Python 2.7

___
Python tracker 
<http://bugs.python.org/issue11373>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11373] Fix 2 new typos in the docs

[Boštjan Mejak]

Boštjan Mejak  added the comment:

Please fix the word "Builtin" to "Built-in" as well. Thank you.

--

___
Python tracker 
<http://bugs.python.org/issue11373>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11373] Fix 2 new typos in the docs

[Boštjan Mejak]

Boštjan Mejak  added the comment:

I am uploading a patch that fixes both of these typos in the docs. Please apply 
it and keep up the good work.

--
versions: +Python 3.1, Python 3.2, Python 3.3
Added file: http://bugs.python.org/file20998/stdtypes_2.patch

___
Python tracker 
<http://bugs.python.org/issue11373>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11373] Fix 2 new typos in the docs

[Boštjan Mejak]

Boštjan Mejak  added the comment:

Georg, please fix all the branches. Also, the online docs are still not updated 
with this fix.

--

___
Python tracker 
<http://bugs.python.org/issue11373>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11806] Missing 2 hyphens in the docs

[Boštjan Mejak]

New submission from Boštjan Mejak :

Please see  http://docs.python.org/py3k/library/argparse.html#module-argparse  
and read the first sentence which goes...

"The argparse module makes it easy to write user friendly command line 
interfaces."

Please fix this to...

"The argparse module makes it easy to write user-friendly command-line 
interfaces."

Note: "user friendly" --> "user-friendly"
  "command line" --> "command-line"

--
assignee: docs@python
components: Documentation
messages: 133377
nosy: Retro, docs@python
priority: normal
severity: normal
status: open
title: Missing 2 hyphens in the docs
versions: Python 3.2, Python 3.3, Python 3.4

___
Python tracker 
<http://bugs.python.org/issue11806>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11806] Missing 2 hyphens in the docs

[Boštjan Mejak]

Changes by Boštjan Mejak :


--
nosy: +georg.brandl

___
Python tracker 
<http://bugs.python.org/issue11806>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11806] Missing 2 hyphens in the docs

[Boštjan Mejak]

Boštjan Mejak  added the comment:

There are more of this typos in the same chapter. Just a little below the
one of the reported sentence. Check this out...

"Assuming the Python code above is saved into a file called prog.py, it can
be run at the !! command line !! and provides useful help messages:"  --> it
has to be: command-line

But then this...

"When run with the appropriate arguments, it prints either the sum or the
max of the !! command-line !! integers:"  --> here it is correct!

I don't get it. Please be consistent. Thanks.

--
Added file: http://bugs.python.org/file21638/unnamed

___
Python tracker 

___There are more of this typos in the same chapter. Just a little below the one 
of the reported sentence. Check this out..."Assuming the Python code above is saved into a file 
called prog.py, it can be run 
at the !! command line !! and provides useful help messages:"  --> it 
has to be: command-line
But then 
this...
"When run with the appropriate arguments, it prints either the sum or 
the max of the !! command-line !! integers:"  --> here it is 
correct!
I 
don't get it. Please be consistent. Thanks.
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11806] Missing 2 hyphens in the docs

[Boštjan Mejak]

Boštjan Mejak  added the comment:

Georg Brandl, please fix this typos. You would understand. Thank you.

--
Added file: http://bugs.python.org/file21643/unnamed

___
Python tracker 

___Georg Brandl, please fix this typos. You would understand. Thank you.
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11806] Missing 2 hyphens in the docs

[Boštjan Mejak]

Boštjan Mejak  added the comment:

Also, please fix the main title of the argparse section...

from
15.4. argparse
—
Parser for command line options, arguments and sub-commands
to
15.4. argparse
—
Parser for command-line options, arguments and sub-commands
Please note the added hyphen (-) for the word command-line. Since this is
actually one word, it needs the hyphen. This is not Python related, but is
orthology related. Please fix all this documentation imprecisions in the
section argparse. Won't take a minute.

--
Added file: http://bugs.python.org/file21648/unnamed

___
Python tracker 

___Also, please fix the main title of the argparse 
section...from
15.4. http://docs.python.org/dev/library/argparse.html#module-argparse"; 
title="argparse: Command-line option and argument parsing library." 
style="color: rgb(53, 95, 124); text-decoration: none; ">argparse — 
Parser for command line options, arguments and sub-commands
to
15.4. http://docs.python.org/dev/library/argparse.html#module-argparse"; 
title="argparse: Command-line option and argument parsing library." 
style="color: rgb(53, 95, 124); text-decoration: none; ">argparse — 
Parser for command-line options, arguments and sub-commands
Please note the added hyphen (-) for the word command-line. Since 
this is actually one word, it needs the hyphen. This is not Python related, but 
is orthology related. Please fix all this documentation imprecisions in the 
section argparse. Won't take a minute.

___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11806] Missing 2 hyphens in the docs

[Boštjan Mejak]

Boštjan Mejak  added the comment:

If you'd look into the English dictionary, you'd find words like
coffee-table and command-line and built-in and user-friendly. The main
bother in this issue is the inconsistency with the wording "command-line".
Somewhere under the argparse section of the docs it is "command line" and
then shortly after it is "command-line". Make up your mind and be consistent
with one wording. I propose to let it be "command-line" as the major
dictionary of English language writes it, with a hyphen that is. Thank you.

--
Added file: http://bugs.python.org/file21654/unnamed

___
Python tracker 

___If you'd look into the English dictionary, you'd find words like 
coffee-table and command-line and built-in and user-friendly. The main bother 
in this issue is the inconsistency with the wording "command-line". 
Somewhere under the argparse section of the docs it is "command line" 
and then shortly after it is "command-line". Make up your mind and be 
consistent with one wording. I propose to let it be "command-line" as 
the major dictionary of English language writes it, with a hyphen that is. 
Thank you.
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11806] Missing 2 hyphens in the docs

[Boštjan Mejak]

Boštjan Mejak  added the comment:

I did a little mistake with the "coffee-table" thing. It's written as
"coffee table" (no hyphen). But other words listed are written with the
hyphen. Fix those damn things mentioned in the issue.

--
Added file: http://bugs.python.org/file21664/unnamed

___
Python tracker 

___I did a little mistake with the "coffee-table" thing. It's 
written as "coffee table" (no hyphen). But other words listed are 
written with the hyphen. Fix those damn things mentioned in the issue.
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11806] Missing 2 hyphens in the docs

[Boštjan Mejak]

Changes by Boštjan Mejak :


Removed file: http://bugs.python.org/file21638/unnamed

___
Python tracker 
<http://bugs.python.org/issue11806>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11806] Missing 2 hyphens in the docs

[Boštjan Mejak]

Changes by Boštjan Mejak :


Removed file: http://bugs.python.org/file21643/unnamed

___
Python tracker 
<http://bugs.python.org/issue11806>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11806] Missing 2 hyphens in the docs

[Boštjan Mejak]

Changes by Boštjan Mejak :


Removed file: http://bugs.python.org/file21648/unnamed

___
Python tracker 
<http://bugs.python.org/issue11806>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11806] Missing 2 hyphens in the docs

[Boštjan Mejak]

Changes by Boštjan Mejak :


Removed file: http://bugs.python.org/file21654/unnamed

___
Python tracker 
<http://bugs.python.org/issue11806>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11806] Missing 2 hyphens in the docs

[Boštjan Mejak]

Changes by Boštjan Mejak :


Removed file: http://bugs.python.org/file21664/unnamed

___
Python tracker 
<http://bugs.python.org/issue11806>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11855] urlretrieve --> urlretrieve()

[Boštjan Mejak]

New submission from Boštjan Mejak :

A typo in the docs was found here: 
http://docs.python.org/library/urllib.html#urllib.urlretrieve

Two instances of the word "urlretrieve" need to be "urlretrieve()", as other 
instances of it are, with that fancy color and a link-like look. You know what 
I mean. If you care, please fix this.

--
assignee: docs@python
components: Documentation
messages: 133887
nosy: Retro, docs@python
priority: normal
severity: normal
status: open
title: urlretrieve --> urlretrieve()
versions: Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4

___
Python tracker 
<http://bugs.python.org/issue11855>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11857] Hyphenate the argparse.rst file, patch added

[Boštjan Mejak]

New submission from Boštjan Mejak :

Please apply this patch. And fix the occurences where you think the word 
"command line" acts as a noun.

--
assignee: docs@python
components: Documentation
files: argparse.patch
keywords: patch
messages: 133893
nosy: Retro, docs@python, georg.brandl
priority: normal
severity: normal
status: open
title: Hyphenate the argparse.rst file, patch added
versions: Python 3.2, Python 3.3, Python 3.4
Added file: http://bugs.python.org/file21682/argparse.patch

___
Python tracker 
<http://bugs.python.org/issue11857>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11857] Hyphenate the argparse.rst file, patch added

[Boštjan Mejak]

Changes by Boštjan Mejak :


Removed file: http://bugs.python.org/file21682/argparse.patch

___
Python tracker 
<http://bugs.python.org/issue11857>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11857] Hyphenate the argparse.rst file, patch added

[Boštjan Mejak]

Boštjan Mejak  added the comment:

Added the new and improved patch. Now it is perfect. Please apply it.

--
Added file: http://bugs.python.org/file21687/argparse.patch

___
Python tracker 
<http://bugs.python.org/issue11857>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11885] argparse docs needs fixing

[Boštjan Mejak]

New submission from Boštjan Mejak :

Hello, I am returning to report new fixes to be made to argparse docs. The 
issues can be observed in this link:

http://docs.python.org/dev/library/argparse.html#upgrading-optparse-code


1) "When most everything in optparse had either been copy-pasted over or 
monkey-patched ..."

"When most in optparse had either been copy-pasted over or monkey-patched ..."

Word "everything" was removed.

2) "- Replace strings with implicit arguments such as %default or %prog with 
the standard python syntax to use dictionaries to format strings, that is, 
%(default)s and %(prog)s."

"- Replace strings with implicit arguments such as %default or %prog with the 
standard Python syntax to use dictionaries to format strings, that is 
%(default)s and %(prog)s."

Word "python" was fixed to "Python" and comma was deleted after "that is".


Please fix this. Thanks.

--
messages: 134141
nosy: Retro
priority: normal
severity: normal
status: open
title: argparse docs needs fixing

___
Python tracker 
<http://bugs.python.org/issue11885>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11885] argparse docs needs fixing

[Boštjan Mejak]

Changes by Boštjan Mejak :


--
assignee:  -> docs@python
components: +Documentation
nosy: +docs@python
versions: +Python 2.7, Python 3.2, Python 3.3, Python 3.4

___
Python tracker 
<http://bugs.python.org/issue11885>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11885] argparse docs needs fixing

[Boštjan Mejak]

Boštjan Mejak  added the comment:

I have also discovered some non-capitalised "python" words in the very same 
argparse docs. These 2 subtitles have those typos:

1) 15.4.1.1. Creating a parser
2) 15.4.6. Upgrading optparse code


Please fix this as well.

--

___
Python tracker 
<http://bugs.python.org/issue11885>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11885] argparse docs needs fixing

[Boštjan Mejak]

Boštjan Mejak  added the comment:

Eric, you are great! Thanks for fixing the docs. ;)

--
Added file: http://bugs.python.org/file21750/unnamed

___
Python tracker 

___Eric, you are great! Thanks for fixing the docs. ;)
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11885] argparse docs needs fixing

[Boštjan Mejak]

Boštjan Mejak  added the comment:

I ment to say Ezio. Got confused. Thanks, Ezio!

--
Added file: http://bugs.python.org/file21758/unnamed

___
Python tracker 

___I ment to say Ezio. Got confused. Thanks, Ezio!
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11931] Regular expression documentation patch

[Boštjan Mejak]

New submission from Boštjan Mejak :

I have read and fixed the regular expression documentation and made a patch. 
Ezio, please review it and apply it. Thanks.

--
assignee: docs@python
components: Documentation
files: re.patch
keywords: patch
messages: 134506
nosy: Retro, docs@python, ezio.melotti
priority: normal
severity: normal
status: open
title: Regular expression documentation patch
versions: Python 2.7, Python 3.1, Python 3.2, Python 3.3
Added file: http://bugs.python.org/file21787/re.patch

___
Python tracker 
<http://bugs.python.org/issue11931>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11931] Regular expression documentation patch

[Boštjan Mejak]

Boštjan Mejak  added the comment:

Raymond, what about the title "search() vs. match()"? There is a dot there! 
Please add the dot where I added it. Or remove it here as well. Also, "Checking 
For a Pair" is "Checking for a Pair". The word "for" must be lowercase.

--

___
Python tracker 
<http://bugs.python.org/issue11931>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10122] Documentation typo fix and a side question

[Boštjan Mejak]

Boštjan Mejak  added the comment:

If you visit  
http://docs.python.org/library/functions.html?highlight=getattr#getattr  there 
is still the word 'attributed' present in online docs. Please fix the docs 
completely.

--

___
Python tracker 
<http://bugs.python.org/issue10122>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10122] Documentation typo fix and a side question

[Boštjan Mejak]

Boštjan Mejak  added the comment:

The change is still not reflected. Why not? It's been more than a
month now. What is going on?

--

___
Python tracker 
<http://bugs.python.org/issue10122>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1710703] zipfile.ZipFile behavior inconsistent.

[Boštjan Mejak]

Boštjan Mejak  added the comment:

Please fix this patch to raise BadZipFile instead of BadZipfile. See 
http://docs.python.org/dev/library/zipfile.html?highlight=zipfile#zipfile.BadZipfile.
 The use of the class name BadZipfile is deprecated. The class name BadZipFile 
is prefered.

--
nosy: +Retro

___
Python tracker 
<http://bugs.python.org/issue1710703>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10562] Change 'j' for imaginary unit into an 'i'

[Boštjan Mejak]

New submission from Boštjan Mejak :

In Python, the letter 'j' denotes the imaginary unit. It would be great if we 
would follow mathematics in this regard and let the imaginary unit be denoted 
with an 'i'.

--
components: Interpreter Core
messages: 122662
nosy: Retro
priority: normal
severity: normal
status: open
title: Change 'j' for imaginary unit into an 'i'
type: feature request
versions: Python 3.2

___
Python tracker 
<http://bugs.python.org/issue10562>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10562] Change 'j' for imaginary unit into an 'i'

[Boštjan Mejak]

Boštjan Mejak  added the comment:

"The Python programming language also uses j to denote the imaginary unit.
MATLAB associates both i and j with the imaginary unit."
-Wikipedia

It would be a welcome feature in Python if the programming language would,
like MATLAB, associate both i and j with the imaginary unit.

--
Added file: http://bugs.python.org/file19858/unnamed

___
Python tracker 

___"The Python programming language also uses j to denote the imaginary unit. 
MATLAB associates both i and j with the imaginary unit." -http://en.wikipedia.org/wiki/Imaginary_unit#Alternative_notations";>Wikipedia
It would be a welcome feature in Python if the programming language would, 
like MATLAB, associate both i and j with the imaginary unit.
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10562] Change 'j' for imaginary unit into an 'i'

[Boštjan Mejak]

Boštjan Mejak  added the comment:

It would be great if the feature of having both j and i would exist in the
interpreter core, as well as the built-in function complex() to accept i.

--
Added file: http://bugs.python.org/file19860/unnamed

___
Python tracker 

___It would be great if the feature of having both j and i would exist in the 
interpreter core, as well as the built-in function complex() to accept i.
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10580] Installer sentence in bold

[Boštjan Mejak]

New submission from Boštjan Mejak :

The installer of Python should have consistent sentences, the ones in bold.

There's one sentence that needs fixing. The sentence "Completing the Python 
x.x.x Installer" should be "Complete the Python x.x.x Installer", because other 
sentences are in the form of "Install xxx" and "Customize xxx" (they are not 
written as "Installing xxx" and "Customizing xxx"). Please fix this.

--
components: Installation
messages: 122832
nosy: Retro
priority: normal
severity: normal
status: open
title: Installer sentence in bold
versions: Python 2.7, Python 3.1, Python 3.2, Python 3.3

___
Python tracker 
<http://bugs.python.org/issue10580>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10092] calendar does not restore locale properly

[Boštjan Mejak]

Changes by Boštjan Mejak :


Removed file: http://bugs.python.org/file19306/unnamed

___
Python tracker 
<http://bugs.python.org/issue10092>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com