Changes by Ezio Melotti :
--
nosy: -BreamoreBoy
versions: +Python 3.3 -Python 3.1
___
Python tracker
<http://bugs.python.org/issue1047397>
___
___
Python-bug
Changes by Ezio Melotti :
--
versions: -Python 2.6
___
Python tracker
<http://bugs.python.org/issue7267>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ezio Melotti :
--
nosy: +ezio.melotti
stage: needs patch -> patch review
versions: +Python 3.3 -Python 3.1
___
Python tracker
<http://bugs.python.org/iss
Changes by Ezio Melotti :
--
keywords: +easy
stage: -> needs patch
versions: +Python 2.7, Python 3.3 -Python 3.1
___
Python tracker
<http://bugs.python.org/issu
Changes by Ezio Melotti :
--
stage: needs patch -> patch review
versions: +Python 3.3
___
Python tracker
<http://bugs.python.org/issue7695>
___
___
Python-
Changes by Ezio Melotti :
--
keywords: +easy
stage: -> needs patch
___
Python tracker
<http://bugs.python.org/issue13424>
___
___
Python-bugs-list mai
Changes by Ezio Melotti :
--
nosy: +eli.bendersky, eric.araujo, terry.reedy
___
Python tracker
<http://bugs.python.org/issue12907>
___
___
Python-bugs-list mailin
Changes by Ezio Melotti :
--
nosy: +eli.bendersky, eric.araujo, ezio.melotti, terry.reedy
___
Python tracker
<http://bugs.python.org/issue12908>
___
___
Python-bug
Changes by Ezio Melotti :
--
nosy: +ezio.melotti
___
Python tracker
<http://bugs.python.org/issue12907>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ezio Melotti :
--
versions: +Python 3.3
___
Python tracker
<http://bugs.python.org/issue6733>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ezio Melotti :
--
versions: +Python 3.3 -Python 3.2
___
Python tracker
<http://bugs.python.org/issue2527>
___
___
Python-bugs-list mailing list
Unsub
Ezio Melotti added the comment:
A test?
--
stage: -> test needed
type: -> behavior
___
Python tracker
<http://bugs.python.org/issue12890>
___
___
Pyth
Changes by Ezio Melotti :
--
stage: test needed -> patch review
___
Python tracker
<http://bugs.python.org/issue12890>
___
___
Python-bugs-list mailing list
Un
Changes by Ezio Melotti :
--
assignee: docs@python -> ezio.melotti
nosy: +georg.brandl
stage: -> needs patch
___
Python tracker
<http://bugs.python.org/i
Changes by Ezio Melotti :
--
stage: -> committed/rejected
versions: -Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.4
___
Python tracker
<http://bugs.python.org/issu
Ezio Melotti added the comment:
Is "To check for the exact type, use :func:`assertIs(type(obj), cls)
`." better?
I think the problem this solves is clear enough even without mentioning
sub/superclasses.
--
___
Python trac
Changes by Ezio Melotti :
--
nosy: +ezio.melotti
___
Python tracker
<http://bugs.python.org/issue13437>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ezio Melotti :
--
nosy: +loewis
___
Python tracker
<http://bugs.python.org/issue13438>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ezio Melotti added the comment:
There are usually two cases that lead me to check the code:
1) The documentation is incomplete, not clear, missing, or plain wrong;
2) I want to check how something is implemented, mostly just out of curiosity;
Regarding the first case, in theory the docs should
Changes by Ezio Melotti :
--
keywords: +easy
nosy: +ezio.melotti
stage: -> needs patch
___
Python tracker
<http://bugs.python.org/issue13443>
___
___
Python-
Ezio Melotti added the comment:
> Is Python supposed to support characters outside U+-U+10 range?
No, they should be rejected. Allowing them in some specific places might cause
them to leak somewhere else and cause problems, so I'd rather stick with that
range and reject
Ezio Melotti added the comment:
It's not because of the security risk, but simply because the docs for 2.6 are
not rebuilt automatically anymore. So, even if we fix it on 2.6, no one will
see the change unless someone goes and triggers a full doc rebuild manually. A
missing comma i
Ezio Melotti added the comment:
+1
What you describe sounds all good to me, except that I would keep all tests in
the same dir (i.e. Tools/tests (or Tools/test?)) instead of having different
test dirs for each subdir (so test_pygettext.py would go in Tools/tests and not
in Tools/i18n/tests
Changes by Ezio Melotti :
--
nosy: +ezio.melotti
___
Python tracker
<http://bugs.python.org/issue12759>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ezio Melotti added the comment:
Thanks for the patch!
The patch should also include tests for this case in Lib/test/test_re.py
--
components: +Regular Expressions
stage: needs patch -> test needed
___
Python tracker
<http://bugs.pyth
Ezio Melotti added the comment:
Confirmed on py3k, it doesn't seem to happen with smaller values.
--
components: +Extension Modules
nosy: +ezio.melotti, rhettinger
stage: -> test needed
versions: +Python 3.3
___
Python tracke
New submission from Ezio Melotti :
The documentation about the bug tracker is sparse in a few different places.
The devguide contains 4 pages:
1. http://docs.python.org/devguide/helptriage.html
2. http://docs.python.org/devguide/devrole.html
3. http://docs.python.org/devguide/triaging.html
Changes by Ezio Melotti :
--
components: +Extension Modules
nosy: +belopolsky, lemburg
stage: -> test needed
versions: +Python 3.2, Python 3.3
___
Python tracker
<http://bugs.python.org/issu
Ezio Melotti added the comment:
> I think the reason these docs are scattered is that the devguide is a
> guide, not a reference manual. I don't think this patch makes sense: if
> the tracker really needed so much text to explain how it works, then
> the tracker would
Ezio Melotti added the comment:
> Well, it does hurt, because the more sentences you write, the more the
> devguide becomes bloated and difficult to follow
OTOH is easy to ignore an "how to register to the tracker" section if you are
already registered or if you don't ne
Ezio Melotti added the comment:
I agree with Antoine, there's no need to mention them in the quickstart.
Moreover these dependencies are optional, so there's no need to install them
unless they are specifically needed (on a related note I would also add an
"optional"
Changes by Ezio Melotti :
--
nosy: +ezio.melotti
versions: -Python 3.1
___
Python tracker
<http://bugs.python.org/issue10507>
___
___
Python-bugs-list mailin
Ezio Melotti added the comment:
I'd search the Jython devguide at http://www.jython.org/devguide/, having it at
http://docs.python.org/devguide/jython/ doesn't make much sense IMHO
(especially if it is a "full" guid
Changes by Ezio Melotti :
--
nosy: +ezio.melotti
stage: -> needs patch
___
Python tracker
<http://bugs.python.org/issue13474>
___
___
Python-bugs-list mai
Changes by Ezio Melotti :
--
nosy: +ezio.melotti
___
Python tracker
<http://bugs.python.org/issue13476>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ezio Melotti added the comment:
The feature request seems reasonable to me, but this can only go in 3.3.
If you want to propose a patch, you might want to check the devguide and what
other modules like zipfile do.
--
nosy: +ezio.melotti, lars.gustaebel
stage: -> test needed
t
Changes by Ezio Melotti :
--
stage: needs patch -> patch review
___
Python tracker
<http://bugs.python.org/issue11365>
___
___
Python-bugs-list mailing list
Un
Changes by Ezio Melotti :
--
versions: -Python 3.1
___
Python tracker
<http://bugs.python.org/issue4966>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ezio Melotti added the comment:
Can this be closed?
--
nosy: +ezio.melotti
status: open -> pending
___
Python tracker
<http://bugs.python.org/issue10811>
___
_
Ezio Melotti added the comment:
> I think about it in the reverse: You want a featurefull library, and
> disable some things (zlib, ssl, threads) only if you specifically
> don’t want them (if you’re a Twisted fan for example ).
I have a few arguments in favor of my position:
1) P
Ezio Melotti added the comment:
I see the note just after the sausage example and in the table at the top of
the page, from the link you provided.
--
nosy: +ezio.melotti
resolution: -> invalid
stage: -> committed/rejected
status: open -> closed
versions: -P
Ezio Melotti added the comment:
The convention is to put the note at the end of the section. For this specific
case the section about Counter is immediately followed by the documentation of
its methods, so it's indeed hard to notice. Maybe a different CSS would make
this more ev
Ezio Melotti added the comment:
+1
--
nosy: +ezio.melotti
stage: -> needs patch
___
Python tracker
<http://bugs.python.org/issue13494>
___
___
Python-bugs-lis
Changes by Ezio Melotti :
--
components: +Extension Modules -Library (Lib)
stage: -> test needed
versions: +Python 3.3 -Python 3.2
___
Python tracker
<http://bugs.python.org/iss
Changes by Ezio Melotti :
--
stage: -> needs patch
versions: +Python 2.7 -Python 2.6
___
Python tracker
<http://bugs.python.org/issue6766>
___
___
Python-
Changes by Ezio Melotti :
--
nosy: +benjamin.peterson
stage: -> test needed
type: -> behavior
versions: +Python 3.3
___
Python tracker
<http://bugs.python.org/i
Changes by Ezio Melotti :
--
nosy: -BreamoreBoy
versions: +Python 3.3 -Python 3.1
___
Python tracker
<http://bugs.python.org/issue6167>
___
___
Python-bugs-list m
Changes by Ezio Melotti :
--
assignee: -> ezio.melotti
___
Python tracker
<http://bugs.python.org/issue3>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Ezio Melotti :
--
keywords: +easy
nosy: +petri.lehtinen
stage: -> patch review
versions: +Python 3.3 -Python 3.1
___
Python tracker
<http://bugs.python.org/issu
Changes by Ezio Melotti :
--
keywords: +easy
versions: +Python 3.2, Python 3.3 -Python 2.6, Python 3.0, Python 3.1
___
Python tracker
<http://bugs.python.org/issue5
Changes by Ezio Melotti :
--
nosy: +mrabarnett
___
Python tracker
<http://bugs.python.org/issue3665>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ezio Melotti :
--
stage: -> patch review
versions: -Python 3.1
___
Python tracker
<http://bugs.python.org/issue10052>
___
___
Python-bugs-list mai
Changes by Ezio Melotti :
--
nosy: +ncoghlan
versions: +Python 3.3 -Python 3.1
___
Python tracker
<http://bugs.python.org/issue7238>
___
___
Python-bugs-list m
Changes by Ezio Melotti :
--
versions: -Python 3.1
___
Python tracker
<http://bugs.python.org/issue8065>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ezio Melotti :
--
components: +Library (Lib)
stage: -> needs patch
___
Python tracker
<http://bugs.python.org/issue12790>
___
___
Python-bugs-lis
Changes by Ezio Melotti :
--
stage: needs patch -> patch review
___
Python tracker
<http://bugs.python.org/issue12919>
___
___
Python-bugs-list mailing list
Un
Changes by Ezio Melotti :
--
nosy: -BreamoreBoy
stage: -> needs patch
versions: +Python 2.7, Python 3.3
___
Python tracker
<http://bugs.python.org/issue1
Ezio Melotti added the comment:
Is this still an issue?
--
nosy: +ezio.melotti
___
Python tracker
<http://bugs.python.org/issue6753>
___
___
Python-bugs-list m
Changes by Ezio Melotti :
--
stage: -> needs patch
type: -> feature request
versions: +Python 3.3 -Python 2.7
___
Python tracker
<http://bugs.python.org/
Changes by Ezio Melotti :
--
versions: +Python 3.3 -Python 3.1
___
Python tracker
<http://bugs.python.org/issue7074>
___
___
Python-bugs-list mailing list
Unsub
Changes by Ezio Melotti :
--
stage: -> patch review
type: -> behavior
___
Python tracker
<http://bugs.python.org/issue6899>
___
___
Python-bugs-list
Changes by Ezio Melotti :
--
stage: -> needs patch
___
Python tracker
<http://bugs.python.org/issue11374>
___
___
Python-bugs-list mailing list
Unsubscri
Ezio Melotti added the comment:
I'll change this in a doc issue then.
Any suggestions about the wording?
Adding "Passing unicode strings is suggested/advised/preferred." in the .feed()
section is a bit vague, and mentioning the problem (with str it might break in
some corn
Ezio Melotti added the comment:
http://www.w3.org/TR/html5/named-character-references.html lists 2152 HTML 5
entities (see also attached file for a dict generated from that table).
Currently html.entities only has 252 entities, organized in 3 dicts:
1) name -> intvalue (e.g. 'amp&
Ezio Melotti added the comment:
Usually we don't talk about performance in the doc, and in my personal
experience I didn't notice any major difference between the different
implementations (but than again I haven't used them much).
Talking about the other implementations and t
Ezio Melotti added the comment:
> Seriously, minidom is widely known for being extremely slow and
> extremely memory hungry. And that is backed by basically any benchmark
> that has ever been done on the subject.
Do you have any link?
My point is that if you say thing like "
Changes by Ezio Melotti :
--
nosy: +eric.araujo, ezio.melotti
stage: -> needs patch
versions: +Python 2.7, Python 3.2, Python 3.3
___
Python tracker
<http://bugs.python.org/issu
Ezio Melotti added the comment:
FWIW I've seen several persons using "for line in file.readlines(): ..." or
even "while 1: line = file.readline()". IMHO it's a good idea to document that
"without sizehint, it's equivalent to list(file)" and that
Ezio Melotti added the comment:
You should report this to the PIL bug tracker. PIL is not part of the Python
standard library.
--
nosy: +ezio.melotti
resolution: -> invalid
stage: -> committed/rejected
status: open -> closed
___
Pytho
Ezio Melotti added the comment:
You could try submitting your patch to the image-sig ML
(http://mail.python.org/mailman/listinfo/image-sig).
--
___
Python tracker
<http://bugs.python.org/issue13
Ezio Melotti added the comment:
Grouping the common warnings in a "Security Considerations" section sounds OK,
but the warnings should still be visible IMHO.
In my experience, people:
1) jump right to the doc for the function they are using;
2) read the example and try to figure
Ezio Melotti added the comment:
I think we are mixing a few different things here:
1) the content of the warning(s);
2) the position of the warning(s);
3) the style of the warning(s);
Duplicating the same content in each warning is bad, so a specific section that
summarizes the problem is
Ezio Melotti added the comment:
corenova, can you try what Martin said?
--
nosy: +ezio.melotti
status: open -> pending
___
Python tracker
<http://bugs.python.org/issu
Ezio Melotti added the comment:
Committed, thanks for the patch!
I preferred to add a separate test, because only the tests with "assert False"
need to be skipped with -O, the other can run with and without -O.
--
assignee: -> ezio.melotti
resolution: -> fixed
sta
Changes by Ezio Melotti :
--
components: +Library (Lib)
stage: -> patch review
type: -> feature request
___
Python tracker
<http://bugs.python.org/i
Changes by Ezio Melotti :
--
keywords: +easy
stage: -> needs patch
versions: +Python 2.7, Python 3.2, Python 3.3 -Python 2.6, Python 3.1
___
Python tracker
<http://bugs.python.org/issu
Changes by Ezio Melotti :
--
components: +Extension Modules
stage: -> patch review
type: -> feature request
___
Python tracker
<http://bugs.python.org/i
Ezio Melotti added the comment:
Would it be ok to state that:
1) <, >, ==, >=, <=, and != compare the values of two objects;
2) the two objects don't necessarily have to be of the same type;
3) with == and !=, objects of different types compare unequal, unless they
define a sp
Ezio Melotti added the comment:
LGTM.
--
assignee: docs@python -> eric.araujo
nosy: +ezio.melotti
stage: patch review -> commit review
___
Python tracker
<http://bugs.python.org/i
Changes by Ezio Melotti :
--
stage: -> patch review
___
Python tracker
<http://bugs.python.org/issue9420>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Ezio Melotti :
--
stage: -> needs patch
type: -> behavior
versions: +Python 2.7 -Python 3.2, Python 3.3
___
Python tracker
<http://bugs.python.org/i
Changes by Ezio Melotti :
--
nosy: -BreamoreBoy
versions: +Python 3.3
___
Python tracker
<http://bugs.python.org/issue2651>
___
___
Python-bugs-list mailin
Ezio Melotti added the comment:
+1
--
nosy: +ezio.melotti
stage: patch review -> commit review
___
Python tracker
<http://bugs.python.org/issue13513>
___
_
Ezio Melotti added the comment:
Done!
--
assignee: docs@python -> ezio.melotti
nosy: +ezio.melotti
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python
Ezio Melotti added the comment:
Fixed!
@Eli
At least in the doc, I haven't seen any other suspicious use of 'cast'.
--
assignee: docs@python -> ezio.melotti
resolution: -> fixed
stage: needs patch -> committed/rejecte
Ezio Melotti added the comment:
Python doesn't require the .py to run the code if there's a .pyc. This is
expected so there's no need to give a warning.
If the .py is present but it's a symlink pointing nowhere, it might make sense
to give a warning before falling back
Changes by Ezio Melotti :
--
nosy: +ezio.melotti
stage: -> needs patch
versions: +Python 2.7, Python 3.3
___
Python tracker
<http://bugs.python.org/issu
Ezio Melotti added the comment:
Attached a patch to make the CSS used for warnings and notes less evident by
removing the red/gray background color.
--
keywords: +patch
Added file: http://bugs.python.org/file23842/issue13515.diff
___
Python tracker
Changes by Ezio Melotti :
Added file: http://bugs.python.org/file23843/warnnew.png
___
Python tracker
<http://bugs.python.org/issue13515>
___
___
Python-bugs-list mailin
Changes by Ezio Melotti :
Added file: http://bugs.python.org/file23844/warnold.png
___
Python tracker
<http://bugs.python.org/issue13515>
___
___
Python-bugs-list mailin
Ezio Melotti added the comment:
This section has been removed from the 3.x docs in 3828f81a64e7 and
2aeef275bec8, but it's still there in 2.7.
--
nosy: +pitrou
___
Python tracker
<http://bugs.python.org/is
Ezio Melotti added the comment:
Sure, do you want to propose a patch? (You can see the devguide for more
information.)
--
keywords: +easy
nosy: +ezio.melotti
stage: -> test needed
versions: +Python 3.2, Python 3.3
___
Python tracker
&l
Changes by Ezio Melotti :
--
nosy: +jnoller
stage: -> needs patch
versions: -Python 2.6, Python 3.1, Python 3.4
___
Python tracker
<http://bugs.python.org/issu
Ezio Melotti added the comment:
I think the patch includes too many changes. It would be better if you can
split it in two separate patches: one with the increased coverage, the other
with the bugs you found and their tests.
I can easily commit the first (assuming it doesn't break the
Changes by Ezio Melotti :
--
assignee: -> ezio.melotti
stage: test needed -> commit review
___
Python tracker
<http://bugs.python.org/issue13531>
___
___
Ezio Melotti added the comment:
Committed, thanks for the report and the patch!
For the record, this is related to https://bugs.pypy.org/issue953
--
resolution: -> fixed
stage: commit review -> committed/rejected
status: open -> closed
_
Ezio Melotti added the comment:
This section could be clearer imho.
First of all there's nothing special about "nested" list comprehensions. In
[expr for elem in seq], expr might be any expression -- including a listcomp.
As with any other expression, the nested listcomp w
Changes by Ezio Melotti :
--
assignee: docs@python -> ezio.melotti
keywords: +patch
nosy: +eric.araujo, terry.reedy
stage: needs patch -> commit review
Added file: http://bugs.python.org/file23882/issue13549.diff
___
Python tracker
Ezio Melotti added the comment:
> - I’d recommend a few whitespace beautifications,
> like in ``for x in [1,2,3]`` and ``range(1,6)``.
Leaving the space out in [1,2,3] makes the expression a bit more readable IMHO*.
> I think there is an example that makes that line more
> un
Changes by Ezio Melotti :
Added file: http://bugs.python.org/file23885/issue13549-2.diff
___
Python tracker
<http://bugs.python.org/issue13549>
___
___
Python-bugs-list m
401 - 500 of 5818 matches
Mail list logo