>I think that despite the objection that monkeypatching shoudn't be
>made too easy, it's worth at looking into a unification of the API,
>features, and implementation.
I agree. The other virtue of having it in the standard library is that
it's immediately recognisable for what it is.
--
Andrew M
What would be useful is a method that generates (i.e., a generator in
the Python sense) the (continued fraction) convergents to a rational.
People wanting specific constraints on a rational approximation
(including, but not limited to, the two you identified) can easily
build them on top of such a
I am pleased to announce that PyCon 2008 registration is now open!
http://us.pycon.org/2008/registration/
Early-bird registration is open until February 20, so there's one
month to register at the low rates. Regular on-line registration will
be available from February 21 through March 7.
P
On Sun, Jan 20, 2008 at 11:23:38AM +0100, Quentin Gallet-Gilles wrote:
> Excellent ! When will be the next one ? :-)
We could certainly try to hold one in February. Maybe on the 16th?
For March the best date is probably the Monday of the sprints at
PyCon, because there will be a Python core sprin
On Mon, Jan 21, 2008 at 12:17:20AM +0200, Tristan Seligmann wrote:
> * Oleg Broytmann <[EMAIL PROTECTED]> [2008-01-20 20:12:38 +0300]:
>
> > On Sun, Jan 20, 2008 at 06:00:31PM +0100, Christian Heimes wrote:
> > > #!/usr/bin/env python -E -s
> >
> >On most Unicies #! magic may have only one pa
Tristan Seligmann schrieb:
> * Oleg Broytmann <[EMAIL PROTECTED]> [2008-01-20 20:12:38 +0300]:
>
>> On Sun, Jan 20, 2008 at 06:00:31PM +0100, Christian Heimes wrote:
>> > #!/usr/bin/env python -E -s
>>
>>On most Unicies #! magic may have only one parameter after the program;
>> the program he
Brett Cannon writes:
> In my dream schema, severity becomes
Then how does the user indicate how important it is to him? My
severities (in an experimental roundup tracker I'm implementing) are
'inelegant', 'inconvenient', 'some work obstructed', 'much work
obstructed', 'security', 'data loss',
* Oleg Broytmann <[EMAIL PROTECTED]> [2008-01-20 20:12:38 +0300]:
> On Sun, Jan 20, 2008 at 06:00:31PM +0100, Christian Heimes wrote:
> > #!/usr/bin/env python -E -s
>
>On most Unicies #! magic may have only one parameter after the program;
> the program here is env, the parameter is python,
A.M. Kuchling schrieb:
> Today's bug day was a great success. Experienced people like Georg,
> Facundo, and Gregory P. Smith participated, and we also had people who
> submitted their first patches, some of which got applied today, too.
> Hopefully we'll see those people again.
>
> As of this w
I took Python-3000 out of the cc list as I originally just wanted to
make them aware of this issue.
On Jan 14, 2008, at 12:59 PM, Armin Rigo wrote:
> Hi,
>
> On Sat, Jan 12, 2008 at 07:33:38PM -0500, Alexandre Vassalotti wrote:
>> Well, in Python 3K, inst_persistent_id() won't be usable, since
On Jan 20, 2008 6:56 AM, Aahz <[EMAIL PROTECTED]> wrote:
> On Sat, Jan 19, 2008, Guido van Rossum wrote:
> >
> > I believe that a constraint should be that by default (without -3 or a
> > __future__ import) str and bytes should be the same thing. Or, another
> > way of looking at this, reads from b
Georg Brandl wrote:
> Christian currently does a good job of assigning the correct properties
> to new bugs. In any case, I'd prefer to keep a way to mark a bug as
> "high-priority" (meaning that it should be fixed before the next release)
> even if most of the bugs don't have an assigned priority.
On 1/20/08, Paul Moore <[EMAIL PROTECTED]> wrote:
> Both of these are likely to be of limited use. The most common usage I
> know of is to make a "sensible" rational from a float (i.e., a DWIM
> style conversion 0.1 -> 1/10) or to provide readable output. On the
> other hand, both are subtle to imp
Martin v. Löwis schrieb:
> After some months of tracker operation, I'd like to discuss one aspect
> of the tracker schema: priorities.
>
> Each issue has a severity and a priority. The severity is assigned by
> the submitter, defaults to normal, and indicates how serious the issue
> impacts him an
On Jan 20, 2008 10:42 AM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> After some months of tracker operation, I'd like to discuss one aspect
> of the tracker schema: priorities.
>
> Each issue has a severity and a priority. The severity is assigned by
> the submitter, defaults to normal, and ind
Martin v. Löwis wrote:
> After some months of tracker operation, I'd like to discuss one aspect
> of the tracker schema: priorities.
>
> Each issue has a severity and a priority. The severity is assigned by
> the submitter, defaults to normal, and indicates how serious the issue
> impacts him and
After some months of tracker operation, I'd like to discuss one aspect
of the tracker schema: priorities.
Each issue has a severity and a priority. The severity is assigned by
the submitter, defaults to normal, and indicates how serious the issue
impacts him and the community.
The priority is ass
On Sun, Jan 20, 2008 at 07:34:02PM +0100, Jan Claeys wrote:
> Op zondag 20-01-2008 om 20:46 uur [tijdzone +0300], schreef Oleg
> Broytmann:
> > On Sun, Jan 20, 2008 at 06:46:31PM +0100, Jan Claeys wrote:
> > > Op woensdag 16-01-2008 om 02:33 uur [tijdzone +0100], schreef Christian
> > > Heimes:
>
On Sun, Jan 20, 2008 at 07:30:03PM +0100, Christian Heimes wrote:
> Oleg Broytmann wrote:
> > #! /usr/bin/env python -O
> >
> >[trying to execute the script on Linux]
> >
> > /usr/bin/env: python -O: No such file or directory
> >
> > Oleg.
>
> Oh right. I was sure that I've seen a shebang w
Jan Claeys wrote:
> So this is stuff that should never be changed by the user?
~/.local/lib/python2.6 has the same semantics as
/usr/local/lib/python2.6 except it's a per user directory and not per
machine.
Christian
___
Python-Dev mailing list
Python-
Jeroen Ruigrok van der Werven wrote:
> Pendantic note: ~ is an expansion character, the correct variable to talk
> about is HOME (see IEEE Std 1003.1, 2004 section 2.5.3 and 2.6.1).
Most Python developers should the meaning of "~". Should I replace ~
with $HOME for those who don't have as much exp
Op zondag 20-01-2008 om 20:46 uur [tijdzone +0300], schreef Oleg
Broytmann:
> On Sun, Jan 20, 2008 at 06:46:31PM +0100, Jan Claeys wrote:
> > Op woensdag 16-01-2008 om 02:33 uur [tijdzone +0100], schreef Christian
> > Heimes:
> > > ~/Library/ is a Mac OS X thing. I haven't seen it on other Unix sy
Oleg Broytmann wrote:
>A shell has nothing to do with it as it is the OS (exec system call)
> that upon reading the magic of the file sees #! and executes the program
> (up to the first space) and pass to the program the first (and the only)
> parameter.
>
> #! /usr/bin/env python -O
>
>[
Op zondag 20-01-2008 om 18:01 uur [tijdzone +0100], schreef Christian
Heimes:
> Jan Claeys wrote:
> > What do you mean by "configuration directory"? IMHO configuration files
> > on linux/unix should go into ~/.python2.6 or ~/.config/python2.6 or
> > something like that?
>
> It's already renamed i
On Sun, Jan 20, 2008 at 06:46:31PM +0100, Jan Claeys wrote:
> Op woensdag 16-01-2008 om 02:33 uur [tijdzone +0100], schreef Christian
> Heimes:
> > Bill Janssen wrote:
> > > Good point, but I prefer ~/Library/Python to either of these.
> >
> > ~/Library/ is a Mac OS X thing. I haven't seen it on
Op woensdag 16-01-2008 om 02:33 uur [tijdzone +0100], schreef Christian
Heimes:
> Bill Janssen wrote:
> > Good point, but I prefer ~/Library/Python to either of these.
>
> ~/Library/ is a Mac OS X thing. I haven't seen it on other Unix systems.
There is (at least) one linux distro using it, but
On Sun, Jan 20, 2008 at 06:25:57PM +0100, Jeroen Ruigrok van der Werven wrote:
> -On [20080120 18:12], Oleg Broytmann ([EMAIL PROTECTED]) wrote:
> > On most Unicies #! magic may have only one parameter after the program;
> >the program here is env, the parameter is python, and tha
-On [20080120 18:12], Oleg Broytmann ([EMAIL PROTECTED]) wrote:
> On most Unicies #! magic may have only one parameter after the program;
>the program here is env, the parameter is python, and that's all. Adding
>python options will result in different errors - some platforms sil
On Sun, Jan 20, 2008 at 06:00:31PM +0100, Christian Heimes wrote:
> #!/usr/bin/env python -E -s
On most Unicies #! magic may have only one parameter after the program;
the program here is env, the parameter is python, and that's all. Adding
python options will result in different errors - some
-On [20080116 07:15], Oleg Broytmann ([EMAIL PROTECTED]) wrote:
> The site only mentions $HOME/.local/share, there is no $HOME/.local/bin
>at the site.
As was mentioned earlier in the thread. Only $HOME/.local/share was in the
Free Desktop specification. The bin is something that got introduced
A.M. Kuchling schrieb:
> Today's bug day was a great success. Experienced people like Georg,
> Facundo, and Gregory P. Smith participated, and we also had people who
> submitted their first patches, some of which got applied today, too.
> Hopefully we'll see those people again.
>
> As of this w
Jan Claeys wrote:
> What do you mean by "configuration directory"? IMHO configuration files
> on linux/unix should go into ~/.python2.6 or ~/.config/python2.6 or
> something like that?
It's already renamed in the PEP:
http://www.python.org/dev/peps/pep-0370/#specification
Christian
Jan Claeys wrote:
> There should be a way for distro developers to make sure the users local
> 'site-packages' is *not* used when running those tools.
There is an option. Those tools should use the -E and -s argument:
#!/usr/bin/env python -E -s
Christian
___
Op zondag 13-01-2008 om 10:45 uur [tijdzone +0100], schreef Christian
Heimes:
> Gregory P. Smith wrote:
> > My main suggestion was going to be the ability to turn it off as you already
> > mentioned. However, please consider leaving it off by default to avoid
> > problems for installed python scri
Op zaterdag 12-01-2008 om 00:27 uur [tijdzone +0100], schreef Christian
Heimes:
> Specification
> =
[...]
> user configuration directory
>
>Usually the parent directory of the user site directory. It's meant
>for Python version specific data like config files.
>
>Windows:
Malte Helmert wrote:
> One question there: Will the "easy" keyword in roundup be maintained
> further, i.e. will new easy bugs be marked in the future? That would be
> very useful for neophyte contributors.
Yes, we will keep marking easy bugs with the "easy" keyword.
Christian
__
Christian Heimes wrote:
> Quentin Gallet-Gilles wrote:
>> Excellent ! When will be the next one ? :-)
>
> Everyday can be a bug day. :)
> Nobody is going to stop you from squalling through the bug tracker.
I enjoyed the bug day a lot and will certainly come back for more when I
can spare a little
On Sat, Jan 19, 2008, Guido van Rossum wrote:
>
> I believe that a constraint should be that by default (without -3 or a
> __future__ import) str and bytes should be the same thing. Or, another
> way of looking at this, reads from binary files and reads from sockets
> (and other similar things, lik
On 19/01/2008, Jeffrey Yasskin <[EMAIL PROTECTED]> wrote:
> The first returns the closest rational whose denominator is less than
> a given integer.
[...]
> The second returns the simplest rational within some distance.
Both of these are likely to be of limited use. The most common usage I
know of
Quentin Gallet-Gilles wrote:
> Excellent ! When will be the next one ? :-)
Everyday can be a bug day. :)
Nobody is going to stop you from squalling through the bug tracker.
Christian
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.o
Excellent ! When will be the next one ? :-)
On Jan 20, 2008 2:14 AM, A.M. Kuchling <[EMAIL PROTECTED]> wrote:
> Today's bug day was a great success. Experienced people like Georg,
> Facundo, and Gregory P. Smith participated, and we also had people who
> submitted their first patches, some of wh
41 matches
Mail list logo
