Am 02.04.2012 00:31, schrieb Matěj Cepl:
On 1.4.2012 23:46, Brian Curtin wrote:
For what reason? Are the git or bzr files causing issues on HG?
No, but wrong .gitignore causes issues with git repo obtained via
hg-fast-import. If it is meant as an intentional sabotage of using git
(and bzr)
On 02/04/2012 07:03, Martin v. Löwis wrote:
Am 02.04.2012 00:31, schrieb Matěj Cepl:
On 1.4.2012 23:46, Brian Curtin wrote:
For what reason? Are the git or bzr files causing issues on HG?
No, but wrong .gitignore causes issues with git repo obtained via
hg-fast-import. If it is meant as an
On 30 March 2012 21:52, Guido van Rossum gu...@python.org wrote:
Oh dear. I really want to say that 15 ms is good enough. Some possible
exceptions I can think of:
- Profiling. But this really wants to measure CPU time anyways, and it
already uses a variety of hacks and heuristics to pick the
On 2.4.2012 05:26, Scott Dial wrote:
Create an issue on the bug tracker. In the meantime, you can either
commit the change to your clone, or you can put your ignores into
.git/info/exclude. No reason to be so sore about it, since Git lets you
have your own ignore file without requiring it be a
On 2.4.2012 00:52, Guido van Rossum wrote:
Please file a bug to get this reviewed and checked in.
OK, I don't agree with the reasoning, but I willingly submit to BDFL ;)
http://bugs.python.org/issue14472
Matěj
___
Python-Dev mailing list
I've just finished sketching out a skeleton here:
https://bitbucket.org/cameron_simpson/css/src/fb476fcdcfce/lib/python/cs/clockutils.py
get_clock() returns None if no clock has the requested flags, whereas
I expected an exception (LookupError or NotImplementError?).
get_clock() doesn't
On Sun, 1 Apr 2012 19:44:00 -0500
Brian Curtin br...@python.org wrote:
On Sun, Apr 1, 2012 at 17:31, Matěj Cepl mc...@redhat.com wrote:
On 1.4.2012 23:46, Brian Curtin wrote:
For what reason? Are the git or bzr files causing issues on HG?
No, but wrong .gitignore causes issues with
Antoine Pitrou, 02.04.2012 13:50:
On Sun, 1 Apr 2012 19:44:00 -0500
Brian Curtin wrote:
On Sun, Apr 1, 2012 at 17:31, Matěj Cepl wrote:
On 1.4.2012 23:46, Brian Curtin wrote:
For what reason? Are the git or bzr files causing issues on HG?
No, but wrong .gitignore causes issues with git
On Mon, Apr 2, 2012 at 2:31 AM, Sam Partington sam.parting...@gmail.com wrote:
On 30 March 2012 21:52, Guido van Rossum gu...@python.org wrote:
Oh dear. I really want to say that 15 ms is good enough. Some possible
exceptions I can think of:
- Profiling. But this really wants to measure CPU
On Mon, Apr 2, 2012 at 9:50 PM, Antoine Pitrou solip...@pitrou.net wrote:
That said, these files will always be outdated, so we might as well
remove them so that at least git / bzr users don't get confused.
Apologies for what may be a stupid suggestion, but is it possible to
write a script that
At least on some versions of Windows (e.g. XP) the
QueryPerformanceCounter()-API is more or less only a stub around a
call to RDTSC which in turn varies in frequency on (at least) Intel
Pentium 4, Pentium M and Xeon processors (bound to the current clock
frequencies).
-Original Message-
From: python-dev-bounces+kristjan=ccpgames@python.org
[mailto:python-dev-bounces+kristjan=ccpgames@python.org] On
Behalf Of Cameron Simpson
Sent: 30. mars 2012 21:43
There seem to be a few competing features for clocks that people want:
- monotonic -
You seem to have missed the episode where I explained that caching the
last value in order to avoid going backwards doesn't work -- at least
not if the cached value is internal to the API implementation.
2012/4/2 Kristján Valur Jónsson krist...@ccpgames.com:
-Original Message-
From:
On 4/2/2012 4:37 AM, Victor Stinner wrote:
The API looks much more complex than the API proposed in PEP 418 just
to get the time. You have to call a function to get a function, and
then call the function, instead of just calling a function directly.
Instead of returning an object with a now()
On Apr 2, 2012, at 10:39 AM, Kristján Valur Jónsson wrote:
no steps is something unquantifiable. All time has steps in it.
No steps means something very specific when referring to time APIs. As I
recently explained here:
http://article.gmane.org/gmane.comp.python.devel/131487/.
-glyph
On 4/2/2012 11:03 AM, Chris Angelico wrote:
On Mon, Apr 2, 2012 at 9:50 PM, Antoine Pitrou solip...@pitrou.net wrote:
That said, these files will always be outdated, so we might as well
remove them so that at least git / bzr users don't get confused.
Apologies for what may be a stupid
On 02Apr2012 13:37, Victor Stinner victor.stin...@gmail.com wrote:
| I've just finished sketching out a skeleton here:
|
https://bitbucket.org/cameron_simpson/css/src/fb476fcdcfce/lib/python/cs/clockutils.py
|
| get_clock() returns None if no clock has the requested flags, whereas
| I
On Mon, Apr 2, 2012 at 9:50 PM, Antoine Pitrou solip...@pitrou.net wrote:
That said, these files will always be outdated, so we might as well
remove them so that at least git / bzr users don't get confused.
Given that they were originally *added* by core devs that are (or
were) using git/bzr
On 03Apr2012 07:38, I wrote:
| On 02Apr2012 13:37, Victor Stinner victor.stin...@gmail.com wrote:
| | Could you please update your code according to my remarks? I will try
| | to integrate it into the PEP. A PEP should list all alternatives!
New code here:
On 02Apr2012 10:44, Glenn Linderman v+pyt...@g.nevcal.com wrote:
| On 4/2/2012 4:37 AM, Victor Stinner wrote:
| The API looks much more complex than the API proposed in PEP 418 just
| to get the time. You have to call a function to get a function, and
| then call the function, instead of just
On 03Apr2012 07:38, I wrote:
| On 02Apr2012 13:37, Victor Stinner victor.stin...@gmail.com wrote:
| | Should I use
| | MONTONIC_CLOCKS or HIRES_CLOCKS when I would like a monotonic and
| | high-resolution clock?
|
| Note that you don't need to provide a clock list at all; get_clock(0
| will use
On Tue, 3 Apr 2012 07:43:20 +1000
Nick Coghlan ncogh...@gmail.com wrote:
On Mon, Apr 2, 2012 at 9:50 PM, Antoine Pitrou solip...@pitrou.net wrote:
That said, these files will always be outdated, so we might as well
remove them so that at least git / bzr users don't get confused.
Given
On Tue, Apr 3, 2012 at 3:44 AM, Glenn Linderman v+pyt...@g.nevcal.com wrote:
One thing I don't like about the idea of fallback being buried under some
API is that the efficiency of that API on each call must be less than the
efficiency of directly calling an API to get a single clock's time.
On 4/2/2012 2:40 PM, Nick Coghlan wrote:
On Tue, Apr 3, 2012 at 3:44 AM, Glenn Lindermanv+pyt...@g.nevcal.com wrote:
One thing I don't like about the idea of fallback being buried under some
API is that the efficiency of that API on each call must be less than the
efficiency of directly
On 03Apr2012 07:51, I wrote:
| Changelog: updates based on suggestions from Victor Stinner: flat API
| calls to get time directly, make now() a method instead of a property,
| default flags for get_clock(), adjust hr_clock() to hires_clock(0 for
| consistency.
BTW, I'd also happily change T_HIRES
On Tue, 03 Apr 2012 00:44:32 +0200, Antoine Pitrou solip...@pitrou.net wrote:
On Tue, 3 Apr 2012 07:43:20 +1000
Nick Coghlan ncogh...@gmail.com wrote:
On Mon, Apr 2, 2012 at 9:50 PM, Antoine Pitrou solip...@pitrou.net wrote:
That said, these files will always be outdated, so we might as
On 02Apr2012 14:59, Glenn Linderman v+pyt...@g.nevcal.com wrote:
| On 4/2/2012 2:40 PM, Nick Coghlan wrote:
| On Tue, Apr 3, 2012 at 3:44 AM, Glenn Lindermanv+pyt...@g.nevcal.com
wrote:
|One thing I don't like about the idea of fallback being buried under
some
|API is that the
Hi all,
If you are a running a build slave or otherwise have an MSDN account
for development work, please check that your MSDN subscription is
still in effect. If the subscription expired, please let me know in
private what your subscriber ID is along with the email address you
use for the
I like the aim of letting the user control what clock it get, but I
find this API pretty horrible:
clock = get_clock(T_MONOTONIC|T_HIRES) or get_clock(T_MONOTONIC)
Just my 2 groszy.
//Lennart
___
Python-Dev mailing list
Python-Dev@python.org
29 matches
Mail list logo
