[issue10073] calendar.isleap() not checking parameter type
Boštjan Mejak
report at bugs.python.org
Tue Oct 19 19:27:38 CEST 2010
Boštjan Mejak <bostjan.mejak at gmail.com> 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 <
report at bugs.python.org> wrote:
>
> Alexander Belopolsky <belopolsky at users.sourceforge.net> added the comment:
>
> On Tue, Oct 19, 2010 at 12:34 PM, Boštjan Mejak <report at 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 <report at bugs.python.org>
> <http://bugs.python.org/issue10073>
> _______________________________________
>
----------
Added file: http://bugs.python.org/file19284/unnamed
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue10073>
_______________________________________
-------------- next part --------------
<blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
your change to the parentheses changes the semantics. (Georg Brandl)</blockquote><div><br></div>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."""<div>
<br></div><div><br><div class="gmail_quote">On Tue, Oct 19, 2010 at 7:02 PM, Alexander Belopolsky <span dir="ltr"><<a href="mailto:report at bugs.python.org">report at bugs.python.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Alexander Belopolsky <<a href="mailto:belopolsky at users.sourceforge.net">belopolsky at users.sourceforge.net</a>> added the comment:<br>
<div class="im"><br>
On Tue, Oct 19, 2010 at 12:34 PM, Boštjan Mejak <<a href="mailto:report at bugs.python.org">report at bugs.python.org</a>> wrote:<br>
> I have also written a typo report. But<br>
> got rejected. No one listens to my ideas. So why do you have a bug tracker<br>
> anyway?<br>
<br>
</div>Bug tracker is not the place to discuss ideas. Â We have python-ideas<br>
mailing list for that.<br>
<br>
I searched the tracker and found four documentation issues that you<br>
submitted in the past: #4389, #4648, #4649, and #6475. Â In each case,<br>
your issue received attention from the most senior python developers.<br>
In each case the issue was closed with a detailed comment explaining<br>
the reasons for rejection.<br>
<br>
I think if you search the tracker for issues with "accepted" or<br>
"fixed" resolution, you will understand why we have the bug tracker.<br>
Reading successful reports may also help you to submit better reports<br>
in the future.<br>
<div><div></div><div class="h5"><br>
----------<br>
<br>
_______________________________________<br>
Python tracker <<a href="mailto:report at bugs.python.org">report at bugs.python.org</a>><br>
<<a href="http://bugs.python.org/issue10073" target="_blank">http://bugs.python.org/issue10073</a>><br>
_______________________________________<br>
</div></div></blockquote></div><br></div>
More information about the Python-bugs-list
mailing list