Changes by Facundo Batista facu...@taniquetil.com.ar:
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23887
Facundo Batista added the comment:
Hi Berker, I like your patch, will apply it after doing a test for it.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23887
New submission from Facundo Batista:
I normally print(repr()) the exception I got, for debugging purposes. I use
repr() because for builtin exceptions, str() will print only the message, and
not the exception type.
But for HTTPError, the repr() of it is HTTPError(), without further
Changes by Facundo Batista <facu...@taniquetil.com.ar>:
--
nosy: -facundobatista
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Facundo Batista added the comment:
It looked ok to me (I couldn't try it, as I still have 4.4 kernel).
One thing to the be done is to improve the test coverage (trying the usage of
all the parameters, at least).
--
nosy: +facundobatista
___
Python
Changes by Facundo Batista <facu...@taniquetil.com.ar>:
--
versions: +Python 3.5
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Facundo Batista added the comment:
I think the fix nails it; all the problem was that the "fast" mode was wrongly
detected, and all the problems (counting badly, or a bad repr, etc) is a
problem after setting cnt into PY_SSIZE_T_MAX.
IIUC there is nothing special to do when step=1.0
New submission from Facundo Batista:
So, you could do:
exc = self.assertRaises(ValueError, somefunc, someargs)
And then, explore "exc" as will.
Yes, you can get the exception if you use assertRaises as a context manager,
but that leads to more cumbersome code:
with self.as
New submission from Facundo Batista:
Right now:
>>> Formatter().parse("mira como bebebn los peces en el {rio} {de} {la} plata")
>>> next(_)
('mira como bebebn los peces en el ', 'rio', '', None)
This returned tuple should be a namedtuple, so it's self-exp
Facundo Batista <facu...@taniquetil.com.ar> added the comment:
I have this failure on my machine too (Ubuntu 17.04, kernel 4.10.0-37-generic).
Installing `libgdbm-dev` and running configure with
`--with-dbmliborder=gdbm:bdb` didn't help.
--
nosy: +facundob
New submission from Facundo Batista <facu...@taniquetil.com.ar>:
Sometimes it's nice to do extra checks on the error raised and captured by
self.assertRaises call.
Yes, the same can be achieved using assertRaises as a context manager and then
accessing the `exception` attribute in the c
Change by Facundo Batista <facu...@taniquetil.com.ar>:
--
nosy: -facundobatista
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python
New submission from Facundo Batista <facu...@taniquetil.com.ar>:
This works fine:
>>> "{[0]}".format([1, 2, 3])
'1'
This should work too:
>>> "{[-1]}".format([1, 2, 3])
Traceback (most recent call last):
File "", line 1, in
TypeE
Facundo Batista added the comment:
I understand (and agree with) the merits of automatically converting the int to
str when dumping to a string.
However, this result really surprised me:
>>> json.dumps({1:2, "1":3})
'{"1": 2, "1": 3}'
Is it a valid
New submission from Facundo Batista :
When using pdb to debug, the traceback is off by one line.
For example, this simple script:
```
print("line 1")
import pdb;pdb.set_trace()
print("line 2")
print("line 3", broken)
print("line 4")
```
...when run
Facundo Batista added the comment:
This is a duplicate of https://bugs.python.org/issue16482 -- closing it.
--
resolution: -> duplicate
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Facundo Batista added the comment:
It's a theoretical issue, I didn't hit it myself.
--
___
Python tracker
<https://bugs.python.org/issue40153>
___
___
Pytho
New submission from Facundo Batista :
As stated in docs [0], JSON structures must not have duplicated keys.
>>> json.dumps({1:2, "1":3})
'{"1": 2, "1": 3}'
This is related to https://bugs.python.org/issue34972 .
[0] "The RFC specifies that the
New submission from Facundo Batista :
This is mostly a confusion about 'r' being a synonym of 'rt', while it's more
explicit if we consider 'r' as one default, and 't' as other (as other parts of
the documentation do).
Doing `help(open)` we get:
mode is an optional string that specifies
New submission from Facundo Batista :
Documentation for Path.iterdir (
https://docs.python.org/3/library/pathlib.html#pathlib.Path.iterdir ) doesn't
specify what happens when the directory change.
This is important, as the function does NOT return a list (which would imply
that a "sna
Facundo Batista added the comment:
>From a "consumer" POV, it's totally useful to see that `__ne__` is part of
>what Set (and others) provides, even if it's implemented in the Set class
>itself or wherever.
So +1 to leave it like it's currently is.
--
no
Change by Facundo Batista :
--
nosy: -facundobatista
___
Python tracker
<https://bugs.python.org/issue37168>
___
___
Python-bugs-list mailing list
Unsubscribe:
Facundo Batista added the comment:
I'm closing this, it looks to me that behaviour changed and this is safe now.
--
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/i
Facundo Batista added the comment:
However, Serhiy, `os.listdir()` builds a list quickly and gives you that, so
the chance of the directory being modified is quite low (however, for big
directories, that may happen, and it's probably good to notice that in the
docs).
For `Path.iterdir
Change by Facundo Batista :
--
nosy: -facundobatista
___
Python tracker
<https://bugs.python.org/issue18417>
___
___
Python-bugs-list mailing list
Unsubscribe:
Facundo Batista added the comment:
The balance here is allow an invalid JSON to be created (but documenting that
on some situations that will happen), or sticking to always produce valid
JSONs, but with a hit in performance (which we don't know so far if it's big or
small
Facundo Batista added the comment:
Found this after seeing (once again) somebody asking for help in Python
Argentina after having a file mixing tabs and spaces.
This tends to catch new people.
I'm +1 to just raise an error if the file mixes tabs and spaces for
indentation. I've never seen
Facundo Batista added the comment:
It should behave as you say, yes.
I fixed the class HTTPErrorProcessor(BaseHandler) regarding this issue,
to not raise an error if response is 2xx (see rev 54927).
Regards,
--
nosy: +facundobatista
__
Tracker [EMAIL
Facundo Batista added the comment:
Done, rev 58207.
--
resolution: accepted - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1177
Facundo Batista added the comment:
Applied the patchs long_hash.patch (rev 58208) and decimal_hash_v2.patch
(rev 58211)
--
resolution: - fixed
status: open - closed
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1772851
Facundo Batista added the comment:
As stated in the docs...
http://docs.python.org/dev/reference/lexical_analysis.html#string-literals
r\ is not a valid string literal (even a raw string cannot
end in an odd number of backslashes). Specifically, a raw
string cannot end in a single
Facundo Batista added the comment:
Mark is ok, zero length responses are ok. But that has nothing to do
with self.length.
self.lenght reaching zero means that everything that needed to be read
is already read. If the read() method is called without an argument, it
reads everything until
Facundo Batista added the comment:
Fixed in rev 58530 (also added a test case)
--
resolution: - fixed
status: open - closed
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1580738
Facundo Batista added the comment:
Where this happens? In the documentation? In the PEP? Do you have the
URL where you found this?
--
nosy: +facundobatista
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1289
Facundo Batista added the comment:
Downloaded the testdata.txt file, and yes, it's UTF-8:
[EMAIL PROTECTED]:~/devel$ file testdata.txt
testdata.txt: UTF-8 Unicode text
But I opened it perfectly!
Python 2.5.1 (r251:54863, May 2 2007, 16:56:35)
[GCC 4.1.2 (Ubuntu 4.1.2-0ubuntu4)] on linux2
Facundo Batista added the comment:
Fixed in rev 58531.
--
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1289
__
___
Python
Facundo Batista added the comment:
You migrated only of Python version, or also of windows installation?
I checked Py25 and Py23 in my Win 2k, and in both I have the same behaviour:
C:\Python23python
Python 2.3.5 (#62, Feb 8 2005, 16:23:02) [MSC v.1200 32 bit (Intel)] on
win32
Type help
Changes by Facundo Batista:
--
assignee: - facundobatista
nosy: +facundobatista
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1755179
_
___
Python-bugs-list
Facundo Batista added the comment:
The idea is rejected, so I close the bug.
If wanted, push further discussion of this in the lists.
--
nosy: +facundobatista
status: open - closed
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue419903
Facundo Batista added the comment:
Added to the PEP 42, rev 58638.
--
nosy: +facundobatista
status: open - closed
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue588756
Changes by Facundo Batista:
Removed file: http://bugs.python.org/file8559/unnamed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1290
__
___
Python-bugs-list mailing list
Changes by Facundo Batista:
Removed file: http://bugs.python.org/file8560/unnamed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1290
__
___
Python-bugs-list mailing list
Facundo Batista added the comment:
CharacterData.__repr__ was constructing a string in response that keeped
having a non-ascii character.
Fixed in rev 58641.
--
resolution: works for me - fixed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org
Facundo Batista added the comment:
Really do not understand that assert. It says:
assert(size size * sizeof(Tcl_UniChar));
For that to be true, considering size to be positive, the result of
sizeof needs to be greater than 0.
If you modify it, and also accepts it to be 0, and considering
Facundo Batista added the comment:
The deadlock happens because strptime has an import inside it, and
recursive imports are not allowed in different threads.
As a general rule and good coding style, don't run your code when the
module is imported, but put it in a function like main
Facundo Batista added the comment:
import os.path
os.path.exists(con)
False
os.path.exists(nul)
False
os.path.exists(prn)
False
This is in Windows 2000 (5.00.2195) sp4, using *both* Python 2.3.5 and
2.5.1, no cygwin.
Personally, I'm +1 with Mark Hammond about this:
I agree
Facundo Batista added the comment:
The OP changed his mind, :)
--
nosy: +facundobatista
resolution: - invalid
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1361
Facundo Batista added the comment:
Only in win32, in Linux it behaves ok (I put a /tmp/w.py that prints 'w'):
Python 2.5.1 (r251:54863, May 2 2007, 16:56:35)
[GCC 4.1.2 (Ubuntu 4.1.2-0ubuntu4)] on linux2
Type help, copyright, credits or license for more information.
import sys
Facundo Batista added the comment:
I followed the link you provided. All the discussion there ends asking
for a realiable way to test the problem (otherwise, we could be making
more mistakes than solving the problem in the different platforms).
Please provide a test case, so we include
Facundo Batista added the comment:
I'm positive that this shouldn't happen. There should NOT be any
difference between longs and ints in nowadays Python, so you never
should say to an user to call that long() before the %d.
And, you have some strange behaviours... for example:
%d % 9e8
Facundo Batista added the comment:
I don't understand why after receiving a redirection, and going to a new
URL, you say to NOT send the POST data. Shouldn't the HTTP request be
exactly like the original one, but to another URL destination?
But you said that #2 solution was more RFC compliant
Facundo Batista added the comment:
So, for 302 error we should resend the request as POST (header with
lenght and data), and for the others we need to keep current behaviour.
Actually, we just need to code a new handling function for 302, and
leave the existing one as is.
What do you think
Facundo Batista added the comment:
Fixed in the trunk (rev 59053).
Thank you!
--
nosy: +facundobatista
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1463
Facundo Batista added the comment:
This is not a bug report, just a copied traceback.
For a useful bug, put what you did so we can reproduce it, what you get,
and what you think you should got.
Thanks!
--
nosy: +facundobatista
resolution: - rejected
status: open - closed
Facundo Batista added the comment:
On IDLE and Python with the same exact version, but in Windows, this
works ok.
Don't have IDLE in Linux to try it, though.
--
nosy: +facundobatista
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1486
Facundo Batista added the comment:
Rejected as requested by the OP.
--
resolution: - rejected
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1486
Facundo Batista added the comment:
This was fixed at the same time than issue 1772851.
int(D(1e1234567890987654321)) stills take too long, but this is fault
of doing 10**1234567890987654321 to convert it to an int.
Note that hash(D(1e1234567890987654321)) is fast now.
--
resolution
Facundo Batista added the comment:
Fixed in the trunk, rev 59195.
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1755179
_
___
Python-bugs-list mailing list
Unsubscribe
Facundo Batista added the comment:
But is ok to hide the problem?
I mean, there *is* an error: the operation is not permitted (even if
it's not Python fault), so why to not have the exception?
--
nosy: +facundobatista
__
Tracker [EMAIL PROTECTED]
http
Facundo Batista added the comment:
os.walk has an error handling mechanism because it goes through a
collection of files, so it's nice to have, for example, a function
applied if errors appear in some of those files.
As this operation is applicable only to one file, this is not useful at
all
Facundo Batista added the comment:
I'm -1 to the library ignore errors without specific indication from the
user, specially when it's so easy to do it in the calling code.
We agree that copytree could grow an option like the one in os.walk.
Feel free to open an issue for it (this discussion
Changes by Facundo Batista:
--
title: IDLE shell doesn\'t accept non ascii char input - IDLE shell doesn't
accept non ascii char input
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1542677
Facundo Batista added the comment:
Commited, rev 59297.
Thank you!
--
nosy: +facundobatista
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1547
__
___
Python-bugs-list
Changes by Facundo Batista:
--
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1547
__
___
Python-bugs-list mailing list
Facundo Batista added the comment:
There's no crash in 2.5.1 neither in the trunk.
As 2.3 or 2.4 won't be fixed, do you think that this bug can be closed?
Thanks!
--
nosy: +facundobatista
Tracker [EMAIL PROTECTED]
http://bugs.python.org
Facundo Batista added the comment:
2007/12/8, Adam Sampson [EMAIL PROTECTED]:
On Fri, Dec 07, 2007 at 08:07:38PM -, Facundo Batista wrote:
There's no crash in 2.5.1 neither in the trunk.
As 2.3 or 2.4 won't be fixed, do you think that this bug can be closed?
Yep, go
Facundo Batista added the comment:
I have another way:
* Check if the destination is a directory, and in such case make an
os.path.join(destination, originfile), and then use os.rename() with
this new destination.
What do you think? Do you think this way suffers from any multiplatform
issue
Facundo Batista added the comment:
Do you think that can came up with a patch for this?
Just the paragraphs better written, or a better example, that would be
great!
Thanks!
--
nosy: +facundobatista
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org
Facundo Batista added the comment:
What happens if you do NOT change the library path in front of it?
--
nosy: +facundobatista
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1610
Changes by Facundo Batista:
--
assignee: - facundobatista
nosy: +facundobatista
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1501
__
___
Python-bugs-list mailing
Facundo Batista added the comment:
The PEP is not approved yet. This look interesting, will take a look
again in the future after the PEP approval.
Thanks for the work!
Regards,
--
resolution: - postponed
status: open - pending
__
Tracker [EMAIL
Facundo Batista added the comment:
I'm +1 to this change.
As this does not negatively affect the behavior on Py2, for each part of
the patch I propose:
- decimal.py: incorporate them to the trunk
- numbers.py: of course, in Py3
- test_decimal.py: incorporate this tests, activating them
Facundo Batista added the comment:
This is not a bug, just a comment of a code you did.
If you think that there's actually a problem in HTMLParser.py, tell us
what you do, what you get, and what you expect to get.
When submitting changes, it's very useful to send the diff only, as in a
patch
Changes by Facundo Batista:
--
assignee: - facundobatista
nosy: +facundobatista
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1680
__
___
Python-bugs-list mailing
Facundo Batista added the comment:
The patch applies cleanly, all test cases are ok.
To be commited, documentation should be created for this, would you
please take care of it?
Also, some lines for NEWS will be welcomed.
Thank you!!
--
nosy: +facundobatista
Facundo Batista added the comment:
Couldn't apply cleanly the patch, as it appears to be a diff in other
format.
Anyway, applied it by hand, and now I attach the correct svn diff.
The test cases run ok with this change, and the problem is solved.
Regarding the delay introduced, I tested
Facundo Batista added the comment:
A lot of water passed through httplib.py. A lot of people made
corrections from Python versions 2.2 and 2.3.
Even me. I added timeout to it. And fixed recently (r58530) a problem
that could generate the second exception.
But how can check if this is solved
Facundo Batista added the comment:
Mmm... I thought this would be a clean backport... but no.
If we just copy the files to 2.5, we get two failures running the tests.
- test_hash_method (DecimalUsabilityTest): This is because of the
changes we made to the hash builtin in the trunk, and we
Facundo Batista added the comment:
Backported, commited in r59823.
--
resolution: - fixed
status: open - closed
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1755179
Facundo Batista added the comment:
Fixed in r59852.
--
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1757
__
___
Python-bugs
Facundo Batista added the comment:
As re provides regular expression matching operations similar to those
found in Perl, I tried there to see what happens:
use Data::Dumper;
$a = 'a\nb\nc';
$a =~ s/$/#/;
print Dumper($a);
$a = 'a\nb\n';
$a =~ s/$/#/;
print Dumper($a);
$ perl pru_sub.pl
Facundo Batista added the comment:
Decimal was backported to Py2.5, commited in r59859.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1182
__
___
Python-bugs-list mailing list
Changes by Facundo Batista:
--
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1182
__
___
Python-bugs-list mailing list
Facundo Batista added the comment:
Fix it, please.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1182
__
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org
Changes by Facundo Batista:
--
assignee: - facundobatista
nosy: +facundobatista
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1774
__
___
Python-bugs-list mailing
Facundo Batista added the comment:
Tried it on Linux, but the behaviour is the same on Py2.5.
It was already fixed in the trunk (it returns , as in the inbound read).
Thanks for the report!
--
resolution: - out of date
status: open - closed
Facundo Batista added the comment:
Retried it in a platform where I trust timing, and it proved ok.
So, problem solved, no performance impact, all tests pass ok. Commited
in r59862.
Thank you all!
--
resolution: - fixed
status: open - closed
Facundo Batista added the comment:
It was ok in the trunk docs. Fixed it in the 2.5 maint branch.
Thanks for the report!
--
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1774
Facundo Batista added the comment:
The PEP 239 is Rejected (http://www.python.org/dev/peps/pep-0239/).
If a Rational data type would be included in the stdlib, my
recommendation is that first that PEP would be reopened and pushed until
get accepted.
Also, note the kind of questions Mark
Facundo Batista added the comment:
2008/1/9, Raymond Hettinger said:
* Consider adding Decimal.from_rational and Rational.from_decimal. I
believe these are both easy and can be done losslessly.
If it's lossless, why not just allow Decimal(Rational(...)) and
Rational(Decimal
Facundo Batista added the comment:
I think that the Spec disallows additional whitespace to not allow, for
example, 2. 34 as 2.34, or 10 e-12.
I don't see any harm in having 2.34 or 5.73\n as good input
values, as long we remove those characters at both ends.
I propose to just make a .strip
Facundo Batista added the comment:
Already fixed in the trunk and 2.5 maintenance branch.
--
nosy: +facundobatista
resolution: - out of date
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1788
Facundo Batista added the comment:
Mark Dickinson:
The other option that maintains full compliance with the
specification is to do what we like with Decimal.__new__
(e.g. allowing leading and trailing whitespace), but
make sure that there's a fully conforming to-number
elsewhere
Facundo Batista added the comment:
Why not just double the size? The doubling + 1024 address some
specific issue? If so, it should be commented.
Also, do you have an example of a marshal.dumps() that suffers from this
issue?
Thank you!
--
nosy: +facundobatista
Facundo Batista added the comment:
Already fixed in trunk and 2.5 branch.
--
nosy: +facundobatista
resolution: - out of date
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1791
Changes by Facundo Batista:
--
nosy: +facundobatista
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1819
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Facundo Batista added the comment:
Yes, something was bad with my test. Now I have the same behaviour.
Sorry for the noise.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1863
Facundo Batista added the comment:
Don't follow you:
class C:
a = 42
list(a for _ in 'x')
Works here! (Python 2.5.1 on win32)
--
nosy: +facundobatista
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1863
Facundo Batista added the comment:
No news after two years and a half. Considering the arguments of Raymond
after S. Kochen brought the issue back up, I'd close the patch as rejected.
Feel free to bring this issue to python-dev, and if there's real need,
we can always open the patch back.
Fred
Facundo Batista added the comment:
If those two are obsolete, we may add a DeprecationWarning in 2.6 and
hide/remove them in 2.7.
What do you think?
--
nosy: +facundobatista
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue616247
1 - 100 of 349 matches
Mail list logo
