Facundo Batista <[EMAIL PROTECTED]> added the comment:
Ah, I now understand what you mean.
The best, IMO, to avoid the confusion in the import and in the usage, is
to do:
>>> import curses.ascii as curses_ascii
Do you care to send a patch? Thank you!
--
assignee: -&
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Duplicate of the #754016 one.
--
nosy: +facundobatista
resolution: -> duplicate
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Facundo Batista <[EMAIL PROTECTED]> added the comment:
I think this last patch is ok, but the third case that was raised in the
web-sig should be addressed:
"""
There's even a 3rd case: HTTP's Request-URI. For example, '//path' must
be treated as an
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Hi Senthil, some details:
- You should not withdraw the parse_qsl from cgi.rst (btw, why didn't
you extracted also the parse_qs one?), but put a Deprecation message,
saying that the user should use it from the urlparse module.
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Fixed in 64664.
Thank you everybody!
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.p
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Minutes with 61 (0..60) and 62 (0..61) seconds are used to adjust the
theoretical calendar because of small differences with real world
rotation...
Are you aware of any case where a minute with 63 seconds (0..62) should
b
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Closing as invalid, two reasons:
- Your original issue was that time.strptime() didn't allow 62 seconds,
not that it allowed 60 or 61.
- If you use it to validate input... how do you actually know that
03/25/2012 17:13:61 AM
Facundo Batista <[EMAIL PROTECTED]> added the comment:
What I don't understand here is... if gethostbyname() lacks of IPv6
support, instead of creating a new function why not to add the
functionality to that same function?
Right now gethostbyname() is implemented in C, which w
Changes by Facundo Batista <[EMAIL PROTECTED]>:
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1424152>
___
___
Python-bugs-list mailin
Changes by Facundo Batista <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file10632/unnamed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.o
Facundo Batista <[EMAIL PROTECTED]> added the comment:
I see that you're working on a final solution, this is great!
What we would need also to incorporate this to the trunk is a patch for
the test suite. Senthil, could you handle this?
--
assignee: -> facun
Changes by Facundo Batista <[EMAIL PROTECTED]>:
--
assignee: -> facundobatista
nosy: +facundobatista, orsenthil
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Facundo Batista <[EMAIL PROTECTED]> added the comment:
BitTorment, what would increase the possibility of accepting this is a
patch also for the test suite (test_urllib2.py), checking this
behaviour, for us to be sure that does not break again in the future.
Could you please submit als
Changes by Facundo Batista <[EMAIL PROTECTED]>:
--
assignee: -> facundobatista
nosy: +facundobatista, orsenthil
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by Facundo Batista <[EMAIL PROTECTED]>:
--
assignee: -> facundobatista
nosy: +facundobatista
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Senthil: We would need some tests to assure this will keep working ok in
the future
Also as this is (somehow) a new functionality, we'd need to modify the
NEWS file and maybe even the docs (a comment about this case insensitiv
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Senthil, we should incorporate the tests from RFC 3986 to the test
suite, what do you think?
Coul we integrate the effort from Paul Jimenez and the current urlparse
and achieve a RFC compliant library? Should we handle this complia
Facundo Batista <[EMAIL PROTECTED]> added the comment:
The "r" prefix changes how the escape sequences are interpreted after
the string literal has been parsed, it doesn't change how the literal
itself is actually parsed.
Fixing this will imply too much low level work, and
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Commited in r64745. Thanks for this patch!
--
nosy: +facundobatista
resolution: -> accepted
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Commited in r64746. Thank you!!
--
resolution: -> accepted
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Commited in r64775. Thank you very much!!
--
nosy: +facundobatista
resolution: -> accepted
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Commited in r64781, thank you!!
--
nosy: +facundobatista
resolution: -> accepted
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
Facundo Batista <[EMAIL PROTECTED]> added the comment:
Senthil: patch is fine.
Remember to provide not only a modification for docs, but also to the
Misc/NEWS file.
Thank you!!
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Facundo Batista <[EMAIL PROTECTED]> added the comment:
John:
You say that it will break code because it changes the capitalization
policy, or because other reason? Do you think that there's a way to fix
this issue and not break the code?
If you really think that this breaks c
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
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:
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:
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:
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:
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:
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:
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:
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:
Commited in r65220.
Thank you everybody!!
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
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:
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
Changes by Facundo Batista <[EMAIL PROTECTED]>:
--
nosy: +marketdickinson
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3451>
___
_
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
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:
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:
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:
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 65710 and 65711.
Thank you all!!
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by Facundo Batista <[EMAIL PROTECTED]>:
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
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
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:
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:
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: 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:
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:
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:
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:
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:
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:
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:
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:
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:
Fixed in r66326. Thank you!
--
resolution: -> fixed
status: open -> closed
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs
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:
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:
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
Changes by Facundo Batista <[EMAIL PROTECTED]>:
--
nosy: +facundobatista
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1028088>
___
_
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",
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 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
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:
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 P
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 a
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
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.p
Facundo Batista added the comment:
Commited, rev 59297.
Thank you!
--
nosy: +facundobatista
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1547>
__
___
Changes by Facundo Batista:
--
resolution: -> fixed
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1547>
__
___
Python-bugs
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]>
<htt
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
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]>
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/
Changes by Facundo Batista:
--
assignee: -> facundobatista
nosy: +facundobatista
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1501>
__
___
P
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 &
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
Changes by Facundo Batista:
--
assignee: -> facundobatista
nosy: +facundobatista
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1680>
__
___
P
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 test
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:
Mark is right, the current behaviour is correct. See Tim post for a
longer explanation.
As general help, for the money class take a look of this:
http://sourceforge.net/projects/pymoney
There you'll see that the approach was to store the value, not sub
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.o
Changes by Facundo Batista:
--
assignee: -> facundobatista
nosy: +facundobatista
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1757>
__
___
P
Facundo Batista added the comment:
Fixed in r59852.
--
resolution: -> fixed
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
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/
Facundo Batista added the comment:
Decimal was backported to Py2.5, commited in r59859.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1182>
__
___
Python-bugs-
Changes by Facundo Batista:
--
resolution: -> fixed
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1182>
__
___
Python-bugs
Facundo Batista added the comment:
Fix it, please.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1182>
__
___
Python-bugs-list mailing list
Unsubs
Changes by Facundo Batista:
--
assignee: -> facundobatista
nosy: +facundobatista
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1774>
__
___
P
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: o
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 ->
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.pytho
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 is
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
Ratio
101 - 200 of 372 matches
Mail list logo