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
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.
Change by Facundo Batista :
--
nosy: -facundobatista
___
Python tracker
<https://bugs.python.org/issue18417>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Facundo Batista :
--
nosy: -facundobatista
___
Python tracker
<https://bugs.python.org/issue37168>
___
___
Python-bugs-list mailing list
Unsubscribe:
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.it
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.
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
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 &quo
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:
Facundo Batista added the comment:
It's a theoretical issue, I didn't hit it myself.
--
___
Python tracker
<https://bugs.python.org/issue40153>
___
___
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 specifie
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 i
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
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
New submission from Facundo Batista :
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
TypeError: list indices must be int
Change by Facundo Batista :
--
nosy: -facundobatista
___
Python tracker
<https://bugs.python.org/issue26680>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Facundo Batista :
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 context manager, but it look
Facundo Batista 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: +facundobatista
___
P
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 namedtup
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
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
Changes by Facundo Batista :
--
versions: +Python 3.5
___
Python tracker
<http://bugs.python.org/issue28019>
___
___
Python-bugs-list mailing list
Unsubscribe:
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
___
P
Changes by Facundo Batista :
--
nosy: -facundobatista
___
Python tracker
<http://bugs.python.org/issue24974>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Facundo Batista :
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue23887>
___
___
Python-bugs-list
Facundo Batista added the comment:
Hi Berker, I like your patch, will apply it after doing a test for it.
--
___
Python tracker
<http://bugs.python.org/issue23
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()", witho
Facundo Batista added the comment:
El 24/07/14 a las 15:01, Tim Peters escibió:
> "datetime.date() should accept a datetime.datetime as init
> parameter"
>
> instead? That's what the example appears to be getting at.
>
> If so, -1. Datetime objects a
Changes by Facundo Batista :
--
title: datetime.datetime() should accept a datetime.date as constructor ->
datetime.datetime() should accept a datetime.date as init parameter
___
Python tracker
<http://bugs.python.org/issu
New submission from Facundo Batista:
Currently (tested on py3.4):
>>> from datetime import datetime, date
>>> d = datetime.now()
>>> date(d)
Traceback (most recent call last):
File "", line 1, in
TypeError: an integer is required (got type datetime.date
Changes by Facundo Batista :
--
stage: resolved -> patch review
versions: +Python 3.4 -Python 3.3
___
Python tracker
<http://bugs.python.org/issue13866>
___
_
Facundo Batista added the comment:
Jesús, Amaury:
What if pickle would assign a random unique name to the lambda (like, an UUID)
so it can be pickled and unpickled?
--
___
Python tracker
<http://bugs.python.org/issue19
Facundo Batista added the comment:
Ethan, lambda functions are included in "functions defined at the top level of
a module".
Probably we should note there something like "except lambdas, because function
pickling is by na
New submission from Facundo Batista:
This is ok:
Python 3.4.0a3+ (default:86af5991c809, Oct 13 2013, 16:42:52)
...
>>> import pickle
>>> def f():
... pass
...
>>> pickle.dumps(f)
b'\x80\x03c__main__\nf\nq\x00.'
However, whe
New submission from Facundo Batista:
In the doc it says:
"""
Assigning a new value to instances of the pointer types c_char_p, c_wchar_p,
and c_void_p changes the memory location they point to, not the contents of the
memory block [...].
>>> s = "Hello,
Changes by Facundo Batista :
--
nosy: -facundobatista
___
Python tracker
<http://bugs.python.org/issue10897>
___
___
Python-bugs-list mailing list
Unsubscribe:
Facundo Batista added the comment:
Antoine, to see if I understood correctly... if we build the dict, and just
return it but don't save it in the frame, this leak would be solved? (yes, it'd
be slower because everytime it's asked, it'd ne
Facundo Batista added the comment:
Making a copy of f_locals values to return a dictionary that doesn't hold
references to the locals of the frame is not that simple (for me, at least):
- shallow copy: we'll return always a new dict, with the values being a copy of
locals; this
Changes by Facundo Batista :
--
assignee: facundobatista ->
___
Python tracker
<http://bugs.python.org/issue7221>
___
___
Python-bugs-list mailing list
Un
Facundo Batista added the comment:
Senthil, I'm assigning this issue to you because you know more about this
subject than me. Feel free to unassign if will not be working in it.
Thanks!
--
assignee: facundobatista -> orsenthil
___
Python
Changes by Facundo Batista :
--
assignee: facundobatista ->
___
Python tracker
<http://bugs.python.org/issue5340>
___
___
Python-bugs-list mailing list
Un
Changes by Facundo Batista :
--
versions: -Python 2.5.3
___
Python tracker
<http://bugs.python.org/issue1545463>
___
___
Python-bugs-list mailing list
Unsub
Facundo Batista added the comment:
I'm ok with the proposed changes from Sidnei (yes, a patch is needed).
--
___
Python tracker
<http://bugs.python.org/i
Facundo Batista added the comment:
Juanjo, ping me in private if you want help with the doc toolchain, I can show
you how to touch the .rst and see the changes after processing.
--
___
Python tracker
<http://bugs.python.org/issue7
Changes by Facundo Batista :
--
nosy: +facundobatista
___
Python tracker
<http://bugs.python.org/issue5911>
___
___
Python-bugs-list mailing list
Unsubscribe:
Facundo Batista added the comment:
I like this. I'd love to see a test of this, though.
Pablo, do you think you could came up with a test? Thanks!
--
___
Python tracker
<http://bugs.python.org/i
Facundo Batista added the comment:
Issue 1: +1 to raise ValueError
Issue 3: -0 to change actual behaviour
Thanks!
--
___
Python tracker
<http://bugs.python.org/issue6
Facundo Batista added the comment:
Applied the patch (slightly modified) to trunk (2.7), 2.6, and 3k branches.
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/
New submission from Facundo Batista :
If something bad happens between a os.pipe() call is called, and the
returned file descriptors are closed, those file descriptors are never
closed.
In a long lived process this is a problem.
Patch (against trunk) to solve this is attached
Facundo Batista added the comment:
Hans, please take a look to my comment 79573 in this same bug. If you
could do that, it'd be amazing...
Thank you!
--
___
Python tracker
<http://bugs.python.org/issu
Facundo Batista added the comment:
CGI tests shouldn't be run as root, it seems, as it breaks the inherent
protection.
--
nosy: +facundobatista
resolution: -> invalid
status: open -> closed
___
Python tracker
<http://bugs.python
Facundo Batista added the comment:
When fixing this, note that the builtin name "list" should not be
overwritten by the argument name.
--
message_count: 1.0 -> 2.0
nosy: +facundobatista
nosy_count: 1.0 -> 2.0
___
Pytho
Facundo Batista added the comment:
Removed the messages in decimal.py (r.69674).
___
Python tracker
<http://bugs.python.org/issue3676>
___
___
Python-bugs-list mailin
Facundo Batista added the comment:
Raymond, Mark, thanks for this work!
I'd include the following in the PEP (under the "from float"
discussion), what do you think?
"""
Update: The .from_float() method was added to Python 2.7 and 3.1
versions, providing loss
Facundo Batista added the comment:
Senthil, do you think you could provide a test case for this?
Thank you!
--
assignee: -> facundobatista
nosy: +facundobatista
___
Python tracker
<http://bugs.python.org/iss
Facundo Batista added the comment:
Yes, _buffer is not longer global.
Thanks for the report!
--
nosy: +facundobatista
resolution: -> out of date
status: open -> closed
___
Python tracker
<http://bugs.python.org/
Facundo Batista added the comment:
Everything looks ok, with one detail, the new set_tunnel() function.
Should this function be public? If yes, new documentation should be
added. If not, it should start with "_".
I think that it should be public, because we're using it from
Facundo Batista added the comment:
Bill, should this issue be closed?
Or Senthil found a bug in the actual code and you're waiting for him to
point out where is the problem or a way to reproduce it?
--
nosy: +facundobatista
___
Python tr
Changes by Facundo Batista :
--
nosy: +facundobatista
___
Python tracker
<http://bugs.python.org/issue4753>
___
___
Python-bugs-list mailing list
Unsubscribe:
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Commited in trunk and Py3, thanks Mark!
Please, could you commit it in 2.5? The only change I've made in the
patch is adding the issue number to Misc/NEWS, the rest is ok.
After that, just close this.
Thanks again!
Facundo Batista <[EMAIL PROTECTED]> added the comment:
2008/10/9 Raymond Hettinger <[EMAIL PROTECTED]>:
> Alternatively, we could decide to allow decimal/float
> comparisons -- the float can be converted to a decimal
> exactly and compared exactly -- it would be slow but
Facundo Batista <[EMAIL PROTECTED]> added the comment:
(Ok, remember that I'm not a "numeric" guy before start hitting me, :p )
I think that if we have Decimal(1)==1, and 1==1.0, to have Decimal(1)==1.0.
We always rejected comparison with "unsupported types",
Changes by Facundo Batista <[EMAIL PROTECTED]>:
--
nosy: +facundobatista
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1028088>
___
_
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Let me reopen this, I think we have an issue with this fix.
The conclusion of this discussion so far is that in 3.0 the crc32 will
behave like the standard, which is a good thing (tm), but in 2.6 it will
not: it should return a
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Nick said:
> So I would suggest either a new directory in the sandbox, or
> re-using Facundo's original directory (which includes the
> telco benchmark)
+1
> And I agree that it is far more sensible to target 2
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Giampaolo, should we close this one as duplicate of 3818 (that you
created one minute later)?
--
nosy: +facundobatista
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Fixed in r66326. Thank you!
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Facundo Batista <[EMAIL PROTECTED]> added the comment:
My fault, I'm exercising functions that have to raise a deprecation
warning... should I remove these tests?
Thank you!
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Dumb error, it was even only in 2.6, 3.0 was ok.
Thanks for noticing it, I fixed it and added tests for both versions.
Thank you again!!
--
nosy: +facundobatista
resolution: -> fixed
status: open
Facundo Batista <[EMAIL PROTECTED]> added the comment:
The parse_qs() and parse_qsl() relocation from module cgi to urlparse
needs an entry in the "What's new..." (alerting you through here,
because I commited this last night).
See issue 600362 for further inf
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Commited in r66196 and r66199, this went into 2.6/3.0 rc1!!
Thank you all for the effort!
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PR
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Can not get into this now, but I'll be able to deal with this in some
weeks...
--
assignee: -> facundobatista
___
Python tracker <[EMAIL PROTECTED]>
<http://bu
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Senthil, please update the patchs, adding a DeprecationWarning in 3.0 and
a PendingDeprecationWarning in 2.6.
Thanks!
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Gregory... I tried to fill the path in urlunparse, and other functions
that use this started to fail.
As we're so close to final releases, I'll leave this as it's right now,
that a
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Maybe we can put it in urlunparse... do you all agree with this test cases?
def test_alwayspath(self):
u = urlparse.urlparse("http://netloc/path;params?query#fragment";)
self.assertEqual(urlparse.urlunparse(u),
&qu
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Senthil: I don't like that.
Creating a public method called "fix_broken", introducing new behaviours
now in beta, and actually not fixing the url in any broken possibility
(just the path if it's not there), it
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Terry, I don't get to understand your comment. Could you please explain
in more detail? Thank you!
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Senthil:
Look at that URL that the server returned in the second redirect:
http://www.wikispaces.com?responseToken=ee3fca88a9b0dc865152d8a9e5b6138d
See that the "?" appears without a path between the host and it.
Check t
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Antoine, it works great, both in 2.6 and in 3.0 (with the obvious small
modification).
--
nosy: +facundobatista
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Facundo Batista <[EMAIL PROTECTED]> added the comment:
What I think is that the AbstractHTTPHandler is grabbing the headers, in
the do_open() method, in an incorrect way.
Check the get_header() method from Request:
def get_header(self, header_name, default=None):
return self.heade
Changes by Facundo Batista <[EMAIL PROTECTED]>:
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Commited in revs 65710 and 65711.
Thank you all!!
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Facundo Batista <[EMAIL PROTECTED]> added the comment:
This is ok, maybe with some small changes in the docs.
I asked in python-dev if this should go now or wait until 2.7/3.1
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Commited in revs 65679 and 65680.
Thank you all!!
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Senthil: We should ask for advice in the web-sig list to see if this is
enough a "bug to be fixed" now that we're in beta for the releases.
Thanks!
___
Python tracker <
Facundo Batista <[EMAIL PROTECTED]> added the comment:
I'm ok with these patchs, Senthil.
John, what do you think about this?
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.
Facundo Batista <[EMAIL PROTECTED]> added the comment:
zkfarmer, please try the following from your IDLE:
>>> myfilename = r"c:\tmp\test.txt"
>>> fh = open(myfilename, "w")
>>> fh.write("test\n")
>>> fh.close()
>>&g
Changes by Facundo Batista <[EMAIL PROTECTED]>:
--
nosy: +marketdickinson
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3451>
___
_
Facundo Batista <[EMAIL PROTECTED]> added the comment:
The patch looks great, feel free to apply it and commit.
For the record: the name issue that Mark talked about is not in this
last change, it was before, and we handled it the way we now decide
(hey, at least we're coherent wit
Facundo Batista <[EMAIL PROTECTED]> added the comment:
-0 to rename it, specially considering that we had a reduce builtin in
our history... better to not confuse it. But we'd need to convert the
name in the tests...
___
Python tracker <[E
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Commited in r65220.
Thank you everybody!!
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Alexander, tried the issue2417a.diff patch against 65210, and does not
apply cleanly, could you please submit an updated one?
Thanks!
___
Python tracker <[EMAIL PROTECTED]>
<http://
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Ah, sorry, missed that point.
Ok, I included this change and now it works ok.
Also worked a little that code (change the name of the variable
"object", used extend() for a list instead of adding to itself, and
removed a c
Facundo Batista <[EMAIL PROTECTED]> added the comment:
I don't understand.
I tried the following:
Python 2.6b2+ (trunk:65167M, Jul 21 2008, 09:51:48)
[GCC 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)] on linux2
Type "help", "copyright", "credit
Facundo Batista <[EMAIL PROTECTED]> added the comment:
The issue is that you're creating a string of 2GB. It's expectable that
it'll use a lot of resources.
Test this, for example:
>>> a = "." * 2147483647
--
nosy: +facundobatista
resolu
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Confirmed in...
Python 2.6b1+ (trunk:65017M, Jul 16 2008, 13:37:00)
[GCC 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)] on linux2
...with a more simple case:
"""
import sys, cPickle
sys.setrecursionlimit(1040
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Thanks Darryl.
We'll continue in that issue, as the patched commited in this one did
not introduce a regression (it just didn't fix the other bug also).
___
Python tracker <[EMAI
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Here's the link:
http://docs.python.org/dev/library/xml.etree.elementtree.html#the-element-interface
--
nosy: +facundobatista
resolution: -> out of date
status: open -> closed
_
Facundo Batista <[EMAIL PROTECTED]> added the comment:
That class is normally used at the end of the testing suite, as is
recommended in the documentation.
In any case, I don't see that like a bug, so we shouldn't be changing
that behaviour, because of compatibility.
What do
Facundo Batista <[EMAIL PROTECTED]> added the comment:
If readability is enhanced is questionable, but is rejected on the basis
that cosmetic-only changes are not generally recommended: only
difficults following the code evolution in the repository.
The only change that I see reg
1 - 100 of 372 matches
Mail list logo