Re: [Python-Dev] RELEASED Python 2.6.2
In article , "Russell E. Owen" wrote: > In article , > Ned Deily wrote: > > In article , > > Russell Owen wrote: > > > I installed the Mac binary on my Intel 10.5.6 system and it works, > > > except it still uses Apple's system Tcl/Tk 8.4.7 instead of my > > > ActiveState 8.4.19 (which is in /Library/Frameworks where one would > > > expect). > > > > > > I just built python from source and that version does use ActiveState > > > 8.4.19. > > > > > > I wish I knew what's going on. Not being able to use the binary > > > distros is a bit of a pain. > > > > You're right, the tkinter included with the 2.6.2 installer is not > > linked properly: > > > > Is: > > $ cd /Library/Frameworks/Python.framework/Versions/2.6 > > $ cd lib/python2.6/lib-dynload > > $ otool -L _tkinter.so > > _tkinter.so: > >/System/Library/Frameworks/Tcl.framework/Versions/8.4/Tcl > > (compatibility version 8.4.0, current version 8.4.0) > >/System/Library/Frameworks/Tk.framework/Versions/8.4/Tk > > (compatibility version 8.4.0, current version 8.4.0) > >/usr/lib/libSystem.B.dylib [...] > > > > should be: > > _tkinter.so: > >/Library/Frameworks/Tcl.framework/Versions/8.4/Tcl (compatibility > > version 8.4.0, current version 8.4.19) > >/Library/Frameworks/Tk.framework/Versions/8.4/Tk (compatibility > > version 8.4.0, current version 8.4.19) > >/usr/lib/libSystem.B.dylib [...] > > Just for the record, when I built Python 2.6 from source I got the > latter output (the desired result). > > If someone can point me to instructions I'm willing to try to make a > binary installer and make it available (though I'd much prefer to debug > the standard installer). I suspect Ronald will be fixing this in the standard installer soon. -- Ned Deily, n...@acm.org ___ 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
Re: [Python-Dev] RELEASED Python 2.6.2
In article , Ned Deily wrote: > In article , > Russell Owen wrote: > > I installed the Mac binary on my Intel 10.5.6 system and it works, > > except it still uses Apple's system Tcl/Tk 8.4.7 instead of my > > ActiveState 8.4.19 (which is in /Library/Frameworks where one would > > expect). > > > > I just built python from source and that version does use ActiveState > > 8.4.19. > > > > I wish I knew what's going on. Not being able to use the binary > > distros is a bit of a pain. > > You're right, the tkinter included with the 2.6.2 installer is not > linked properly: > > Is: > $ cd /Library/Frameworks/Python.framework/Versions/2.6 > $ cd lib/python2.6/lib-dynload > $ otool -L _tkinter.so > _tkinter.so: >/System/Library/Frameworks/Tcl.framework/Versions/8.4/Tcl > (compatibility version 8.4.0, current version 8.4.0) >/System/Library/Frameworks/Tk.framework/Versions/8.4/Tk > (compatibility version 8.4.0, current version 8.4.0) >/usr/lib/libSystem.B.dylib [...] > > should be: > _tkinter.so: >/Library/Frameworks/Tcl.framework/Versions/8.4/Tcl (compatibility > version 8.4.0, current version 8.4.19) >/Library/Frameworks/Tk.framework/Versions/8.4/Tk (compatibility > version 8.4.0, current version 8.4.19) >/usr/lib/libSystem.B.dylib [...] Just for the record, when I built Python 2.6 from source I got the latter output (the desired result). If someone can point me to instructions I'm willing to try to make a binary installer and make it available (though I'd much prefer to debug the standard installer). -- Russell ___ 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
Re: [Python-Dev] Issue5434: datetime.monthdelta
On Fri, Apr 17, 2009, BJ?rn Lindqvist wrote: > > It's not only about what people find intuitive. Why care about them? > Most persons aren't programmers. It is about what application > developers find useful too. I have often needed to calculate month > deltas according to the proposal. I suspect many other programmers > have too. Writing a month add function isn't entirely trivial and > would be a good candidate for stdlib imho. At this point, further discussion really needs to move to python-ideas; for acceptance in stdlib, there needs to be either well-accepted code out in the community or a PEP for Guido to pronounce on (or probably both, in the end). I've set followups to python-ideas for convenience. -- Aahz (a...@pythoncraft.com) <*> http://www.pythoncraft.com/ "If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." --Red Adair ___ 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
Re: [Python-Dev] Issue5434: datetime.monthdelta
It's not only about what people find intuitive. Why care about them? Most persons aren't programmers. It is about what application developers find useful too. I have often needed to calculate month deltas according to the proposal. I suspect many other programmers have too. Writing a month add function isn't entirely trivial and would be a good candidate for stdlib imho. 2009/4/17, Antoine Pitrou : > James Y Knight fuhm.net> writes: >> >> It's a human-interface operation, and as such, everyone (ahem) "knows >> what it means" to say "2 months from now", but the details don't >> usually have to be thought about too much. > > I don't think it's true. When you say "2 months from now", some people will > think "9 weeks from now" (or "10 weeks from now"), others "60 days from > now", > and yet other will think of the meaning this proposal gives it. > > That's why, when scheduling a meeting, you don't say "2 months from now". > You > give a precise date instead, because you know otherwise people wouldn't show > up > on the same day. > > Regards > > Antoine. > > > ___ > 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/bjourne%40gmail.com > -- mvh Björn ___ 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
[Python-Dev] Experimental and Test Tracker instances live
Hi,
As discussed before, I have put two mock Python Tracker instances online.
The Test[1] instance follows bugs.python.org code, so we can test
bugfixes and procedures without breaking the real tracker. The
Experimental[2] one, aka the cool instance, is where new features are
showcased.
Currently no emails are being sent and the dbs can be reset at any
time. If you'd like to play as a registered user, please email me and
I'll create a user (or activate the one you've started to register).
So far, the new features[3] include:
* Issue tags [4],[5]
* Quiet properties [6]
* Restore removed messages and files [7]
* Claim ('assign to self') and add/remove self as nosy buttons [8]
* Don't close issues with open dependencies [9]
* Auto-add nosy users based on Components [10]
* "Email me" buttons for messages and issues, "Reply by email" [11]
* RSS feeds (per issue and global) [12]
* Display selected issues in the index view [13]
You can subscribe to a RSS feed[14] about the new features.
Thanks to everyone who filled RFEs, there's still time to submit yours :)
Regards,
Daniel
[1] http://bot.bio.br/python-dev/
[2] http://bot.bio.br/python-dev-exp/
[3] http://bot.bio.br/python-dev-exp/issue5
[4] http://mail.python.org/pipermail/tracker-discuss/2009-April/002099.html
[5] http://codereview.appspot.com/40100/show
[6] http://psf.upfronthosting.co.za/roundup/meta/issue249
[7] http://psf.upfronthosting.co.za/roundup/meta/issue267
[8] http://psf.upfronthosting.co.za/roundup/meta/issue258
[9] http://psf.upfronthosting.co.za/roundup/meta/issue266
[10] http://psf.upfronthosting.co.za/roundup/meta/issue258
[11] http://psf.upfronthosting.co.za/roundup/meta/issue245
[12] http://psf.upfronthosting.co.za/roundup/meta/issue155
[13] http://psf.upfronthosting.co.za/roundup/meta/issue246
[14] http://bot.bio.br/python-dev-exp/issu...@template=feed
___
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
Re: [Python-Dev] RELEASED Python 2.6.2
On Apr 16, 2009, at 11:17 PM, Ronald Oussoren wrote: On 16 Apr, 2009, at 20:58, Russell Owen wrote: I installed the Mac binary on my Intel 10.5.6 system and it works, except it still uses Apple's system Tcl/Tk 8.4.7 instead of my ActiveState 8.4.19 (which is in /Library/Frameworks where one would expect). That's very string. I had ActiveState 8.4 installed (whatever was current about a month ago). I agree. (For what it's worth, you probably have Tcl/Tk 8.4.19 -- a version I've found to be very robust. 8.4.19 was released awhile ago and is probably the last version of 8.4 we will see, since all development is happening on 8.5 now). Could you try a simple experiment (assuming you still have ActiveState Tcl/Tk installed): run python from the command line and enter these commands: import Tkinter root = Tkinter.Tk() Then go to the application that comes up and select About Tcl/Tk... (in the Python menu) and see what version it reports. When I run with the Mac binary of 2.6.2 it reports 8.4.7 (Apple's built-in python). When I build python 2.6.2 from source it reports 8.4.19 (my ActiveState Tclc/Tk). Just out of curiosity: which 3rd party Tcl/Tk did you have installed when you made the installer? Perhaps if it was 8.5 that would explain it. If so I may try updating my Tcl/Tk -- I've been wanting some of the bug fixes in 8.5 anyway. Tcl 8.5 won't happen in 2.6, and might not happen in 2.7 either. Tkinter needs to work with the system version of Tcl, which is some version of 8.4, Tkinter will not work when the major release of Tcl is different than during the compile. That makes it rather hard to support both 8.4 and 8.5 in the same installer. Perfect. I agree. -- Russell ___ 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
[Python-Dev] Summary of Python tracker Issues
ACTIVITY SUMMARY (04/10/09 - 04/17/09) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue number. Do NOT respond to this message. open (+37) / 15383 closed (+12) / 17605 total (+49) Open issues with patches: 852 Average duration of open issues: 642 days. Median duration of open issues: 393 days. Open Issues Breakdown open 2168 (+37) pending54 ( +0) Issues Created Or Reopened (50) ___ ignore py3_test_grammar.py syntax error 04/11/09 CLOSED http://bugs.python.org/issue5733reopened benjamin.peterson BufferedRWPair broken04/11/09 http://bugs.python.org/issue5734created bquinlan patch Segfault when loading not recompiled module 04/11/09 http://bugs.python.org/issue5735created chin patch, needs review Add the iterator protocol to dbm modules 04/11/09 http://bugs.python.org/issue5736created akitada patch add Solaris errnos 04/11/09 http://bugs.python.org/issue5737created mahrens easy multiprocessing example wrong04/11/09 http://bugs.python.org/issue5738created yaneurabeya Language reference is ambiguous regarding next() method lookup 04/12/09 http://bugs.python.org/issue5739created ncoghlan multiprocessing.connection.Client API documentation incorrect04/12/09 http://bugs.python.org/issue5740created yaneurabeya SafeConfigParser incorrectly detects lone percent signs 04/12/09 CLOSED http://bugs.python.org/issue5741created marcio inspect.findsource() should look only for sources04/12/09 http://bugs.python.org/issue5742created hdima patch multiprocessing.managers not accessible even though docs say so 04/12/09 CLOSED http://bugs.python.org/issue5743created yaneurabeya multiprocessing.managers.BaseManager.connect example typos 04/12/09 CLOSED http://bugs.python.org/issue5744reopened quiver email document update (more links) 04/13/09 CLOSED http://bugs.python.org/issue5745created ocean-city patch socketserver problem upon disconnection (undefined member) 04/13/09 CLOSED http://bugs.python.org/issue5746created eblond knowing the parent command 04/13/09 http://bugs.python.org/issue5747created tarek Objects/bytesobject.c should include stringdefs.h, instead of de 04/13/09 http://bugs.python.org/issue5748created eric.smith easy Allow bin() to have an optional "Total Bits" argument. 04/14/09 CLOSED http://bugs.python.org/issue5749created MechPaul weird seg fault 04/14/09 CLOSED http://bugs.python.org/issue5750created utilitarian Typo in documentation of print function parameters 04/14/09 http://bugs.python.org/issue5751created nicolasg
Re: [Python-Dev] Python-Dev Digest, Vol 69, Issue 143
On Fri, Apr 17, 2009 at 3:58 PM, Scott David Daniels
wrote:
> Non-associativity is what makes for floating point headaches.
> To my knowledge, floating point is at least commutative.
Well, mostly. :-)
>>> from decimal import Decimal
>>> x, y = Decimal('NaN123'), Decimal('-NaN456')
>>> x + y
Decimal('NaN123')
>>> y + x
Decimal('-NaN456')
Similar effects can happen with regular IEEE 754 binary doubles,
but Python doesn't expose NaN payloads or signs, so we don't
see those effects witihin Python.
Mark
___
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
Re: [Python-Dev] Python-Dev Digest, Vol 69, Issue 143
Greg Ewing wrote:
Steven D'Aprano wrote:
it should be obvious in the same way that string concatenation is
different from numerical addition:
1 + 2 = 2 + 1
'1' + '2' != '2' + '1'
However, the proposed arithmetic isn't just non-
commutative, it's non-associative, which is a
much rarer and more surprising thing. We do
at least have
('1' + '2') + '3' == '1' + ('2' + '3')
But we don't have:
(1e40 + -1e40) + 1 == 1e40 + (-1e40 + 1)
Non-associativity is what makes for floating point headaches.
To my knowledge, floating point is at least commutative.
--Scott David Daniels
scott.dani...@acm.org
___
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
Re: [Python-Dev] Issue5434: datetime.monthdelta
>> "2rd of March on leap years, > ^^^ > The turd of March? Yeah, it's from a little known Shakespearean play about a benevolent dictator, Guidius van Rossumus. The name of the play escapes me at the moment, but there's this critical scene where the BDFL is in mortal danger because of ongoing schemes by the members of the PSU. His one true friend and eventual replacement, Barius Warsawvius, known as the FLUFL, tries to warn him surreptitiously about the dangers lurking all about. Barius utters this immortal quote, "Beware the Turd of March." Unfortunately, the drama of that scene tends to be lost on modern audiences. Upon hearing that famous utterance they tend to break out in laughter, especially if the audience is made up mostly of boys under the age of twelve. -- Skip Montanaro - s...@pobox.com - http://www.smontanaro.net/ "XML sucks, dictionaries rock" - Dave Beazley ___ 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
Re: [Python-Dev] RELEASED Python 2.6.2
On Apr 17, 2009, at 5:42 AM, Piet van Oostrum wrote: Maybe a link to the MacOSX image can also be added to http://www.python.org/download Done. -Barry PGP.sig Description: This is a digitally signed message part ___ 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
Re: [Python-Dev] RELEASED Python 2.6.2
> Barry Warsaw (BW) wrote: >BW> On behalf of the Python community, I'm happy to announce the availability >BW> of Python 2.6.2. This is the latest production-ready version in the >BW> Python 2.6 series. Dozens of issues have been fixed since Python 2.6.1 >BW> was released back in December. Please see the NEWS file for all the gory >BW> details. >BW> http://www.python.org/download/releases/2.6.2/NEWS.txt >BW> For more information on Python 2.6 in general, please see >BW> http://docs.python.org/dev/whatsnew/2.6.html >BW> Source tarballs, Windows installers, and (soon) Mac OS X disk images can >BW> be downloaded from the Python 2.6.2 page: >BW> http://www.python.org/download/releases/2.6.2/ Maybe a link to the MacOSX image can also be added to http://www.python.org/download -- Piet van Oostrum URL: http://pietvanoostrum.com [PGP 8DAE142BE17999C4] Private email: p...@vanoostrum.org ___ 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
Re: [Python-Dev] Issue5434: datetime.monthdelta
James Y Knight fuhm.net> writes: > > It's a human-interface operation, and as such, everyone (ahem) "knows > what it means" to say "2 months from now", but the details don't > usually have to be thought about too much. I don't think it's true. When you say "2 months from now", some people will think "9 weeks from now" (or "10 weeks from now"), others "60 days from now", and yet other will think of the meaning this proposal gives it. That's why, when scheduling a meeting, you don't say "2 months from now". You give a precise date instead, because you know otherwise people wouldn't show up on the same day. Regards Antoine. ___ 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
Re: [Python-Dev] Issue5434: datetime.monthdelta
Jess Austin gmail.com> writes: > > I have worked in utility/telecom billing, and needed to examine large > numbers of invoice dates, fulfillment dates, disconnection dates, > payment dates, collection event dates, etc. There would often be > particular rules for the relationships among these dates, and since > many companies generate invoices every day of the month, you couldn't > rely on rules like "this always happens on the 5th". But, as you say, these are /particular rules/. Why do you think they would be the same in another industry, or even another telecom company? Why should they be integrated in Python's standard distribution? ___ 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
Re: [Python-Dev] Issue5434: datetime.monthdelta
-On [20090417 04:55], s...@pobox.com (s...@pobox.com) wrote: >Again, I think it needs to bake a bit. I understand the desire and need for >doing date arithmetic with months. Python is mature enough though that I >don't think you can just "toss this in". It should be available as a module >outside of Python so people can beat on it, flush out bugs, make suggestions >for enhancements, whatever. I think people should look at mx.DateTime a bit, including its documentation. -- Jeroen Ruigrok van der Werven / asmodai イェルーン ラウフロック ヴァン デル ウェルヴェン http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B To do injustice is more disgraceful than to suffer it... ___ 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
Re: [Python-Dev] Issue5434: datetime.monthdelta
On 2009-04-16 21:55, s...@pobox.com wrote: Jess> If, on the other hand, one of the committers wants to toss this in Jess> at some point, whether now or 3 versions down the road, the patch Jess> is up at bugs.python.org (and I'm happy to make any suggested Jess> modifications). Again, I think it needs to bake a bit. I understand the desire and need for doing date arithmetic with months. Python is mature enough though that I don't think you can just "toss this in". It should be available as a module outside of Python so people can beat on it, flush out bugs, make suggestions for enhancements, whatever. I believe you mentioned putting it up on PyPI. I think that's an excellent idea. I've used parts of Gustavo Niemeyer's dateutil package for a couple years and love it. It's widely used. Adding it to dateutil seems like another possibility. That would guarantee an instant user base. From there, if it is found to be useful it could make the leap to be part of the datetime module. dateutil.relativedelta appears to do everything monthdelta does and more in a general way. Adding monthdelta to dateutil doesn't seem to make much sense. -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco ___ 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
