Hi,
I am afraid that here is the right place to say but I implemented a
patch to add support for Camellia block cipher to Python Cryptography
Toolkit (aka. pycrypto). Camellia is one of the approved encryption
methods by European Union (one of the finalist of NESSIE) and has
specified in several
> Will you please review and test it?
> I hope pycrypto will include the patch.
Dear Yoshisato,
python-dev is not the right place - we deal with the core
Python distribution only. OTOH, amk.ca is probably a good
place; you might also consider posting it to the Python-Crypto
mailing list (http://l
> python-dev is not the right place - we deal with the core
> Python distribution only. OTOH, amk.ca is probably a good
I am sorry to my send email to wrong place, and
thank you for letting me know the right place.
I will send my email to the python-crypto mailing list,
and will also post my patc
The test_raiseMemError() in test_unicode.py is complicating me the
regression tests: tries to use all the memory in my system, which
starts to swap as crazy, and almost freezes everything. When the test
finishes (always pass ok), I have all the memory flushed so it take a
few seconds to go back to
Hi!
The issue 600362 has two patches (one for 2.6 and the other for 3.0)
that are ready to commit (with a small change in the docs). This
patches relocates the parse_qs and parse_qsl functions into the
urlparse module (urllib.parse in 3k), bringing them from the cgi one.
For backward compatibilit
Facundo Batista wrote:
> The test_raiseMemError() in test_unicode.py is complicating me the
> regression tests: tries to use all the memory in my system, which
> starts to swap as crazy, and almost freezes everything. When the test
> finishes (always pass ok), I have all the memory flushed so it ta
Hi,
Le Saturday 16 August 2008 15:43:28 Facundo Batista, vous avez écrit :
> The test_raiseMemError() in test_unicode.py is complicating me the
> regression tests: tries to use all the memory in my system, which
> starts to swap as crazy, and almost freezes everything.
On UNIX, it's possible to l
Facundo Batista gmail.com> writes:
>
> The test_raiseMemError() in test_unicode.py is complicating me the
> regression tests: tries to use all the memory in my system, which
> starts to swap as crazy, and almost freezes everything. When the test
> finishes (always pass ok), I have all the memory
2008/8/16 Antoine Pitrou <[EMAIL PROTECTED]>:
> If the test does allocate the very large string, it means MemoryError isn't
> raised, which defeats the purpose of the test.
I do *not* want to remove the test.
I just want to execute it *only* when I run "-u all" or "-u memory",
not everytime I ru
This may or may not be relevant to 2.6 or 3.0 (because I don't have
those handy at the moment), but on 2.5 and earlier:
Python 2.5.2 (r252:60911, May 7 2008, 15:19:09)
[GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> print ev
On Sat, 16 Aug 2008 13:01:33 -0300, Facundo Batista <[EMAIL PROTECTED]> wrote:
2008/8/16 Antoine Pitrou <[EMAIL PROTECTED]>:
If the test does allocate the very large string, it means MemoryError isn't
raised, which defeats the purpose of the test.
I do *not* want to remove the test.
Antoine
Facundo Batista gmail.com> writes:
>
> I do *not* want to remove the test.
You misunderstood my remark.
If the test takes a lot of time and eats a lot of memory, it's precisely because
the MemoryError isn't raised; and the test needs MemoryError to be raised in
order to be meaningful.
I was pro
> Are you having also this issue? Do you think that it should run not *always*?
See bug http://bugs.python.org/issue3556
If no solution is forthcoming quickly, I recommend to remove/disable the
test.
Regards,
Martin
___
Python-Dev mailing list
Python-
2008/8/16 "Martin v. Löwis" <[EMAIL PROTECTED]>:
> See bug http://bugs.python.org/issue3556
>
> If no solution is forthcoming quickly, I recommend to remove/disable the
> test.
The Antoine patch works ok for me, and solves the whole issue.
I'm on linux, if somebody can give it a try in another p
Antoine Pitrou wrote:
Facundo Batista gmail.com> writes:
The test_raiseMemError() in test_unicode.py is complicating me the
regression tests: tries to use all the memory in my system, which
starts to swap as crazy, and almost freezes everything. When the test
finishes (always pass ok), I have
On Sat, Aug 16, 2008 at 7:04 AM, Facundo Batista
<[EMAIL PROTECTED]> wrote:
> Hi!
>
> The issue 600362 has two patches (one for 2.6 and the other for 3.0)
> that are ready to commit (with a small change in the docs). This
> patches relocates the parse_qs and parse_qsl functions into the
> urlparse
Patrick Maupin wrote:
This may or may not be relevant to 2.6 or 3.0 (because I don't have
those handy at the moment), but on 2.5 and earlier:
Python 2.5.2 (r252:60911, May 7 2008, 15:19:09)
[GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)] on linux2
Type "help", "copyright", "credits" or "license" for more
If you import a module that uses '\r\n' line endings, Python does the
right thing. But if you read in the bytes for the same file and then
pass it to compile() you get an unhelpful syntax error pointing at a
blank line.
Normally I would say one should just open the source file as 'r'
instead of 'r
On Sat, Aug 16, 2008 at 8:34 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> If you import a module that uses '\r\n' line endings, Python does the
> right thing. But if you read in the bytes for the same file and then
> pass it to compile() you get an unhelpful syntax error pointing at a
> blank line
19 matches
Mail list logo
