Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
stage: - needs patch
type: - enhancement
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23756
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
stage: - resolved
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23751
___
___
Python-bugs-list
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
stage: - patch review
type: - enhancement
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23738
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
resolution: - not a bug
stage: - resolved
status: open - closed
title: web course - spam
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23737
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
Removed message: http://bugs.python.org/msg238875
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23737
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
hgrepos: -302
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23737
___
___
Python-bugs-list
Ezio Melotti added the comment:
Raymond, in the meanwhile can the proposed patch be applied?
I don't think it's necessary to show that you need to import a module in order
to test its functions. Using modules also has the disadvantage that people
might not know what result to expect
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
stage: - needs patch
type: - behavior
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23702
Ezio Melotti added the comment:
+1 for 4 spaces.
Smart backspace would be nice too, but I agree it's a separate issue (unless
it's trivial to implement). Deeply-nested code in the interactive interpreter
is uncommon, and the lack of smart backspace never bothered me.
--
nosy
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
stage: - patch review
type: - enhancement
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23645
Ezio Melotti added the comment:
The Table 3-7 of http://www.unicode.org/versions/Unicode5.2.0/ch03.pdf (page 93
of the book, or 40 of the pdf) shows that if the start byte is ED the
continuation byte must be in range 80..9F. This means that, in order to decode
a sequence starting with ED
Ezio Melotti added the comment:
I think that the problem is actually with the file.write() in _show_warning().
If any of the arguments of formatwarning() are unicode, the result will be
unicode, and if file (default sys.stderr) is opened in binary mode, Python
will try to encode the unicode
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23623
___
___
Python-bugs
Ezio Melotti added the comment:
Nice document. Is that actually how Python's decoder checks things?
Yes, Python follows the Unicode standard.
* E0 followed by 80..9F: non-shortest form
* ED followed by A0..BF: surrogate
* F4 followed by 90..BF: outside defined range
If you get a decode
Ezio Melotti added the comment:
I think most of these are either implementation details or private names, so
there is no need to document them. The ones that are intended to be used by
developers or that are useful to understand the functioning of a public API
should be documented
Ezio Melotti added the comment:
A context manager here would seem a bit strange.
I still haven't thought this through, but I can't see any problem with it right
now. This would be similar to:
from contextlib import closing
with closing(MyHTMLParser()) as parser:
parser.feed(html
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +steve.dower
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17570
___
___
Python-bugs-list
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +eric.smith, ezio.melotti, mark.dickinson, rhettinger, skrah
stage: - patch review
type: - enhancement
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23602
Ezio Melotti added the comment:
Here is a patch that fixes the problem.
Even though calling .close() is the correct solution, I preferred to restore
the previous behavior and call handle_data as soon as possible.
There is a corner case in which a charref might be cut in half while feeding
Changes by Ezio Melotti ezio.melo...@gmail.com:
Removed file: http://bugs.python.org/file38376/issue23144.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23144
Changes by Ezio Melotti ezio.melo...@gmail.com:
Added file: http://bugs.python.org/file38380/issue23144.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23144
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
stage: - patch review
type: - behavior
versions: +Python 3.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23584
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23579
___
___
Python-bugs
Ezio Melotti added the comment:
I still think it would be worthwhile adding close() calls to
the examples in the documentation (Doc/library/html.parser.rst).
If I add context manager support to HTMLParser I can update the examples to use
it, but otherwise I don't think it's worth changing
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
stage: - patch review
type: - enhancement
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23595
Ezio Melotti added the comment:
#8087
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23594
___
___
Python-bugs-list mailing
Ezio Melotti added the comment:
In the patch you made some args kw-only.
Isn't that backward incompatible in case someone was passing them by position?
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22936
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23591
___
___
Python-bugs
Ezio Melotti added the comment:
I think the first sentence could be improved, even though it's correct.
A superficial reading might give the impression that function variables are
implicitly global, or that only the variables inside a function are global,
especially if the reader
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
assignee: docs@python - ezio.melotti
nosy: +ezio.melotti
stage: - commit review
versions: +Python 2.7 -Python 3.2, Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
stage: - needs patch
versions: +Python 3.5 -Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14544
Ezio Melotti added the comment:
You are right -- I didn't notice the versionadded in the docs.
Sorry for the noise.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22936
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
components: +Unicode
nosy: +ezio.melotti, haypo, ned.deily, serhiy.storchaka, terry.reedy
type: - behavior
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23583
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19481
___
___
Python-bugs
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
assignee: docs@python - ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23512
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23275
___
___
Python-bugs
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
keywords: +easy
stage: - needs patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22933
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
stage: patch review - test needed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22801
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
stage: - needs patch
type: - enhancement
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22812
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
keywords: +easy
stage: - needs patch
type: - enhancement
versions: +Python 2.7, Python 3.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23460
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23312
___
___
Python-bugs
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23192
___
___
Python-bugs
Ezio Melotti added the comment:
Agreed with what Georg said and I think the devguide can be update accordingly.
--
assignee: - docs@python
components: +Documentation
keywords: +easy
nosy: +docs@python
stage: - needs patch
___
Python tracker rep
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +benjamin.peterson
type: - enhancement
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22785
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +loewis
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23330
___
___
Python-bugs-list
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
stage: - needs patch
type: - enhancement
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22813
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22831
___
___
Python-bugs
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
components: +Unicode
nosy: +ezio.melotti, haypo, serhiy.storchaka
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23367
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +Joshua.Landau, neil.g
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22942
___
___
Python
New submission from Ezio Melotti:
The Doc/library/stdtypes.rst page describes in detail the built-in types and
their methods. As suggested in #21777 (see the comments on Rietveld), it might
be a good idea to group the documentation of some similar methods, such as
{r|l|}just, {r|l|}strip, {r
Ezio Melotti added the comment:
Zach, Ezio - if there are any other refactorings from the reviews that
you'd like to pursue, consider pulling them out to separate issues so
we don't forget about them.
See #23560.
--
___
Python tracker rep
Ezio Melotti added the comment:
While the request is reasonable, the patch seems to touch quite some code.
Since this is just to improve an error message in a somewhat obscure corner
case, I'm not sure it's worth applying it.
--
nosy: +serhiy.storchaka
stage: - patch review
versions
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue433030
___
___
Python-bugs
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23262
___
___
Python-bugs
Ezio Melotti added the comment:
That was me in #10299 (the issue contains a discussion about the ordering in
the last few messages).
Since there are only 4 functions, I think it would be ok removing them from the
table and instead add a sentence like In addition, there are other 4 built
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23504
___
___
Python-bugs
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +pitrou
type: - behavior
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23455
Ezio Melotti added the comment:
Should we add a note to the format docs, or just close this?
--
nosy: +ezio.melotti, mark.dickinson
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23460
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +michael.foord
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23469
___
___
Python-bugs
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue433028
___
___
Python-bugs
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23493
___
___
Python-bugs
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti, mark.dickinson, rhettinger, stutzbach
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23523
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23507
___
___
Python-bugs
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +steve.dower
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1559298
___
___
Python-bugs
Ezio Melotti added the comment:
Ok, so I'm closing this again.
Berker, can you add a link to this issue too on the pydotorg tracker?
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22963
Ezio Melotti added the comment:
The link in PEP 102 is still wrong, even though the pydotorg issue has been
closed.
The problem seems to affect txt PEPs (not rst ones), and it can be fixed by
simply doing:
diff --git a/pep2html.py b/pep2html.py
--- a/pep2html.py
+++ b/pep2html.py
@@ -48,11
Ezio Melotti added the comment:
DeprecationWarning: Base class for warnings about deprecated features.
UserWarning: Base class for warnings generated by user code.
RuntimeWarning: Base class for warnings about dubious runtime behavior.
FutureWarning: Base class for warnings about constructs
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
Removed message: http://bugs.python.org/msg234435
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12312
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
assignee: docs@python - ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23144
Ezio Melotti added the comment:
In the code there is this comment:
# 0**0 = NaN (!), x**0 = 1 for nonzero x (including +/-Infinity)
and raising the error for this specific case seems intentional.
--
nosy: +ezio.melotti, facundobatista, mark.dickinson, rhettinger, skrah
versions
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +brett.cannon, eric.snow, ezio.melotti, ncoghlan
type: - behavior
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23203
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23119
___
___
Python-bugs
Ezio Melotti added the comment:
Without changesets information (not included in the git format) rietveld will
try to apply the patch on default and if it applies clearly it will work, so
creating the patch against an up to date py3 clone should work even with the
git format
Ezio Melotti added the comment:
Do you see the same messages if you use the webbrowser module directly?
--
components: +Library (Lib) -Extension Modules
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23194
Ezio Melotti added the comment:
Does anything change if you use open/open_new/open_new_tab, and/or use
different urls (http and https)?
--
nosy: +hynek, ned.deily, ronaldoussoren
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Ezio Melotti added the comment:
You should propose this to the python-ideas mailing list.
FWIW, if this is accepted, I would use str as default map_function.
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Ezio Melotti added the comment:
On CPython small ints are cached to improve performances.
This is an implementation detail and is should not be used to compare ints
(== should be used instead).
--
nosy: +ezio.melotti
resolution: - not a bug
stage: - resolved
status: open - closed
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19548
___
___
Python-bugs
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23061
___
___
Python-bugs
Ezio Melotti added the comment:
A while ago there was a discussion about updating the MIME registry on bug fix
releases too, and I seem to remember people agreed it should be done. If this
is indeed the case and the patch is accepted for 3.5, should it also be
backported to 2.7 and 3.4
Ezio Melotti added the comment:
I have a few comments about the patch.
About the markup:
1) you can specify the default highlight (bash) once at the top of the file,
and just use :: afterwards instead of .. code-block::;
2) the used for some headers is inconsistent with the other files;
3
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22942
___
___
Python-bugs
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
resolution: - duplicate
stage: - resolved
status: open - closed
superseder: - ensurepip and distutils' build_scripts fails on Windows when
path to Python contains accented characters
___
Python
Ezio Melotti added the comment:
LGTM.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22578
___
___
Python-bugs-list mailing list
Unsubscribe
Ezio Melotti added the comment:
So you are suggesting to fix bugs in re to make it closer to regex, and then
replace re with a forked subset of regex that doesn't include advanced
features, or just to fix/improve re until it matches the behavior of regex?
If you are suggesting the former, I
Ezio Melotti added the comment:
Ok, regardless of what will happen, increasing test coverage is a worthy goal.
We might start by looking at the regex test suite to see if we can import some
tests from there.
--
___
Python tracker rep
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
components: +Library (Lib)
nosy: +ezio.melotti
stage: - needs patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22824
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
stage: - needs patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22823
Ezio Melotti added the comment:
Can you provide a sample DNA sequence (or part of it), the exact code you used,
the output you got, and what you expected?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22817
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22806
___
___
Python-bugs
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
resolution: - not a bug
stage: - resolved
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22786
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
keywords: +easy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22680
___
___
Python-bugs-list
Ezio Melotti added the comment:
James, could you check again with a recent Python and see if the #11798 fix
makes things any better?
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22293
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
keywords: +easy
nosy: +bethard
stage: - needs patch
type: - enhancement
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22317
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22335
___
___
Python-bugs
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
stage: - resolved
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16662
___
___
Python-bugs-list
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
stage: - needs patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22344
Ezio Melotti added the comment:
Possible ways to highlite is to have a light grey:
--
» (at the beginning of the tab)
FWIW the latter (») is what I usually see used, with a lighter color to
distinguish it from regular text.
3. Should tab space in comments and strings be shaded? I think
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +pitrou, yselivanov
stage: - needs patch
type: behavior - enhancement
versions: +Python 3.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22357
Ezio Melotti added the comment:
Patch LGTM.
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22388
___
___
Python-bugs-list
401 - 500 of 5772 matches
Mail list logo