Did you mean to also modify sched.py in this changeset?
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Hey folks,
I'm pleased to announce that as of changeset 74d182cf0187, the
standard library now includes support for the LZMA compression
algorithm (as well as the associated .xz and .lzma file formats). The
new lzma module has a very similar API to the existing bz2 module; it
should serve as a
On Thu, Dec 15, 2011 at 10:44 PM, benjamin.peterson
python-check...@python.org wrote:
+# eval_input is the input for the eval() functions.
Shouldn't this be function rather than functions?
___
Python-Dev mailing list
Python-Dev@python.org
On Thu, Jan 19, 2012 at 11:03 PM, sandro.tosi
python-check...@python.org wrote:
+ are gathered into a lits. This is commonly useful for command line
s/lits/list ?
___
Python-Dev mailing list
Python-Dev@python.org
Hi all,
I've noticed that most of the Mac buildbots have been offline for a while:
* http://www.python.org/dev/buildbot/all/buildslaves/parc-snowleopard-1
* http://www.python.org/dev/buildbot/all/buildslaves/parc-tiger-1
* http://www.python.org/dev/buildbot/all/buildslaves/parc-leopard-1
Does
This may be a bug in the tracker, possibly related to
http://psf.upfronthosting.co.za/roundup/meta/issue402 - it
seems like changes to a user's details on bugs.python.org
are not propagated to the review tool.
Cheers,
Nadeem
___
Python-Dev mailing list
So wallclock() falls back to a not-necessarily-monotonic time source
if necessary,
while monotonic() raises an exception in that case? ISTM that these
don't need to
be separate functions - rather, we can have one function that takes a
flag (called
require_monotonic, or something like that) telling
On Wed, Mar 14, 2012 at 3:03 AM, Victor Stinner
victor.stin...@gmail.com wrote:
I suppose that most libraries and programs will have to implement a
similar fallback.
We may merge both functions with a flag to be able to disable the
fallback. Example:
- time.realtime(): best-effort
A summary of the discussion so far, as I've understood it:
- We should have *one* monotonic/steady timer function, using the
sources described in Victor's original post.
- By default, it should fall back to time.time if a better source is
not available, but there should be a flag that can
+1 for time.steady(strict=False).
On Wed, Mar 14, 2012 at 7:09 PM, Kristján Valur Jónsson
krist...@ccpgames.com wrote:
- By default, it should fall back to time.time if a better source is
not available, but there should be a flag that can disable this
fallback for users who really *need* a
On Thu, Mar 15, 2012 at 1:10 PM, Paul Moore p.f.mo...@gmail.com wrote:
Monotonic clocks are not necessarily hardware based, and may be adjusted
forward by NTP.
I appreciate that. But I'm still unclear how you would tell that had
happened as part of the implementation. One call to the OS
The lzma module ran into a similar issue with 32-bit unsigned ints.
I worked around it by writing a custom converter function to use
with the O code.
You can find the converter definition here:
http://hg.python.org/cpython/file/default/Modules/_lzmamodule.c#l134
And an example usage here:
On Sat, Mar 31, 2012 at 8:27 AM, Lennart Regebro rege...@gmail.com wrote:
So, how about time.timer()?
That seems like a bad idea; it would be too easy to confuse with (or misspell
as) time.time().
Out of the big synonym list Guido posted, I rather like time.stopwatch() - it
makes it more
On Sat, May 19, 2012 at 2:11 PM, kristjan.jonsson
python-check...@python.org wrote:
+Visual Studio 2010 uses version 10 of the C runtime (MSVCRT9). The
executables
Shouldn't that be MSVCRT10?
Nadeem
___
Python-Dev mailing list
Since this changeset, building on Windows seems to be broken (see
http://python.org/dev/buildbot/all/builders/x86%20XP-5%203.x/builds/450
for example).
Nadeem
___
Python-Dev mailing list
Python-Dev@python.org
On Sun, Jun 17, 2012 at 8:33 AM, nick.coghlan
python-check...@python.org wrote:
+ @property
+ def version(self):
+ msg = '%200s has no version specified' % (type(self),)
+ raise NotImplementedError(msg)
+
Shouldn't that be %.200s, rather than %200s?
2010/11/23 Łukasz Langa luk...@langa.pl:
If you agree to do that for regrtest I will clean up the tests for warnings.
Already did that for zipfile so it doesn't raise ResourceWarnings anymore. I
just need to correct multiprocessing and xmlrpc ResourceWarnings, silence
some DeprecationWarnings
On Thu, Nov 25, 2010 at 11:34 AM, Glenn Linderman v+pyt...@g.nevcal.com wrote:
So the following code defines constants with associated names that get put
in the repr.
The code you gave doesn't work if the constant() function is moved
into a separate module from the code that calls it. The
On Thu, Jan 20, 2011 at 3:11 PM, Antoine Pitrou solip...@pitrou.net wrote:
On Thu, 20 Jan 2011 10:47:04 +0100 (CET)
raymond.hettinger python-check...@python.org wrote:
+Code Repository
+===
+
+In addition to the existing Subversion code repository at
http://svn.python.org
On Sat, Mar 12, 2011 at 9:32 AM, Eli Bendersky eli...@gmail.com wrote:
The devguide's recommendation is to forward-port changes withing a major
release line, i.e. if I need something in all 3.[123], then start with 3.1
and forward-port (by hg merge branch) to 3.2 and then 3.3
Just to clarify
On Sat, Mar 12, 2011 at 1:29 PM, Martin v. Löwis mar...@v.loewis.de wrote:
Isn't that command correct only if you are merging into default?
ISTM that it should be hg revert -ar targetbranch.
In general, yes. However, the existing text refers specifically to the
case of merging 3.2
into default,
On Sun, Mar 13, 2011 at 12:43 AM, Éric Araujo mer...@netwok.org wrote:
hg revert -ar default
You can’t combine the -r option with other options. (Yes, it’s a known bug.)
It seems to work for me (Mercurial 1.6.3 on Ubuntu). But I suppose it
wouldn't hurt
to split the options up.
Regards,
I was wondering what the policy is regarding copyright notices and license
boilerplate text at the top of source files.
I am currently rewriting the bz2 module (see http://bugs.python.org/issue5863),
splitting the existing Modules/bz2module.c into Modules/_bz2module.c and
Lib/bz2.py.
Are new
On Mon, Mar 21, 2011 at 2:20 PM, M.-A. Lemburg m...@egenix.com wrote:
Nadeem Vawda wrote:
[snip]
Since you'll be adding new IP to Python, the new code you write should
contain your copyright and the standard PSF contributor agreement
notice, e.g.
(c) Copyright 2011 by Nadeem Vawda
On Sun, Apr 3, 2011 at 8:02 PM, Antoine Pitrou solip...@pitrou.net wrote:
On Sun, 03 Apr 2011 18:55:33 +0200
Éric Araujo mer...@netwok.org wrote:
I think we use Misc/ACKS for code+docs contribution like this one,
Doc/ACKS.txt being used for doc-only changes. This second file is not
Thanks for the feedback. I'll be sure to include more information in my
future commit messages.
Nadeem
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
On Thu, Apr 28, 2011 at 4:44 PM, Senthil Kumaran orsent...@gmail.com wrote:
On Thu, Apr 28, 2011 at 04:20:06PM +0200, Éric Araujo wrote:
if hasattr(os, symlink) and hasattr(os, link):
# For systems that support symbolic and hard links.
if tarinfo.issym():
it sees that
targetpath already exists.
On Thu, Apr 28, 2011 at 5:44 PM, Antoine Pitrou solip...@pitrou.net wrote:
On Thu, 28 Apr 2011 17:40:05 +0200
Nadeem Vawda nadeem.va...@gmail.com wrote:
The deletion case could be handled like this:
if tarinfo.issym():
+try
On Tue, May 3, 2011 at 3:19 PM, victor.stinner
python-check...@python.org wrote:
+# Issue #10276 - check that inputs of 2 GB are handled correctly.
+# Be aware of issues #1202, #8650, #8651 and #10276
+class ChecksumBigBufferTestCase(unittest.TestCase):
+ int_max = 0x7FFF
+
+
On Tue, May 3, 2011 at 10:38 PM, Victor Stinner
victor.stin...@haypocalc.com wrote:
I don't want to check OverflowError: the test is supposed to compute the
checksum of a buffer of 0x7FFF bytes, to check crc32() and
adler32(). 0x7FFF is the biggest size supported by these functions
On Thu, May 5, 2011 at 11:33 AM, Victor Stinner
victor.stin...@haypocalc.com wrote:
Le mercredi 04 mai 2011 à 15:40 -0700, Ethan Furman a écrit :
The comment says 'check that inputs of 2 GB are handled correctly' but
the file created is 1 byte short of 2Gb. Is the test wrong, or just
wrongly
On Mon, May 9, 2011 at 2:53 PM, Jim Jewett jimjjew...@gmail.com wrote:
Can you clarify (preferably in the commit message as well) exactly
*why* these largefile tests are useless? For example, is there
another test that covers this already?
Ah, sorry about that. It was discussed on the tracker
On Wed, May 18, 2011 at 2:21 PM, Victor Stinner
victor.stin...@haypocalc.com wrote:
''.join(c for c in 'abc') and ''.join([c for c in 'abc']) do create a
temporary c variable.
I'm not sure why you would encounter code like that in the first place.
Surely any code of the form:
''.join(c for
I would like to propose adding a class to the stdlib to provide a more flexible
LRU caching mechanism. As things stand, the functools.lru_cache() decorator is
fine for memoization of pure functions, but does not accommodate situations
where cache entries become stale and must be
On Fri, Jul 29, 2011 at 2:46 PM, Antoine Pitrou solip...@pitrou.net wrote:
There's no practical difference (from the user's point of view) between
extension modules and the library, so I think the Extension Modules
section should simply die.
+1. This has been bugging me for a while now.
On Sun, Jul 31, 2011 at 10:26 AM, Nick Coghlan ncogh...@gmail.com wrote:
On Sun, Jul 31, 2011 at 9:09 AM, nadeem.vawda
python-check...@python.org wrote:
- Remove duplicate test run in make test and make testuniversal
That seems very questionable - the rationale for running the test
suite
Thanks for catching that. Fixed in 0b52b6f1bfab.
Nadeem
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
On Tue, Aug 23, 2011 at 8:39 PM, Ross Lagerwall rosslagerw...@gmail.com wrote:
When reviewing the PEP 3151 implementation (*), Ezio commented that
FileSystemError looks a bit strange and that FilesystemError would
be a better spelling. What is your opinion?
I think FilesystemError looks nicer,
Hello all,
I'd like to propose the addition of a new module in Python 3.3. The 'lzma'
module will provide support for compression and decompression using the LZMA
algorithm, and the .xz and .lzma file formats. The matter has already been
discussed on the tracker http://bugs.python.org/issue6715,
On Sat, Aug 27, 2011 at 4:50 PM, Martin v. Löwis mar...@v.loewis.de wrote:
The implementation will also be similar to bz2 - basic compressor and
decompressor classes written in C, with convenience functions and a file
interface implemented on top of those in Python.
When I reviewed lzma, I
On Sat, Aug 27, 2011 at 5:15 PM, Martin v. Löwis mar...@v.loewis.de wrote:
As for file formats, these are handled by liblzma itself; the extension
module
just selects which compressor/decompressor initializer function to use
depending
on the value of the format argument. Our code won't
On Sat, Aug 27, 2011 at 5:42 PM, Martin v. Löwis mar...@v.loewis.de wrote:
Not sure whether you already have this: supporting the tarfile module
would be nice.
Yes, got that - issue 5689. Also of interest is issue 5411 - adding .xz
support to distutils. But I think that these are separate
On Sat, Aug 27, 2011 at 9:47 PM, Terry Reedy tjre...@udel.edu wrote:
On 8/27/2011 9:47 AM, Nadeem Vawda wrote:
I'd like to propose the addition of a new module in Python 3.3. The 'lzma'
module will provide support for compression and decompression using the
LZMA
algorithm, and the .xz
On Sat, Aug 27, 2011 at 10:41 PM, Dan Stromberg drsali...@gmail.com wrote:
It seems like there should be some way of coming up with an xml file
describing the types of the various bits of data and formal arguments -
perhaps using gccxml or something like it.
The problem is that you would need
I've updated the issue http://bugs.python.org/issue6715 with a patch
containing my work so far - the LZMACompressor and LZMADecompressor classes,
along with some tests. These two classes should provide a fairly complete
interface to liblzma; it will be possible to implement LZMAFile on top of
I can confirm that libpthread.so (/usr/lib/x86_64-linux-gnu/libpthread.so)
is a linker script on my Ubuntu 11.04 install. This hasn't ever caused me
any problems, though.
As for why distributions do this, here are the contents of the script:
/* GNU ld script
Use the shared library,
I've posted an updated patch to the bug tracker, with a complete implementation
of the lzma module, including 100% test coverage for the LZMAFile class (which
is implemented entirely in Python). It doesn't include ReST documentation (yet),
but the docstrings are quite detailed.
Please take a look
Another update - I've added proper documentation. Now the code should be
pretty much complete - all that's missing is the necessary bits and pieces
to build it on Windows.
Cheers,
Nadeem
___
Python-Dev mailing list
Python-Dev@python.org
On Thu, Jun 27, 2013 at 12:07 AM, Victor Stinner
victor.stin...@gmail.comwrote:
I would to parse an integer in [0; UINT_MAX] to fix the zlib module on
64-bit system:
http://bugs.python.org/issue18294
How should I implement that? Use O format and then use
PyLong_Check(), PyLong_AsLong(), and
On Mon, Oct 1, 2012 at 11:11 PM, nadeem.vawda
python-check...@python.org wrote:
http://hg.python.org/cpython/rev/a19f47d380d2
changeset: 79382:a19f47d380d2
parent: 79378:fb90e2ff95b7
parent: 79381:6d7bf512e0c3
user:Nadeem Vawda nadeem.va...@gmail.com
date:Mon Oct
This change appears to have broken test_urllib. See, for example:
http://buildbot.python.org/all/builders/AMD64%20OpenIndiana%203.x/builds/4774/steps/test/logs/stdio
- Nadeem
___
Python-Dev mailing list
Python-Dev@python.org
Just to clarify, the release branch hasn't been created yet, correct?
- Nadeem
On Sun, Feb 3, 2013 at 3:38 PM, Benjamin Peterson benja...@python.orgwrote:
2013/2/3 Serhiy Storchaka storch...@gmail.com:
There are crashers for which patches were proposed but do not reviewed
yet:
Issue
52 matches
Mail list logo
