From jim at well.com Thu Apr 1 01:58:53 2010 From: jim at well.com (jim) Date: Wed, 31 Mar 2010 15:58:53 -0800 Subject: [Baypiggies] call for PyCon reminiscences Message-ID: <1270079933.6542.6.camel@jim-laptop> If you went to PyCon last month, tell us about it at our April meeting (20100423), the fourth thursday of the month. Please RSVP, too, so we know who'll be speaking. The amount of time you get is negotiable, depending on how much you need to deliver the info, how many others may also be talking.... Hopefully, jim From rami.chowdhury at gmail.com Thu Apr 1 05:45:41 2010 From: rami.chowdhury at gmail.com (Rami Chowdhury) Date: Wed, 31 Mar 2010 20:45:41 -0700 Subject: [Baypiggies] Slightly OT: *lightweight* Javascript frameworks? Message-ID: <201003312045.42074.rami.chowdhury@gmail.com> Hey all, Very slightly OT -- hope you'll bear with me. I really enjoyed the discussion on here a few months back about client-side web applications and comparisons of various frameworks. I was wondering if I might be able to leverage some of that knowledge base and kick off an interesting discussion at the same time. A client of mine is looking to add Javascript effects, transitions, and AJAX functionality to their web application. The kicker? It's a mobile-oriented web app -- so small code size is key. Even minified and gzipped, most of the popular frameworks are pretty heavy from that point of view. Any thoughts? Thanks in advance, Rami ---- Rami Chowdhury "Passion is inversely proportional to the amount of real information available." -- Benford's Law of Controversy 408-597-7068 (US) / 07875-841-046 (UK) / 01819-245544 (BD) From alecf at flett.org Thu Apr 1 05:56:04 2010 From: alecf at flett.org (Alec Flett) Date: Wed, 31 Mar 2010 20:56:04 -0700 Subject: [Baypiggies] Slightly OT: *lightweight* Javascript frameworks? In-Reply-To: <201003312045.42074.rami.chowdhury@gmail.com> References: <201003312045.42074.rami.chowdhury@gmail.com> Message-ID: jQuery is really not that heavy - something like 24k minified and gzipped, and there are a lot of tiny plugins that will get you specific effects. jQueryUI is slightly more heavyweight, but you can pick and choose at which parts of the package you actually need. Honestly I wouldn't worry about serving up to 100k of JS (minified and gzipped of course) to any iPhone or Android-based web browser... so unless you're talking about some strange mobile platform, jQuery + jQueryUI is a pretty easy choice. Alec On Wed, Mar 31, 2010 at 8:45 PM, Rami Chowdhury wrote: > Hey all, > > Very slightly OT -- hope you'll bear with me. I really enjoyed the > discussion on > here a few months back about client-side web applications and comparisons > of > various frameworks. I was wondering if I might be able to leverage some of > that > knowledge base and kick off an interesting discussion at the same time. > > A client of mine is looking to add Javascript effects, transitions, and > AJAX > functionality to their web application. The kicker? It's a mobile-oriented > web > app -- so small code size is key. Even minified and gzipped, most of the > popular > frameworks are pretty heavy from that point of view. Any thoughts? > > Thanks in advance, > Rami > > ---- > Rami Chowdhury > "Passion is inversely proportional to the amount of real information > available." > -- Benford's Law of Controversy > 408-597-7068 (US) / 07875-841-046 (UK) / 01819-245544 (BD) > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > http://mail.python.org/mailman/listinfo/baypiggies > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rami.chowdhury at gmail.com Thu Apr 1 06:15:35 2010 From: rami.chowdhury at gmail.com (Rami Chowdhury) Date: Wed, 31 Mar 2010 21:15:35 -0700 Subject: [Baypiggies] Slightly OT: *lightweight* Javascript frameworks? In-Reply-To: References: <201003312045.42074.rami.chowdhury@gmail.com> Message-ID: <201003312115.36090.rami.chowdhury@gmail.com> On Wednesday 31 March 2010 21:06:05 Lee Hinde wrote: > On Wed, Mar 31, 2010 at 8:45 PM, Rami Chowdhury wrote: > > Hey all, > > > > Very slightly OT -- hope you'll bear with me. I really enjoyed the > > discussion on here a few months back about client-side web applications > > and comparisons of various frameworks. I was wondering if I might be > > able to leverage some of that knowledge base and kick off an interesting > > discussion at the same time. > > > > A client of mine is looking to add Javascript effects, transitions, and > > AJAX functionality to their web application. The kicker? It's a > > mobile-oriented web app -- so small code size is key. Even minified and > > gzipped, most of the popular frameworks are pretty heavy from that point > > of view. Any thoughts? > > > > Thanks in advance, > > Rami > > http://www.jqtouch.com/ Ooh, that does look interesting -- only 24k minified and gzipped, might be worth suggesting. Thank you! ---- Rami Chowdhury "It always takes longer than you expect, even when you take Hofstadter's Law into account." -- Hofstadter's Law 408-597-7068 (US) / 07875-841-046 (UK) / 01819-245544 (BD) From glen at glenjarvis.com Thu Apr 1 20:54:55 2010 From: glen at glenjarvis.com (Glen Jarvis) Date: Thu, 1 Apr 2010 11:54:55 -0700 Subject: [Baypiggies] Contracting in Python Message-ID: One of the things I've noticed more and more as I meet people in this community is that either have a large number of our members contracting at places, or others trying to contract but don't know how. It's amazing how many people I discover that have been doing this for years. I am not volunteering to put a workshop together (I can't keep up with my own contracts right now, much less help anyone else). But, I think that is something that would be a great idea if someone is interested. I had tried (offline) to put together something like this at the beginning of this year. I even had (still could get) a business developer speaker to speak (without charging us) about some business topics. I just couldn't get a business-like-setting/space for our meetings. I wasn't confident enough to advertise the event because I wasn't certain we could get an adequate space. So, I let it go. Someone else may have better luck. The second thing I've noticed is that some of our work is with front-end technologies. I personally would rather contract out the CSS and JavaScript work to someone else - just so I can focus on one thing. I have a co-worker who really enjoys the JavaScript and CSS type work. If we all got together, physically in the same location, to work on our projects on a Saturday; and if we invited him, would anyone else have work for him? He may be interested in doing this if we can get enough work for him (and if he has the free time). It'd have to be worthwhile for him. Glen Disclaimer: This email does not constitute a time commitment of any kind on Glen's behalf. He's only beginning a conversation to see what the responses may be. ---- Whatever you can do or imagine, begin it; boldness has beauty, magic, and power in it. -- Goethe -------------- next part -------------- An HTML attachment was scrubbed... URL: From jim at well.com Thu Apr 1 23:44:23 2010 From: jim at well.com (jim) Date: Thu, 01 Apr 2010 13:44:23 -0800 Subject: [Baypiggies] Contracting in Python In-Reply-To: References: Message-ID: <1270158263.31553.55.camel@jim-laptop> "I even had (still could get) a business developer speaker to speak (without charging us) about some business topics." (gasp!) Do that! That's one of the (languishing) possible ideas for a bayPIGgies topic. On Thu, 2010-04-01 at 11:54 -0700, Glen Jarvis wrote: > One of the things I've noticed more and more as I meet people in this > community is that either have a large number of our members > contracting at places, or others trying to contract but don't know > how. It's amazing how many people I discover that have been doing this > for years. > > I am not volunteering to put a workshop together (I can't keep up with > my own contracts right now, much less help anyone else). But, I think > that is something that would be a great idea if someone is interested. > I had tried (offline) to put together something like this at the > beginning of this year. I even had (still could get) a business > developer speaker to speak (without charging us) about some business > topics. I just couldn't get a business-like-setting/space for our > meetings. I wasn't confident enough to advertise the event because I > wasn't certain we could get an adequate space. So, I let it go. > Someone else may have better luck. > > The second thing I've noticed is that some of our work is with > front-end technologies. I personally would rather contract out the CSS > and JavaScript work to someone else - just so I can focus on one > thing. > > I have a co-worker who really enjoys the JavaScript and CSS type work. > If we all got together, physically in the same location, to work on > our projects on a Saturday; and if we invited him, would anyone else > have work for him? He may be interested in doing this if we can get > enough work for him (and if he has the free time). It'd have to be > worthwhile for him. > > Glen > > Disclaimer: This email does not constitute a time commitment of any > kind on Glen's behalf. He's only beginning a conversation to see what > the responses may be. > ---- > Whatever you can do or imagine, begin it; > boldness has beauty, magic, and power in it. > > -- Goethe > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > http://mail.python.org/mailman/listinfo/baypiggies From glen at glenjarvis.com Fri Apr 2 00:29:31 2010 From: glen at glenjarvis.com (Glen Jarvis) Date: Thu, 1 Apr 2010 15:29:31 -0700 Subject: [Baypiggies] Contracting in Python In-Reply-To: <1270158263.31553.55.camel@jim-laptop> References: <1270158263.31553.55.camel@jim-laptop> Message-ID: I met my speaker at a Small Business Association SBA course in the past. I originally heard her speak on making the 'elevator' pitch -- showing people what you do in just a few moments (There is a lot of work that can go into this for it to be effective). She is *really* good at sales and is a small business coach -- she bugs the heck out of you until you do all the things that you said you'd do :) I don't know how she'd be for a full BayPIGgies talk.. Howeeeverrrr..... If we did mini talks -- with the theme of how to be a Python Contractor... where we have different people talking about different aspects of this..... she'd definitely be able to talk about the elevator pitch. I can talk about IRS rules, 1099s, QuickBooks, Elance, Legal entities (Sole proprietorship, LLCs...) etc. But, I'm far from an expert -- I figured things out by taking a ton of free SBA classes, making mistakes and working with *very* kind and patient BayPIGgies. I'm afraid I put E through hell because I was so new at so many things and I bike-shed'ed way too much... :( I think I even cost him a little bit more money than they intended when a project was going over budget and I didn't know how to get it in budget :( I also was trying so hard to prove myself, I was getting in my own way and theirs too :( They were so awesome about the whole thing though :) Expert or not, I can definitely share my experiences and my mistakes... However, I bet it's not necessary. I can name *so* many independent contractors off this list that make their sole money doing this (more than I can name people who actually work for companies).... And, I bet they may want to share a thing or two.. *nudge* *nudge* :) Are there other speakers who would speak? Is a "How to be a Python Contractor" a viable theme for a BayPIGgies night? Is this what you mean by (languishing) possible ideas for BayPIGgies topics? Cheers, Glen On Thu, Apr 1, 2010 at 2:44 PM, jim wrote: > > > "I even had (still could get) a business developer speaker to speak > (without charging us) about some business topics." > > (gasp!) Do that! That's one of the (languishing) possible > ideas for a bayPIGgies topic. > > > > > On Thu, 2010-04-01 at 11:54 -0700, Glen Jarvis wrote: > > One of the things I've noticed more and more as I meet people in this > > community is that either have a large number of our members > > contracting at places, or others trying to contract but don't know > > how. It's amazing how many people I discover that have been doing this > > for years. > > > > I am not volunteering to put a workshop together (I can't keep up with > > my own contracts right now, much less help anyone else). But, I think > > that is something that would be a great idea if someone is interested. > > I had tried (offline) to put together something like this at the > > beginning of this year. I even had (still could get) a business > > developer speaker to speak (without charging us) about some business > > topics. I just couldn't get a business-like-setting/space for our > > meetings. I wasn't confident enough to advertise the event because I > > wasn't certain we could get an adequate space. So, I let it go. > > Someone else may have better luck. > > > > The second thing I've noticed is that some of our work is with > > front-end technologies. I personally would rather contract out the CSS > > and JavaScript work to someone else - just so I can focus on one > > thing. > > > > I have a co-worker who really enjoys the JavaScript and CSS type work. > > If we all got together, physically in the same location, to work on > > our projects on a Saturday; and if we invited him, would anyone else > > have work for him? He may be interested in doing this if we can get > > enough work for him (and if he has the free time). It'd have to be > > worthwhile for him. > > > > Glen > > > > Disclaimer: This email does not constitute a time commitment of any > > kind on Glen's behalf. He's only beginning a conversation to see what > > the responses may be. > > ---- > > Whatever you can do or imagine, begin it; > > boldness has beauty, magic, and power in it. > > > > -- Goethe > > _______________________________________________ > > Baypiggies mailing list > > Baypiggies at python.org > > To change your subscription options or unsubscribe: > > http://mail.python.org/mailman/listinfo/baypiggies > > -- Glen ---- Whatever you can do or imagine, begin it; boldness has beauty, magic, and power in it. -- Goethe -------------- next part -------------- An HTML attachment was scrubbed... URL: From cappy2112 at gmail.com Sat Apr 3 03:30:05 2010 From: cappy2112 at gmail.com (Tony Cappellini) Date: Fri, 2 Apr 2010 18:30:05 -0700 Subject: [Baypiggies] Fwd: UG News: Discount for O'Reilly Open Source Convention (OSCON) In-Reply-To: <1270162818.6730.0.495071@post.oreilly.com> References: <1270162818.6730.0.495071@post.oreilly.com> Message-ID: If you would like to view this information in your browser, click here . [image: O'Reilly] Forward this announcement Hi, OSCON Registration is open. Here's a discount you can pass along to your members through your mailing list or at your meetings: OSCON happens July 19-23, 2010 in Portland, OR Use code "os10usrg" when you register, and receive 20% off the registration price. To register for the conference, go to http://oreil.ly/osconug2010 At OSCON, you'll participate in hundreds of sessions covering open source languages and platforms, practical tutorials that go deep into technical skill and best practices, inspirational keynote presentations, an Expo Hall featuring dozens of the latest projects and products, fun networking events and activities, and the best "hallway track" around. - Explore the benefits and challenges of building scalable applications for the cloud - Use open source to target Android, iPhone and other mobile platforms - Understand how and when to use NoSQL databases - Learn best practices from experts in Python, Java, Ruby, Perl, PHP and JavaScript - Use open source effectively as part of your business strategy - Learn how to foster contribution and adoption of your open source projects Follow OSCON on your favorite social networking sites: Facebook Twitter(or look for #OSCON) LinkedIn Hope to see you there, Marsee Henon [image: Spreading the knowledge of innovators][image: oreilly.com] -------------- next part -------------- An HTML attachment was scrubbed... URL: From glen at glenjarvis.com Sun Apr 4 02:42:56 2010 From: glen at glenjarvis.com (Glen Jarvis) Date: Sat, 3 Apr 2010 17:42:56 -0700 Subject: [Baypiggies] Reminder: SHDH next weekend Message-ID: Although I probably won't have time to go (I haven't gone in over a year), here's a reminder for SHDH next weekend. I've seen a lot of Python hacking (and all kinds of fun geeking) at these before: Greetings fellow Dwarves, Eagles, Elves, Ents, Hobbits, Men, and Tom Bombadil, We are calling the fellowship together once again, this time in the shire of Palantir in Palo Alto. So get your robes and wizard hats ready! SuperHappyDevHouse37. Saturday April 10, 2010. 151 University Ave, Palo Alto, CA 94301. 2pm-12am. The Palo Alto CalTrain station is only one block away! Come and check out one of the old Facebook buildings, bring your laptops, friends, ideas and projects. If you live in San Francisco, or San Jose, you can't use the excuse that this is too far away! If you've never been before, why not? It's free, there's food and caffeine, and smart people. How can you say no? Come and check it out! If your friends are difficult to convince, perhaps you should read http://superhappydevhouse.org/HowToInviteFriends. If you would like to tell your fellow hackers about something you think is cool, remember ot obey Timothy and head over to http://superhappydevhouse.org/LightningTalks If you're thinking of coming, let everyone know by posting your name and vague plans to http://superhappydevhouse.org/SuperHappyDevHouse37 Hope to see you there! The DevHouse Crew RSVP Facebook @ http://www.facebook.com/event.php?eid=111202598897403 RSVP Upcoming @ http://upcoming.yahoo.com/event/5650530 Glen -- Whatever you can do or imagine, begin it; boldness has beauty, magic, and power in it. -- Goethe -------------- next part -------------- An HTML attachment was scrubbed... URL: From smcbutler at gmail.com Mon Apr 5 18:25:53 2010 From: smcbutler at gmail.com (Simon Butler) Date: Mon, 5 Apr 2010 09:25:53 -0700 Subject: [Baypiggies] Python/Django linux build consultant required Message-ID: Hi, we are a San Francisco based startup company and are looking for a Python/Django person to help us roll out a close-to-completion IC Design tool application. We're looking for 5 years + Python experience with a knowledge of tools such as pyinstall (or other build systems). Please contact me directly if interested. Rgds. -- Simon Butler: -------------- next part -------------- An HTML attachment was scrubbed... URL: From jim at well.com Tue Apr 6 18:11:32 2010 From: jim at well.com (jim) Date: Tue, 06 Apr 2010 09:11:32 -0700 Subject: [Baypiggies] call for PyCon reports Message-ID: <1270570292.6552.62.camel@jim-laptop> If you went to this year's PyCon, respond if you can report about what impressed you at this month's BayPiggies meeting (April 22). From fperez.net at gmail.com Fri Apr 9 02:34:42 2010 From: fperez.net at gmail.com (Fernando Perez) Date: Thu, 8 Apr 2010 17:34:42 -0700 Subject: [Baypiggies] ANN: April 14 talk at UC Berkeley Message-ID: Hi all, a reminder of next week's talk: April 14, 2pm: Cerebral blood flow simulation -- A SEJITS friendly Python Framework. By: Meriem Ben Salah, Phd. Student, Department of Mechanical Engineering, University of California Berkeley. http://me.berkeley.edu/~bensalah/ Where: 508-20 Evans Hall (5th floor) More information about the UC Berkeley Py4Science meetings: https://cirl.berkeley.edu/view/Py4Science I'd greatly appreciate it if you could forward this announcement to colleagues who could find it interesting. Regards, f From alecf at flett.org Fri Apr 9 20:11:42 2010 From: alecf at flett.org (Alec Flett) Date: Fri, 9 Apr 2010 11:11:42 -0700 Subject: [Baypiggies] Freebase meetup/bootcamp Wednesday 4/14 W Message-ID: Some of you may have heard of freebase.com - basically a giant open (CC-BY) database with a public API with supports for very deep queries (i.e. complex joins in the SQL world, but we're not SQL) We're a big python shop, and have a python library for accessing the RESTful API that I maintain at http://code.google.com/p/freebase-python/ I'm giving a "bootcamp" on MQL (our query language used in the API) at this month's meetup in San Francisco... Anyway, just thought there might be some Baypiggies overlap, and the MQL bootcamp should be a great introduction for folks who've never used it, or only used it a little bit. If this sounds interesting, please drop by (and RSVP so you can get in the building....) http://www.meetup.com/sf-freebase/calendar/12845548/ Also, if you've heard any noise about Gridworks ( http://blog.freebase.com/2010/03/26/preview-freebase-gridworks/) one of the authors will be demoing that as well - a really amazing project, though not specifically python related. Alec -------------- next part -------------- An HTML attachment was scrubbed... URL: From jim at well.com Fri Apr 9 21:01:39 2010 From: jim at well.com (jim) Date: Fri, 09 Apr 2010 12:01:39 -0700 Subject: [Baypiggies] Freebase meetup/bootcamp Wednesday 4/14 W In-Reply-To: References: Message-ID: <1270839699.6749.103.camel@jim-laptop> are you interested in pitching your talk to the baypiggies meeting? any month, including this month (thursday april 22), is open. hopefully, jim or baypiggies On Fri, 2010-04-09 at 11:11 -0700, Alec Flett wrote: > Some of you may have heard of freebase.com - basically a giant open > (CC-BY) database with a public API with supports for very deep queries > (i.e. complex joins in the SQL world, but we're not SQL) > > > We're a big python shop, and have a python library for accessing the > RESTful API that I maintain > at http://code.google.com/p/freebase-python/ > > > I'm giving a "bootcamp" on MQL (our query language used in the > API) at this month's meetup in San Francisco... > > > Anyway, just thought there might be some Baypiggies overlap, and the > MQL bootcamp should be a great introduction for folks who've never > used it, or only used it a little bit. > > > If this sounds interesting, please drop by (and RSVP so you can get in > the building....) > > > http://www.meetup.com/sf-freebase/calendar/12845548/ > > > Also, if you've heard any noise about Gridworks > (http://blog.freebase.com/2010/03/26/preview-freebase-gridworks/) one > of the authors will be demoing that as well - a really amazing > project, though not specifically python related. > > > Alec > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > http://mail.python.org/mailman/listinfo/baypiggies From aahz at pythoncraft.com Tue Apr 13 16:28:20 2010 From: aahz at pythoncraft.com (Aahz) Date: Tue, 13 Apr 2010 07:28:20 -0700 Subject: [Baypiggies] FWD: OpenHatch: Find ways to contribute to open source (including Python itself) Message-ID: <20100413142820.GB8456@panix.com> ----- Forwarded message from Asheesh Laroia ----- > Date: Mon, 12 Apr 2010 16:47:08 -0400 (EDT) > From: Asheesh Laroia > To: python-announce-list at python.org > Subject: OpenHatch: Find ways to contribute to open source (including Python > itself) > Reply-To: python-list at python.org > Newsgroups: comp.lang.python.announce > > Hi all! I'm happy to announce the new version of the OpenHatch volunteer > opportunity finder. > > Volunteer opportunity finder > ---------------------------- > > Looking for a way to get involved in open source, but don't know where to > start? Try browsing bugs in the OpenHatch volunteer opportunity finder: > https//openhatch.org/search/ > > At PyCon, I led an open space where some of us tried finding things to > work on. We found "easy" documentation bugs in Python, and wrote up > patches. Within a few weeks, our patches were comitted to the Python > core. > > Contributors to hundreds of projects (including Python itself) label bugs > as good for new contributors. Those bugs are an opportunity for you to > find a new project to contribute to in open source, so try browsing them > at https://openhatch.org/search/?q=&toughness=bitesize > > Do you run an open source project? You can add your project to our index > by clicking "Add a bug tracker." If you want to get new contributors more > easily, try tagging bugs in your bug tracker as "bitesize."We're always > looking for more projects to include in our crawls. > > About OpenHatch > --------------- > > We're a website for helping people find ways to get involved in free, > open source software. We also run a profile engine where you can tell > your story in open source, emphasizing all the ways you've been involved > in projects. (Successful open source projects take more than just code!) > > For more info > ------------- > > Keep in touch by: > > * Joining #openhatch on irc.freenode.net > * Replying to me and getting on our announcements list > * Subscribing to @openhatchery on Twitter/Identi.ca > * Reading our blog at https://openhatch.org/blog/ > > Or grab our source code: https://openhatch.org/source-code-etc/ > > -- Asheesh. > > -- > ... bacteriological warfare ... hard to believe we were once foolish > enough to play around with that. > -- McCoy, "The Omega Glory", stardate unknown > ----- End forwarded message ----- -- Aahz (aahz at pythoncraft.com) <*> http://www.pythoncraft.com/ "It is easier to optimize correct code than to correct optimized code." --Bill Harlan From bpederse at gmail.com Wed Apr 14 17:20:59 2010 From: bpederse at gmail.com (Brent Pedersen) Date: Wed, 14 Apr 2010 08:20:59 -0700 Subject: [Baypiggies] a python puzzle Message-ID: hi, in trying to write a func that does a kind of merging of 2 sorted lists, i've come up with a fairly simple implementation that "almost works": http://gist.github.com/365485 but it hits StopIteration before returning the last value ([9], None) i can wrap the whole thing in a bunch more if statements, i've tried heapq.merge, but cant find a nice solution. any ideas? i think it's an interesting problem. -brent From bpederse at gmail.com Wed Apr 14 18:04:57 2010 From: bpederse at gmail.com (Brent Pedersen) Date: Wed, 14 Apr 2010 09:04:57 -0700 Subject: [Baypiggies] a python puzzle In-Reply-To: References: Message-ID: On Wed, Apr 14, 2010 at 8:20 AM, Brent Pedersen wrote: > hi, in trying to write a func that does a kind of merging of 2 sorted lists, > i've come up with a fairly simple implementation that "almost works": > http://gist.github.com/365485 > > but it hits StopIteration before returning the last value ([9], None) > i can wrap the whole thing in a bunch more if statements, i've tried > heapq.merge, but cant find a nice solution. > > any ideas? i think it's an interesting problem. > -brent > i should add the for my real use-case, the iterables going in will not be lists, they'll be lazily generated, and very large, so i dont want to read them into memory to get the last element or slice them. From emile at fenx.com Wed Apr 14 18:03:40 2010 From: emile at fenx.com (Emile van Sebille) Date: Wed, 14 Apr 2010 09:03:40 -0700 Subject: [Baypiggies] a python puzzle In-Reply-To: References: Message-ID: <4BC5E75C.1000502@fenx.com> a = [1, 1, 2, 4, 6, 8, 9] b = [1, 3, 4, 5, 6, 7, 8] def popwhile(l,t): r = [] while l[:1] == t: r.append(l.pop(0)) return r while bool(a or b): m = min(a[:1],b[:1]) or max(a[:1],b[:1]) print popwhile(a,m), popwhile(b,m) Emile On 4/14/2010 8:20 AM Brent Pedersen said... > hi, in trying to write a func that does a kind of merging of 2 sorted lists, > i've come up with a fairly simple implementation that "almost works": > http://gist.github.com/365485 > > but it hits StopIteration before returning the last value ([9], None) > i can wrap the whole thing in a bunch more if statements, i've tried > heapq.merge, but cant find a nice solution. > > any ideas? i think it's an interesting problem. > -brent > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > http://mail.python.org/mailman/listinfo/baypiggies > From aahz at pythoncraft.com Wed Apr 14 18:11:01 2010 From: aahz at pythoncraft.com (Aahz) Date: Wed, 14 Apr 2010 09:11:01 -0700 Subject: [Baypiggies] a python puzzle In-Reply-To: References: Message-ID: <20100414161101.GA24357@panix.com> On Wed, Apr 14, 2010, Brent Pedersen wrote: > > hi, in trying to write a func that does a kind of merging of 2 sorted lists, > i've come up with a fairly simple implementation that "almost works": Please describe in more detail what you're trying to do and give examples of inputs and expected outputs. -- Aahz (aahz at pythoncraft.com) <*> http://www.pythoncraft.com/ "It is easier to optimize correct code than to correct optimized code." --Bill Harlan From glen at glenjarvis.com Wed Apr 14 18:19:21 2010 From: glen at glenjarvis.com (Glen Jarvis) Date: Wed, 14 Apr 2010 09:19:21 -0700 Subject: [Baypiggies] a python puzzle In-Reply-To: References: Message-ID: Zip, or anything it itertools doesn't do what you need? Glen On Apr 14, 2010, at 8:20 AM, Brent Pedersen wrote: > hi, in trying to write a func that does a kind of merging of 2 > sorted lists, > i've come up with a fairly simple implementation that "almost works": > http://gist.github.com/365485 > > but it hits StopIteration before returning the last value ([9], None) > i can wrap the whole thing in a bunch more if statements, i've tried > heapq.merge, but cant find a nice solution. > > any ideas? i think it's an interesting problem. > -brent > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > http://mail.python.org/mailman/listinfo/baypiggies From tbelote at tombelote.com Wed Apr 14 18:20:17 2010 From: tbelote at tombelote.com (Thomas Belote) Date: Wed, 14 Apr 2010 09:20:17 -0700 Subject: [Baypiggies] a python puzzle In-Reply-To: References: Message-ID: Here is my solution, change how next works so it is compatible with your while conditions: import itertools def fnext(next): try: return next() except: return False, [] def as_pairs(xs, ys, grouper=lambda _: _): # assume xs and ys are sorted. xgrouper = itertools.groupby(xs, grouper) ygrouper = itertools.groupby(ys, grouper) x, xgroup = fnext(xgrouper.next) y, ygroup = fnext(ygrouper.next) while x or y: if x == y: yield list(xgroup), list(ygroup) try: x, xgroup = fnext(xgrouper.next) y, ygroup = fnext(ygrouper.next) except: traceback.print_exc() elif not y or x < y: yield list(xgroup), None x, xgroup = fnext(xgrouper.next) elif not x or x > y: yield (None, list(ygroup)) y, ygroup = fnext(ygrouper.next) print repr(x) + " or " + repr(y) aordered = [1, 1, 2, 4, 6, 8, 9] bordered = [1, 3, 4, 5, 6, 7, 8] for a, b in as_pairs(aordered, bordered): a, b On Apr 14, 2010, at 8:20 AM, Brent Pedersen wrote: > hi, in trying to write a func that does a kind of merging of 2 sorted lists, > i've come up with a fairly simple implementation that "almost works": > http://gist.github.com/365485 > > but it hits StopIteration before returning the last value ([9], None) > i can wrap the whole thing in a bunch more if statements, i've tried > heapq.merge, but cant find a nice solution. > > any ideas? i think it's an interesting problem. > -brent > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > http://mail.python.org/mailman/listinfo/baypiggies From bpederse at gmail.com Wed Apr 14 18:24:54 2010 From: bpederse at gmail.com (Brent Pedersen) Date: Wed, 14 Apr 2010 09:24:54 -0700 Subject: [Baypiggies] a python puzzle In-Reply-To: <20100414161101.GA24357@panix.com> References: <20100414161101.GA24357@panix.com> Message-ID: On Wed, Apr 14, 2010 at 9:11 AM, Aahz wrote: > On Wed, Apr 14, 2010, Brent Pedersen wrote: >> >> hi, in trying to write a func that does a kind of merging of 2 sorted lists, >> i've come up with a fairly simple implementation that "almost works": > > Please describe in more detail what you're trying to do and give > examples of inputs and expected outputs. > -- > Aahz (aahz at pythoncraft.com) ? ? ? ? ? <*> ? ? ? ? http://www.pythoncraft.com/ > the inputs and outputs are in the doctest. it's similar to zip, except only pairs things that have the same key (as defined by groupby). if there's no pair, return the list associated with the lower key and None) > "It is easier to optimize correct code than to correct optimized code." > --Bill Harlan > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > http://mail.python.org/mailman/listinfo/baypiggies > From glen at glenjarvis.com Wed Apr 14 18:27:21 2010 From: glen at glenjarvis.com (Glen Jarvis) Date: Wed, 14 Apr 2010 09:27:21 -0700 Subject: [Baypiggies] a python puzzle In-Reply-To: References: Message-ID: > i should add the for my real use-case, the iterables going in will not > be lists, they'll be lazily generated, and very large, so > i dont want to read them into memory to get the last element or > slice them I haven't seen the code that you sent (on iPhone now). But, is the izip (for iterables) helpful. It's in itertools. There are some very sharp tools in itertools. I'd be surprised I'd they didn't supply a good deal of the functionality (that I imagine) you are looking for. Cheers, Glen From damonmc at gmail.com Wed Apr 14 18:29:08 2010 From: damonmc at gmail.com (Damon McCormick) Date: Wed, 14 Apr 2010 09:29:08 -0700 Subject: [Baypiggies] a python puzzle In-Reply-To: References: Message-ID: Keeping your original approach, you could define a function like this: def next_or_none_pair (itr): def result_func (): try: return itr.next() except StopIteration: return (None, None) return result_func and then replace your current definitions of xnext and ynext by the following: xnext = next_or_none_pair(itertools.groupby(xs, grouper)) ynext = next_or_none_pair(itertools.groupby(ys, grouper)) The condition of your while loop is already set up to exit when either x or y is None (a condition which, I believe, is currently never True, since the loop ends when StopIteration is thrown). So the only other modification you'd need is that your comparisions between x and y need to handle None: elif y is None or x < y: yield list(xgroup), None x, xgroup = xnext() elif x is None or x > y: yield (None, list(ygroup)) y, ygroup = ynext() So the entire thing would look like this: import itertools def next_or_none_pair (itr): def result_func (): try: return itr.next() except StopIteration: return (None, None) return result_func def as_pairs (xs, ys, grouper=lambda _: _): """ >>> aordered = [1, 1, 2, 4, 6, 8, 9] >>> bordered = [1, 3, 4, 5, 6, 7, 8] >>> for a, b in as_pairs(aordered, bordered): ... a, b ([1, 1], [1]) ([2], None) (None, [3]) ([4], [4]) (None, [5]) ([6], [6]) (None, [7]) ([8], [8]) ([9], None) """ # assume xs and ys are sorted. xnext = next_or_none_pair(itertools.groupby(xs, grouper)) ynext = next_or_none_pair(itertools.groupby(ys, grouper)) import itertools def next_or_none_pair (itr): def result_func (): try: return itr.next() except StopIteration: return (None, None) return result_func def as_pairs (xs, ys, grouper=lambda _: _): """ >>> aordered = [1, 1, 2, 4, 6, 8, 9] >>> bordered = [1, 3, 4, 5, 6, 7, 8] >>> for a, b in as_pairs(aordered, bordered): ... a, b ([1, 1], [1]) ([2], None) (None, [3]) ([4], [4]) (None, [5]) ([6], [6]) (None, [7]) ([8], [8]) ([9], None) """ # assume xs and ys are sorted. xnext = next_or_none_pair(itertools.groupby(xs, grouper)) ynext = next_or_none_pair(itertools.groupby(ys, grouper)) x, xgroup = xnext() y, ygroup = ynext() while x or y: if x == y: yield list(xgroup), list(ygroup) x, xgroup = xnext() y, ygroup = ynext() elif y is None or x < y: yield list(xgroup), None x, xgroup = xnext() elif x is None or x > y: yield (None, list(ygroup)) y, ygroup = ynext() else: assert False if __name__ == "__main__": import doctest doctest.testmod() On Wed, Apr 14, 2010 at 9:04 AM, Brent Pedersen wrote: > On Wed, Apr 14, 2010 at 8:20 AM, Brent Pedersen > wrote: > > hi, in trying to write a func that does a kind of merging of 2 sorted > lists, > > i've come up with a fairly simple implementation that "almost works": > > http://gist.github.com/365485 > > > > but it hits StopIteration before returning the last value ([9], None) > > i can wrap the whole thing in a bunch more if statements, i've tried > > heapq.merge, but cant find a nice solution. > > > > any ideas? i think it's an interesting problem. > > -brent > > > > i should add the for my real use-case, the iterables going in will not > be lists, they'll be lazily generated, and very large, so > i dont want to read them into memory to get the last element or slice them. > ______________________________ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From damonmc at gmail.com Wed Apr 14 18:32:18 2010 From: damonmc at gmail.com (Damon McCormick) Date: Wed, 14 Apr 2010 09:32:18 -0700 Subject: [Baypiggies] a python puzzle In-Reply-To: References: Message-ID: Sorry about the cut-and-paste error. Corrected below. Also, I believe my code is equivalent to Thomas'. -Damon On Wed, Apr 14, 2010 at 9:29 AM, Damon McCormick wrote: > Keeping your original approach, you could define a function like this: > > def next_or_none_pair (itr): > def result_func (): > try: > return itr.next() > except StopIteration: > return (None, None) > return result_func > > and then replace your current definitions of xnext and ynext by the > following: > > xnext = next_or_none_pair(itertools.groupby(xs, grouper)) > ynext = next_or_none_pair(itertools.groupby(ys, grouper)) > > The condition of your while loop is already set up to exit when either x or > y is None (a condition which, I believe, is currently never True, since the > loop ends when StopIteration is thrown). > > So the only other modification you'd need is that your comparisions between > x and y need to handle None: > > elif y is None or x < y: > yield list(xgroup), None > x, xgroup = xnext() > elif x is None or x > y: > yield (None, list(ygroup)) > y, ygroup = ynext() > > So the entire thing would look like this: > > > import itertools > > > def next_or_none_pair (itr): > def result_func (): > try: > return itr.next() > except StopIteration: > return (None, None) > return result_func > > > def as_pairs (xs, ys, grouper=lambda _: _): > > """ > >>> aordered = [1, 1, 2, 4, 6, 8, > 9] > >>> bordered = [1, 3, 4, 5, 6, 7, > 8] > >>> for a, b in as_pairs(aordered, > bordered): > ... a, > b > ([1, 1], > [1]) > ([2], > None) > (None, > [3]) > ([4], > [4]) > (None, > [5]) > ([6], > [6]) > (None, > [7]) > ([8], > [8]) > ([9], > None) > """ > # assume xs and ys are > sorted. > xnext = next_or_none_pair(itertools.groupby(xs, grouper)) > ynext = next_or_none_pair(itertools.groupby(ys, grouper)) > x, xgroup = xnext() > y, ygroup = ynext() > > while x or y: > if x == y: > yield list(xgroup), list(ygroup) > x, xgroup = xnext() > y, ygroup = ynext() > elif y is None or x < y: > yield list(xgroup), None > x, xgroup = xnext() > elif x is None or x > y: > yield (None, list(ygroup)) > y, ygroup = ynext() > else: > assert False > > if __name__ == "__main__": > import doctest > doctest.testmod() > > > > > > On Wed, Apr 14, 2010 at 9:04 AM, Brent Pedersen wrote: > >> On Wed, Apr 14, 2010 at 8:20 AM, Brent Pedersen >> wrote: >> > hi, in trying to write a func that does a kind of merging of 2 sorted >> lists, >> > i've come up with a fairly simple implementation that "almost works": >> > http://gist.github.com/365485 >> > >> > but it hits StopIteration before returning the last value ([9], None) >> > i can wrap the whole thing in a bunch more if statements, i've tried >> > heapq.merge, but cant find a nice solution. >> > >> > any ideas? i think it's an interesting problem. >> > -brent >> > >> >> i should add the for my real use-case, the iterables going in will not >> be lists, they'll be lazily generated, and very large, so >> i dont want to read them into memory to get the last element or slice >> them. >> ______________________________ >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jason at mischievous.org Wed Apr 14 18:24:24 2010 From: jason at mischievous.org (Jason Culverhouse) Date: Wed, 14 Apr 2010 09:24:24 -0700 Subject: [Baypiggies] a python puzzle In-Reply-To: <4BC5E75C.1000502@fenx.com> References: <4BC5E75C.1000502@fenx.com> Message-ID: <516B3767-8EA7-4C95-B7C1-6CA1F968D932@mischievous.org> If the lists are already sorted wouldn't sorted(itertools.chain(a,b)) be fairly efficient? http://bugs.python.org/file4451/timsort.txt Jason On Apr 14, 2010, at 9:03 AM, Emile van Sebille wrote: > a = [1, 1, 2, 4, 6, 8, 9] > b = [1, 3, 4, 5, 6, 7, 8] > > def popwhile(l,t): > r = [] > while l[:1] == t: > r.append(l.pop(0)) > return r > > while bool(a or b): > m = min(a[:1],b[:1]) or max(a[:1],b[:1]) > print popwhile(a,m), popwhile(b,m) > > > Emile > > On 4/14/2010 8:20 AM Brent Pedersen said... >> hi, in trying to write a func that does a kind of merging of 2 sorted lists, >> i've come up with a fairly simple implementation that "almost works": >> http://gist.github.com/365485 >> >> but it hits StopIteration before returning the last value ([9], None) >> i can wrap the whole thing in a bunch more if statements, i've tried >> heapq.merge, but cant find a nice solution. >> >> any ideas? i think it's an interesting problem. >> -brent >> _______________________________________________ >> Baypiggies mailing list >> Baypiggies at python.org >> To change your subscription options or unsubscribe: >> http://mail.python.org/mailman/listinfo/baypiggies >> > > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > http://mail.python.org/mailman/listinfo/baypiggies From glen at glenjarvis.com Wed Apr 14 18:37:41 2010 From: glen at glenjarvis.com (Glen Jarvis) Date: Wed, 14 Apr 2010 09:37:41 -0700 Subject: [Baypiggies] World Plone Day Message-ID: <7A76A21B-61C6-4537-9564-C29AF2A1CEBB@glenjarvis.com> I'm sorry for the bad cut and paste. World Plone Day is in April. Although I know little about Plone, I know it's python based and has a passionate community. Obviously, we're not going to Wellington (or I can't). However, I've attended events like this here before. World Plone Day Wellington, Wednesday 28 April, 12pm, The Treasury, Level 5, 1 The Terrace World Plone Day is a worldwide event to promote and educate the worldwide public about the benefits of using Plone in education, government, ngos, and in business. Emerge Technology and The Treasury will host this FREE event for the Wellington area on April 28, 2010 at the New Zealand Treasury's offices.http://plone.org/events/wpd/2010/ wellington-new-zealand -------------- next part -------------- An HTML attachment was scrubbed... URL: From bpederse at gmail.com Wed Apr 14 18:41:09 2010 From: bpederse at gmail.com (Brent Pedersen) Date: Wed, 14 Apr 2010 09:41:09 -0700 Subject: [Baypiggies] a python puzzle In-Reply-To: References: Message-ID: On Wed, Apr 14, 2010 at 9:32 AM, Damon McCormick wrote: > Sorry about the cut-and-paste error.? Corrected below.? Also, I believe my > code is equivalent to Thomas'. > > -Damon > > > On Wed, Apr 14, 2010 at 9:29 AM, Damon McCormick wrote: >> >> Keeping your original approach, you could define a function like this: >> >> def next_or_none_pair (itr): >> ??? def result_func (): >> ??????? try: >> ??????????? return itr.next() >> ??????? except StopIteration: >> ??????????? return (None, None) >> ??? return result_func >> >> and then replace your current definitions of xnext and ynext by the >> following: >> >> ??? xnext = next_or_none_pair(itertools.groupby(xs, grouper)) >> ??? ynext = next_or_none_pair(itertools.groupby(ys, grouper)) >> >> The condition of your while loop is already set up to exit when either x >> or y is None (a condition which, I believe, is currently never True, since >> the loop ends when StopIteration is thrown). >> >> So the only other modification you'd need is that your comparisions >> between x and y need to handle None: >> >> ??????? elif y is None or x < y: >> ??????????? yield list(xgroup), None >> ??????????? x, xgroup = xnext() >> ??????? elif x is None or x > y: >> ??????????? yield (None, list(ygroup)) >> ??????????? y, ygroup = ynext() >> >> So the entire thing would look like this: >> > >> >> import itertools >> >> >> def next_or_none_pair (itr): >> ??? def result_func (): >> ??? try: >> ??????????? return itr.next() >> ??? except StopIteration: >> ??????????? return (None, None) >> ??? return result_func >> >> def as_pairs (xs, ys, grouper=lambda _: _): >> >> """ >> ??? >>> aordered = [1, 1, 2, 4, 6, 8, >> 9] >> ??? >>> bordered = [1, 3, 4, 5, 6, 7, >> 8] >> ??? >>> for a, b in as_pairs(aordered, >> bordered): >> ??? ... a, >> b >> ??? ([1, 1], >> [1]) >> ??? ([2], >> None) >> ??? (None, >> [3]) >> ??? ([4], >> [4]) >> ??? (None, >> [5]) >> ??? ([6], >> [6]) >> ??? (None, >> [7]) >> ??? ([8], >> [8]) >> ??? ([9], >> None) >> ??? """ >> ??? # assume xs and ys are >> sorted. >> ??? xnext = next_or_none_pair(itertools.groupby(xs, grouper)) >> ??? ynext = next_or_none_pair(itertools.groupby(ys, grouper)) >> ??? x, xgroup = xnext() >> ??? y, ygroup = ynext() >> ??? while x or y: >> ??????? if x == y: >> ??????????? yield list(xgroup), list(ygroup) >> ??????????? x, xgroup = xnext() >> ??????????? y, ygroup = ynext() >> ??????? elif y is None or x < y: >> ??????????? yield list(xgroup), None >> ??????????? x, xgroup = xnext() >> ??????? elif x is None or x > y: >> ??????????? yield (None, list(ygroup)) >> ??????????? y, ygroup = ynext() >> ??????? else: >> ??????????? assert False >> >> if __name__ == "__main__": >> ??? import doctest >> ??? doctest.testmod() >> >> >> >> >> On Wed, Apr 14, 2010 at 9:04 AM, Brent Pedersen >> wrote: >>> >>> On Wed, Apr 14, 2010 at 8:20 AM, Brent Pedersen >>> wrote: >>> > hi, in trying to write a func that does a kind of merging of 2 sorted >>> > lists, >>> > i've come up with a fairly simple implementation that "almost works": >>> > http://gist.github.com/365485 >>> > >>> > but it hits StopIteration before returning the last value ([9], None) >>> > i can wrap the whole thing in a bunch more if statements, i've tried >>> > heapq.merge, but cant find a nice solution. >>> > >>> > any ideas? i think it's an interesting problem. >>> > -brent >>> > >>> >>> i should add the for my real use-case, the iterables going in will not >>> be lists, they'll be lazily generated, and very large, so >>> i dont want to read them into memory to get the last element or slice >>> them. >>> ______________________________ > > i'm glad to see you guys are hitting the same problems i did. yours now works, but try setting bordered = xrange(15) then it has a problem. but your approach is pretty close, i'll see where i can get from there. thanks. From tungwaiyip at yahoo.com Wed Apr 14 17:56:15 2010 From: tungwaiyip at yahoo.com (Tung Wai Yip) Date: Wed, 14 Apr 2010 09:56:15 -0600 Subject: [Baypiggies] a python puzzle In-Reply-To: References: Message-ID: What problem have you encountered with heapq.merge? Wai Yip > hi, in trying to write a func that does a kind of merging of 2 sorted > lists, > i've come up with a fairly simple implementation that "almost works": > http://gist.github.com/365485 > > but it hits StopIteration before returning the last value ([9], None) > i can wrap the whole thing in a bunch more if statements, i've tried > heapq.merge, but cant find a nice solution. > > any ideas? i think it's an interesting problem. > -brent > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > http://mail.python.org/mailman/listinfo/baypiggies From bpederse at gmail.com Thu Apr 15 03:09:22 2010 From: bpederse at gmail.com (Brent Pedersen) Date: Wed, 14 Apr 2010 18:09:22 -0700 Subject: [Baypiggies] a python puzzle In-Reply-To: References: Message-ID: On Wed, Apr 14, 2010 at 8:20 AM, Brent Pedersen wrote: > hi, in trying to write a func that does a kind of merging of 2 sorted lists, > i've come up with a fairly simple implementation that "almost works": > http://gist.github.com/365485 > > but it hits StopIteration before returning the last value ([9], None) > i can wrap the whole thing in a bunch more if statements, i've tried > heapq.merge, but cant find a nice solution. > > any ideas? i think it's an interesting problem. > -brent > hey, thanks for all the input, damon and i ended up with this: http://gist.github.com/365485 not too bad, i guess. the real application is for a (huge) set of short sequences aligned to 2 different genomes. i need to do different things with a sequence depending on whether it aligned to genome a, genome b or to both. and since the grouping function is an argument, i have a number of other possible uses. From spmcinerney at hotmail.com Thu Apr 15 21:03:57 2010 From: spmcinerney at hotmail.com (Stephen McInerney) Date: Thu, 15 Apr 2010 12:03:57 -0700 Subject: [Baypiggies] New Meetup group - East Bay Google Technology User Group In-Reply-To: <1363699655.1271357581129.JavaMail.root@jobs.meetup.com> References: <1363699655.1271357581129.JavaMail.root@jobs.meetup.com> Message-ID: There is a new Meetup group (East Bay Google Technology User Group). However their meet date is the exact same as BayPIGgies (4th Thursday). This seems unfortunate as we will cannibalize each others' audiences. Just letting people know, Stephen New Meetup Group! East Bay Google Technology User Group The East Bay Google Technology User Group (EBGTUG) meets on the 4th Thursday of the month in East Bay. We invite our members that develop applications using Google technology to do brief demos of 5 minutes. This is followed by a technical presentation and/or demonstration of one or more Google technologies from 7:00 to 8:00pm. The time between 8:00pm and 9:00pm is available for longer talks, extended Q&A and/or more informal networking before everyone heads home. Our general meetings will always be free and open to the general public. We may charge to cover costs for our workshops. This group's first Meetup is already scheduled! East Bay Google Technology User Group Meetup ? Thursday, April 29, 2010 Organized by: lawrence CHECK OUT THIS MEETUP GROUP _________________________________________________________________ The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmail. http://www.windowslive.com/campaign/thenewbusy?tile=multicalendar&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_5 -------------- next part -------------- An HTML attachment was scrubbed... URL: From john_re at fastmail.us Sun Apr 18 07:12:35 2010 From: john_re at fastmail.us (giovanni_re) Date: Sat, 17 Apr 2010 22:12:35 -0700 Subject: [Baypiggies] Python at BerkeleyTIP-Global meeting on Sunday April 18 12N-3P, & April 27 Message-ID: <1271567555.18788.1370527791@webmail.messagingengine.com> Come discuss python. :) Join via VOIP or come to Berkeley http://sites.google.com/site/berkeleytip/voice-voip-conferencing FSCafe at Moffitt at UCBerkeley, opens 1pm, but can connect from outside at 12N. Hot topics: Ubuntu 10.04, Free Culuture, VOIP, Set up the web server & mail list & asterisk/freeswitch on the BTIP box with Ubuntu 10.04? Tues April 27 5-6P VOIP online meeting also. http://sites.google.com/site/berkeleytip/ Join the mail list, tell us what you're interested in. http://sites.google.com/site/berkeleytip/mailing-lists From cappy2112 at gmail.com Mon Apr 19 04:03:15 2010 From: cappy2112 at gmail.com (Tony Cappellini) Date: Sun, 18 Apr 2010 19:03:15 -0700 Subject: [Baypiggies] GUI Automation on Windows Message-ID: Does anyone here have any experience automating non-COM-based GUI's on Windows platforms? -------------- next part -------------- An HTML attachment was scrubbed... URL: From DennisR at dair.com Mon Apr 19 08:14:36 2010 From: DennisR at dair.com (Dennis Reinhardt) Date: Sun, 18 Apr 2010 23:14:36 -0700 Subject: [Baypiggies] GUI Automation on Windows In-Reply-To: References: Message-ID: <20100419062458.B138AEE98C@mail.python.org> At 07:03 PM 4/18/2010, Tony Cappellini wrote: >Does anyone here have any experience automating non-COM-based GUI's >on Windows platforms? I do. What are you interested in? I have written http://www.dialogdevil.com and have coded a Windows dll call interception wrapper which I have not commercialized ... yet. Dennis --------------------------------- | Dennis | DennisR at dair.com | | Reinhardt | http://www.dair.com | --------------------------------- From jason at mischievous.org Mon Apr 19 19:32:13 2010 From: jason at mischievous.org (Jason Culverhouse) Date: Mon, 19 Apr 2010 10:32:13 -0700 Subject: [Baypiggies] GUI Automation on Windows In-Reply-To: References: Message-ID: <60AA270F-5F0E-4968-864F-D115491F0572@mischievous.org> This one made the rounds a few months ago. http://groups.csail.mit.edu/uid/sikuli/index.shtml It "automates" using screen images via a python (jython) based scripting language. Jason On Apr 18, 2010, at 7:03 PM, Tony Cappellini wrote: > > Does anyone here have any experience automating non-COM-based GUI's on Windows platforms? > > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > http://mail.python.org/mailman/listinfo/baypiggies From cappy2112 at gmail.com Mon Apr 19 20:10:35 2010 From: cappy2112 at gmail.com (Tony Cappellini) Date: Mon, 19 Apr 2010 11:10:35 -0700 Subject: [Baypiggies] GUI Automation on Windows In-Reply-To: <60AA270F-5F0E-4968-864F-D115491F0572@mischievous.org> References: <60AA270F-5F0E-4968-864F-D115491F0572@mischievous.org> Message-ID: Been there, done that. Thanks On Mon, Apr 19, 2010 at 10:32 AM, Jason Culverhouse wrote: > This one made the rounds a few months ago. > http://groups.csail.mit.edu/uid/sikuli/index.shtml > > It "automates" using screen images via a python (jython) based scripting > language. > > Jason > > On Apr 18, 2010, at 7:03 PM, Tony Cappellini wrote: > > > > > Does anyone here have any experience automating non-COM-based GUI's on > Windows platforms? > > > > _______________________________________________ > > Baypiggies mailing list > > Baypiggies at python.org > > To change your subscription options or unsubscribe: > > http://mail.python.org/mailman/listinfo/baypiggies > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From damonmc at gmail.com Mon Apr 19 20:28:06 2010 From: damonmc at gmail.com (Damon McCormick) Date: Mon, 19 Apr 2010 11:28:06 -0700 Subject: [Baypiggies] GUI Automation on Windows In-Reply-To: References: <60AA270F-5F0E-4968-864F-D115491F0572@mischievous.org> Message-ID: Any comments on your experience trying to use Sikuli? I've been wondering how well it works in practice for gui testing. Thanks, Damon On Mon, Apr 19, 2010 at 11:10 AM, Tony Cappellini wrote: > Been there, done that. > > Thanks > > > On Mon, Apr 19, 2010 at 10:32 AM, Jason Culverhouse > wrote: > >> This one made the rounds a few months ago. >> http://groups.csail.mit.edu/uid/sikuli/index.shtml >> >> It "automates" using screen images via a python (jython) based scripting >> language. >> >> Jason >> >> On Apr 18, 2010, at 7:03 PM, Tony Cappellini wrote: >> >> > >> > Does anyone here have any experience automating non-COM-based GUI's on >> Windows platforms? >> > >> > _______________________________________________ >> > Baypiggies mailing list >> > Baypiggies at python.org >> > To change your subscription options or unsubscribe: >> > http://mail.python.org/mailman/listinfo/baypiggies >> >> > > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > http://mail.python.org/mailman/listinfo/baypiggies > -------------- next part -------------- An HTML attachment was scrubbed... URL: From luca.pellicoro at gmail.com Mon Apr 19 23:37:21 2010 From: luca.pellicoro at gmail.com (Luca Pellicoro) Date: Mon, 19 Apr 2010 14:37:21 -0700 Subject: [Baypiggies] GUI Automation on Windows In-Reply-To: References: <60AA270F-5F0E-4968-864F-D115491F0572@mischievous.org> Message-ID: On Mon, Apr 19, 2010 at 11:28 AM, Damon McCormick wrote: > Any comments on your experience trying to use Sikuli?? I've been wondering > how well it works in practice for gui testing. We tried it for flash functional test automation but the API and implementation had issues. So we went with autopy+selenium instead. > Thanks, > Damon > > On Mon, Apr 19, 2010 at 11:10 AM, Tony Cappellini > wrote: >> >> Been there, done that. >> >> Thanks >> >> On Mon, Apr 19, 2010 at 10:32 AM, Jason Culverhouse >> wrote: >>> >>> This one made the rounds a few months ago. >>> http://groups.csail.mit.edu/uid/sikuli/index.shtml >>> >>> It "automates" using screen images via a python (jython) based scripting >>> language. >>> >>> Jason >>> >>> On Apr 18, 2010, at 7:03 PM, Tony Cappellini wrote: >>> >>> > >>> > Does anyone here have any experience automating non-COM-based GUI's on >>> > Windows platforms? >>> > >>> > _______________________________________________ >>> > Baypiggies mailing list >>> > Baypiggies at python.org >>> > To change your subscription options or unsubscribe: >>> > http://mail.python.org/mailman/listinfo/baypiggies >>> >> >> >> _______________________________________________ >> Baypiggies mailing list >> Baypiggies at python.org >> To change your subscription options or unsubscribe: >> http://mail.python.org/mailman/listinfo/baypiggies > > > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > http://mail.python.org/mailman/listinfo/baypiggies > From jim at well.com Wed Apr 21 20:08:54 2010 From: jim at well.com (jim) Date: Wed, 21 Apr 2010 11:08:54 -0700 Subject: [Baypiggies] BayPIGgies meeting Thursday, April 22, 2010: From "Invent with Python" to Pygame Message-ID: <1271873334.6469.12.camel@jim-laptop> BayPIGgies meeting Thursday, March 25, 2010: From "Invent with Python" to Pygame Tonight's talk is * From "Invent with Python" to Pygame by Al Sweigart Meetings usually start with a Newbie Nugget, a short discussion of an essential Python feature, especially for those new to Python. Tonight's Newbie Nugget: If time allows, discussion of Python features and techniques LOCATION Symantec Corporation Symantec Vcafe 350 Ellis Street Mountain View, CA 94043 http://maps.google.com/maps/ms?oe=utf-8&client=firefox-a&ie=UTF8&fb=1&split=1&gl=us&ei=w6i_Sfr6MZmQsQOzlv0v&hl=en&t=h&msa=0&msid=116202735295394761637.00046550c09ff3d96bff1&ll=37.397693,-122.053707&spn=0.002902,0.004828&z=18 BayPIGgies meeting information is available at http://www.baypiggies.net/ ------------------------ Agenda ------------------------ ..... 7:30 PM ........................... General hubbub, inventory end-of-meeting announcements, any first-minute announcements. ..... 7:35 PM to 7:45 PM ................ Newbie Nugget: deferred until after the end of main talk ..... 7:45 PM to 8:40 PM (or so) ................ * From "Invent with Python" to Pygame I'll talk about the book, which is available in full under a Creative Commons license at http://inventwithpython.com as well as the process of writing it. I'll also go through the last chapter, which is a light intro to Pygame, just to show off what Pygame can do. (from the web site: ) "Python is the new BASIC", "Invent with Python" is designed to teach real programming in Python. ..... 8:50 PM to 9:30 PM ................ Mapping and Random Access Mapping is a rapid-fire audience announcement of issues, hiring, events, and other topics. Random Access follows people immediately to allow follow up on the announcements and other interests. From cappy2112 at gmail.com Thu Apr 22 19:24:12 2010 From: cappy2112 at gmail.com (Tony Cappellini) Date: Thu, 22 Apr 2010 10:24:12 -0700 Subject: [Baypiggies] GUI Bloopers Message-ID: Have any of you read this book on GUI Bloopers? http://www.gui-bloopers.com/ IF so- do you have any feedback? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From jim at well.com Thu Apr 22 19:44:37 2010 From: jim at well.com (jim) Date: Thu, 22 Apr 2010 10:44:37 -0700 Subject: [Baypiggies] GUI Bloopers In-Reply-To: References: Message-ID: <1271958277.6595.24.camel@jim-laptop> i looked at the table of contents as well as downloaded the sample chapter (text bloopers) and the appendix (color bloopers). overall it strikes me as valuable, required reading for GUI (and to some degree CLI) designers. On Thu, 2010-04-22 at 10:24 -0700, Tony Cappellini wrote: > > Have any of you read this book on GUI Bloopers? > http://www.gui-bloopers.com/ > > IF so- do you have any feedback? > > > Thanks > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > http://mail.python.org/mailman/listinfo/baypiggies From kenobi at gmail.com Fri Apr 23 00:53:52 2010 From: kenobi at gmail.com (Rick Kwan) Date: Thu, 22 Apr 2010 15:53:52 -0700 Subject: [Baypiggies] GUI Bloopers In-Reply-To: <1271958277.6595.24.camel@jim-laptop> References: <1271958277.6595.24.camel@jim-laptop> Message-ID: "The username and password you entered do not match." -- p. 155, fig. 4.2 +++1 On Thu, Apr 22, 2010 at 10:44 AM, jim wrote: > > > ? i looked at the table of contents as well as > downloaded the sample chapter (text bloopers) > and the appendix (color bloopers). overall it > strikes me as valuable, required reading for > GUI (and to some degree CLI) designers. > > > > On Thu, 2010-04-22 at 10:24 -0700, Tony Cappellini wrote: >> >> Have any of you read this book on GUI Bloopers? >> http://www.gui-bloopers.com/ >> >> IF so- do you have any feedback? >> >> >> Thanks >> _______________________________________________ >> Baypiggies mailing list >> Baypiggies at python.org >> To change your subscription options or unsubscribe: >> http://mail.python.org/mailman/listinfo/baypiggies > > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > http://mail.python.org/mailman/listinfo/baypiggies > From kenobi at gmail.com Fri Apr 23 00:59:50 2010 From: kenobi at gmail.com (Rick Kwan) Date: Thu, 22 Apr 2010 15:59:50 -0700 Subject: [Baypiggies] GUI Bloopers In-Reply-To: References: <1271958277.6595.24.camel@jim-laptop> Message-ID: On second thought, what is a proper succinct way to say that? On Thu, Apr 22, 2010 at 3:53 PM, Rick Kwan wrote: > "The username and password you entered do not match." -- p. 155, fig. 4.2 > > +++1 > > On Thu, Apr 22, 2010 at 10:44 AM, jim wrote: >> >> >> ? i looked at the table of contents as well as >> downloaded the sample chapter (text bloopers) >> and the appendix (color bloopers). overall it >> strikes me as valuable, required reading for >> GUI (and to some degree CLI) designers. >> >> >> >> On Thu, 2010-04-22 at 10:24 -0700, Tony Cappellini wrote: >>> >>> Have any of you read this book on GUI Bloopers? >>> http://www.gui-bloopers.com/ >>> >>> IF so- do you have any feedback? >>> >>> >>> Thanks >>> _______________________________________________ >>> Baypiggies mailing list >>> Baypiggies at python.org >>> To change your subscription options or unsubscribe: >>> http://mail.python.org/mailman/listinfo/baypiggies >> >> _______________________________________________ >> Baypiggies mailing list >> Baypiggies at python.org >> To change your subscription options or unsubscribe: >> http://mail.python.org/mailman/listinfo/baypiggies >> > From hyperneato at gmail.com Fri Apr 23 02:13:45 2010 From: hyperneato at gmail.com (Isaac) Date: Thu, 22 Apr 2010 17:13:45 -0700 Subject: [Baypiggies] GUI Bloopers In-Reply-To: References: <1271958277.6595.24.camel@jim-laptop> Message-ID: The password does not match the username you entered. On Thu, Apr 22, 2010 at 3:59 PM, Rick Kwan wrote: > On second thought, what is a proper succinct way to say that? > > On Thu, Apr 22, 2010 at 3:53 PM, Rick Kwan wrote: > > "The username and password you entered do not match." -- p. 155, fig. 4.2 > > > > +++1 > > > > On Thu, Apr 22, 2010 at 10:44 AM, jim wrote: > >> > >> > >> i looked at the table of contents as well as > >> downloaded the sample chapter (text bloopers) > >> and the appendix (color bloopers). overall it > >> strikes me as valuable, required reading for > >> GUI (and to some degree CLI) designers. > >> > >> > >> > >> On Thu, 2010-04-22 at 10:24 -0700, Tony Cappellini wrote: > >>> > >>> Have any of you read this book on GUI Bloopers? > >>> http://www.gui-bloopers.com/ > >>> > >>> IF so- do you have any feedback? > >>> > >>> > >>> Thanks > >>> _______________________________________________ > >>> Baypiggies mailing list > >>> Baypiggies at python.org > >>> To change your subscription options or unsubscribe: > >>> http://mail.python.org/mailman/listinfo/baypiggies > >> > >> _______________________________________________ > >> Baypiggies mailing list > >> Baypiggies at python.org > >> To change your subscription options or unsubscribe: > >> http://mail.python.org/mailman/listinfo/baypiggies > >> > > > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > http://mail.python.org/mailman/listinfo/baypiggies > -------------- next part -------------- An HTML attachment was scrubbed... URL: From keith at dartworks.biz Fri Apr 23 02:30:22 2010 From: keith at dartworks.biz (Keith Dart) Date: Thu, 22 Apr 2010 17:30:22 -0700 Subject: [Baypiggies] GUI Bloopers In-Reply-To: References: <1271958277.6595.24.camel@jim-laptop> Message-ID: <20100422173022.44baf0c5@dartworks.biz> === On Thu, 04/22, Isaac wrote: === > The password does not match the username you entered. === "Excuse me, but that password does not correspond to the account name you entered." :-) -- Keith Dart -- -- -------------------- Keith Dart ======================= From johan.mickelin at gmail.com Fri Apr 23 02:49:49 2010 From: johan.mickelin at gmail.com (Johan Mickelin) Date: Thu, 22 Apr 2010 17:49:49 -0700 Subject: [Baypiggies] GUI Bloopers In-Reply-To: <20100422173022.44baf0c5@dartworks.biz> References: <1271958277.6595.24.camel@jim-laptop> <20100422173022.44baf0c5@dartworks.biz> Message-ID: http://blogs.sfweekly.com/thesnitch/2010/04/sex_offender_locator_youre_doi.php :) On Thu, Apr 22, 2010 at 5:30 PM, Keith Dart wrote: > === On Thu, 04/22, Isaac wrote: === > > The password does not match the username you entered. > > === > > "Excuse me, but that password does not correspond to the account name > you entered." > > :-) > > > -- Keith Dart > > -- > -- -------------------- > Keith Dart > > ======================= > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > http://mail.python.org/mailman/listinfo/baypiggies > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hyperneato at gmail.com Fri Apr 23 02:56:32 2010 From: hyperneato at gmail.com (Isaac) Date: Thu, 22 Apr 2010 17:56:32 -0700 Subject: [Baypiggies] GUI Bloopers In-Reply-To: <20100422173022.44baf0c5@dartworks.biz> References: <1271958277.6595.24.camel@jim-laptop> <20100422173022.44baf0c5@dartworks.biz> Message-ID: "And the username you entered does not match any account on record here, maybe somewhere else?" On Thu, Apr 22, 2010 at 5:30 PM, Keith Dart wrote: > === On Thu, 04/22, Isaac wrote: === > > The password does not match the username you entered. > > === > > "Excuse me, but that password does not correspond to the account name > you entered." > > :-) > > > -- Keith Dart > > -- > -- -------------------- > Keith Dart > > ======================= > -------------- next part -------------- An HTML attachment was scrubbed... URL: From keith at dartworks.biz Fri Apr 23 03:05:16 2010 From: keith at dartworks.biz (Keith Dart) Date: Thu, 22 Apr 2010 18:05:16 -0700 Subject: [Baypiggies] GUI Bloopers In-Reply-To: References: <1271958277.6595.24.camel@jim-laptop> <20100422173022.44baf0c5@dartworks.biz> Message-ID: <20100422180516.17291506@dartworks.biz> === On Thu, 04/22, Johan Mickelin wrote: === > http://blogs.sfweekly.com/thesnitch/2010/04/sex_offender_locator_youre_doi.php === Wow, perfect timing! -- Keith Dart -- -- -------------------- Keith Dart ======================= From aahz at pythoncraft.com Fri Apr 23 03:55:18 2010 From: aahz at pythoncraft.com (Aahz) Date: Thu, 22 Apr 2010 18:55:18 -0700 Subject: [Baypiggies] Security bloopers (was GUI Bloopers) In-Reply-To: References: <1271958277.6595.24.camel@jim-laptop> <20100422173022.44baf0c5@dartworks.biz> Message-ID: <20100423015518.GA27368@panix.com> On Thu, Apr 22, 2010, Isaac wrote: > > "And the username you entered does not match any account on record here, > maybe somewhere else?" Being serious for a moment: no Generally speaking, one principle of security is that you never let crackers know whether any given username exists on your system. -- Aahz (aahz at pythoncraft.com) <*> http://www.pythoncraft.com/ "It is easier to optimize correct code than to correct optimized code." --Bill Harlan From spmcinerney at hotmail.com Mon Apr 26 00:58:03 2010 From: spmcinerney at hotmail.com (Stephen McInerney) Date: Sun, 25 Apr 2010 15:58:03 -0700 Subject: [Baypiggies] "Moving From Python 2 to Python 3" Map or similar In-Reply-To: <8249c4ac0911211826k518272dk670e7d29beb01316@mail.gmail.com> References: <8249c4ac0911211826k518272dk670e7d29beb01316@mail.gmail.com> Message-ID: Did anyone ever download this Pearson "Moving From Python 2 to Python 3" Map PDF (promo is no longer available) or can you recommend any similar quick reference online? Stephen Date: Sat, 21 Nov 2009 18:26:12 -0800 From: cappy2112 at yahoo.com To: baypiggies at python.org Subject: [Baypiggies] Fwd: Pearson UG Special: "Moving From Python 2 to Python 3" Map At the link below, there is a Download button which points to a PDF quick reference sheet for migrating to Python 3. FOR YOUR MEMBERS: Please send your members this link where they can download the map, as well as enter an exclusive User Group contest for the chance to win one of five ?Python prize packs?. http://www.informit.com/promotions/promotion.aspx?promo=137495 _________________________________________________________________ Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_1 -------------- next part -------------- An HTML attachment was scrubbed... URL: From wescpy at gmail.com Mon Apr 26 03:12:14 2010 From: wescpy at gmail.com (wesley chun) Date: Sun, 25 Apr 2010 18:12:14 -0700 Subject: [Baypiggies] "Moving From Python 2 to Python 3" Map or similar In-Reply-To: References: <8249c4ac0911211826k518272dk670e7d29beb01316@mail.gmail.com> Message-ID: http://tinyurl.com/29xdp69 On Sun, Apr 25, 2010 at 3:58 PM, Stephen McInerney wrote: > > Did anyone ever download this Pearson "Moving From Python 2 to Python 3" Map PDF > (promo is no longer available) or can you recommend any similar quick reference online? > > Stephen > > ________________________________ > Date: Sat, 21 Nov 2009 18:26:12 -0800 > From: cappy2112 at yahoo.com > To: baypiggies at python.org > Subject: [Baypiggies] Fwd: Pearson UG Special: "Moving From Python 2 to > Python 3" Map > > At the link below, there is a Download button which points to a PDF quick > reference sheet for migrating to Python 3. > > FOR YOUR MEMBERS: Please send your members this link where they can download > the map, as well as enter an exclusive User Group contest for the chance to > win one of five ?Python prize packs?. > > http://www.informit.com/promotions/promotion.aspx?promo=137495 -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - "Python Web Development with Django", Addison Wesley, (c) 2009 http://withdjango.com wesley.j.chun :: wescpy-at-gmail.com python training and technical consulting cyberweb.consulting : silicon valley, ca http://cyberwebconsulting.com From glen at glenjarvis.com Mon Apr 26 03:23:34 2010 From: glen at glenjarvis.com (Glen Jarvis) Date: Sun, 25 Apr 2010 18:23:34 -0700 Subject: [Baypiggies] "Moving From Python 2 to Python 3" Map or similar In-Reply-To: References: <8249c4ac0911211826k518272dk670e7d29beb01316@mail.gmail.com> Message-ID: I have one and can give you a copy if you need it. Glen On Apr 25, 2010, at 3:58 PM, Stephen McInerney wrote: > > Did anyone ever download this Pearson "Moving From Python 2 to > Python 3" Map PDF > (promo is no longer available) > or can you recommend any similar quick reference online? > > Stephen > > Date: Sat, 21 Nov 2009 18:26:12 -0800 > From: cappy2112 at yahoo.com > To: baypiggies at python.org > Subject: [Baypiggies] Fwd: Pearson UG Special: "Moving From Python 2 > to Python 3" Map > > At the link below, there is a Download button which points to a PDF > quick reference sheet for migrating to Python 3. > > FOR YOUR MEMBERS: Please send your members this link where they can > download the map, as well as enter an exclusive User Group contest > for the chance to win one of five ?Python prize packs?. > > http://www.informit.com/promotions/promotion.aspx?promo=137495 > > > > > > > Hotmail has tools for the New Busy. Search, chat and e-mail from > your inbox. Learn more. > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > http://mail.python.org/mailman/listinfo/baypiggies -------------- next part -------------- An HTML attachment was scrubbed... URL: From tony at tcapp.com Mon Apr 26 05:37:12 2010 From: tony at tcapp.com (Tony Cappellini) Date: Sun, 25 Apr 2010 20:37:12 -0700 Subject: [Baypiggies] "Moving From Python 2 to Python 3" Map or similar In-Reply-To: References: <8249c4ac0911211826k518272dk670e7d29beb01316@mail.gmail.com> Message-ID: On Sun, Apr 25, 2010 at 6:12 PM, wesley chun wrote: > http://tinyurl.com/29xdp69 > Shouldn't a reference like this be posted on Python.org - in neon? From spmcinerney at hotmail.com Mon Apr 26 07:34:04 2010 From: spmcinerney at hotmail.com (Stephen McInerney) Date: Sun, 25 Apr 2010 22:34:04 -0700 Subject: [Baypiggies] "Moving From Python 2 to Python 3" Map or similar In-Reply-To: References: <8249c4ac0911211826k518272dk670e7d29beb01316@mail.gmail.com>, , Message-ID: Wes, there's no need for a content-free post like that. Before I posted my question, I had in fact already googled it, and the PDF reference that the Pearson promo had offered is not available, and references to the dude's book (as opposed to the quick reference) are not available. Hence my question. I was going to say all that in my email, but I thought it went without saying so I deleted that comment. In future you can safely assume that any question I ask I have already googled on it and not found the result. In fact, if you did in fact google it, you would find a ton of (now-useless) archived references of Tony's original email. So: does anyone else have a short reference on this topic? Not a whole book, just a quick-reference. Thanks, Stephen > Date: Sun, 25 Apr 2010 18:12:14 -0700 > Subject: Re: [Baypiggies] "Moving From Python 2 to Python 3" Map or similar > From: wescpy at gmail.com > To: spmcinerney at hotmail.com > CC: baypiggies at python.org > > http://tinyurl.com/29xdp69 > > > On Sun, Apr 25, 2010 at 3:58 PM, Stephen McInerney > wrote: > > > > Did anyone ever download this Pearson "Moving From Python 2 to Python 3" Map PDF > > (promo is no longer available) or can you recommend any similar quick reference online? > > > > Stephen > > > > ________________________________ > > Date: Sat, 21 Nov 2009 18:26:12 -0800 > > From: cappy2112 at yahoo.com > > To: baypiggies at python.org > > Subject: [Baypiggies] Fwd: Pearson UG Special: "Moving From Python 2 to > > Python 3" Map > > > > At the link below, there is a Download button which points to a PDF quick > > reference sheet for migrating to Python 3. > > > > FOR YOUR MEMBERS: Please send your members this link where they can download > > the map, as well as enter an exclusive User Group contest for the chance to > > win one of five ?Python prize packs?. > > > > http://www.informit.com/promotions/promotion.aspx?promo=137495 > > > -- > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > "Python Web Development with Django", Addison Wesley, (c) 2009 > http://withdjango.com > > wesley.j.chun :: wescpy-at-gmail.com > python training and technical consulting > cyberweb.consulting : silicon valley, ca > http://cyberwebconsulting.com _________________________________________________________________ The New Busy is not the old busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3 -------------- next part -------------- An HTML attachment was scrubbed... URL: From spmcinerney at hotmail.com Mon Apr 26 07:37:16 2010 From: spmcinerney at hotmail.com (Stephen McInerney) Date: Sun, 25 Apr 2010 22:37:16 -0700 Subject: [Baypiggies] "Moving From Python 2 to Python 3" Map or similar In-Reply-To: References: <8249c4ac0911211826k518272dk670e7d29beb01316@mail.gmail.com>, , Message-ID: As a follow-up, if you google for pearson UG "Moving From Python 2 to Python 3" you indeed get garbage results as opposed to plain old "Moving From Python 2 to Python 3" which does give good results. Why Google gives junk results when I supply a *more* accurate query, is not my business. > Date: Sun, 25 Apr 2010 18:12:14 -0700 > Subject: Re: [Baypiggies] "Moving From Python 2 to Python 3" Map or similar > From: wescpy at gmail.com > To: spmcinerney at hotmail.com > CC: baypiggies at python.org > > http://tinyurl.com/29xdp69 > > > On Sun, Apr 25, 2010 at 3:58 PM, Stephen McInerney > wrote: > > > > Did anyone ever download this Pearson "Moving From Python 2 to Python 3" Map PDF > > (promo is no longer available) or can you recommend any similar quick reference online? > > > > Stephen > > > > ________________________________ > > Date: Sat, 21 Nov 2009 18:26:12 -0800 > > From: cappy2112 at yahoo.com > > To: baypiggies at python.org > > Subject: [Baypiggies] Fwd: Pearson UG Special: "Moving From Python 2 to > > Python 3" Map > > > > At the link below, there is a Download button which points to a PDF quick > > reference sheet for migrating to Python 3. > > > > FOR YOUR MEMBERS: Please send your members this link where they can download > > the map, as well as enter an exclusive User Group contest for the chance to > > win one of five ?Python prize packs?. > > > > http://www.informit.com/promotions/promotion.aspx?promo=137495 > > > -- > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > "Python Web Development with Django", Addison Wesley, (c) 2009 > http://withdjango.com > > wesley.j.chun :: wescpy-at-gmail.com > python training and technical consulting > cyberweb.consulting : silicon valley, ca > http://cyberwebconsulting.com _________________________________________________________________ The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail. http://www.windowslive.com/campaign/thenewbusy?tile=multiaccount&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4 -------------- next part -------------- An HTML attachment was scrubbed... URL: From venkat83 at gmail.com Mon Apr 26 08:37:26 2010 From: venkat83 at gmail.com (Venkatraman S) Date: Mon, 26 Apr 2010 12:07:26 +0530 Subject: [Baypiggies] [OT] Job Portal Message-ID: Crowd sourcing Q : If there were to be a job site, what would be the features that you would look for? or yearn for? IMHO, i would need : # a simple design. # not much UI clutter. # 1-2 ads at the max(just to keep the site functioning). # 1-2 step workflow at the max - for both the job posters and job seekers. Anything else? -Venkat http://twitter.com/venkasub -------------- next part -------------- An HTML attachment was scrubbed... URL: From python at dylanreinhardt.com Mon Apr 26 17:22:59 2010 From: python at dylanreinhardt.com (Dylan Reinhardt) Date: Mon, 26 Apr 2010 08:22:59 -0700 Subject: [Baypiggies] "Moving From Python 2 to Python 3" Map or similar In-Reply-To: References: <8249c4ac0911211826k518272dk670e7d29beb01316@mail.gmail.com> Message-ID: Is this what you're looking for? http://ptgmedia.pearsoncmg.com/imprint_downloads/informit/promotions/python/python2python3.pdf HTH On Sun, Apr 25, 2010 at 10:34 PM, Stephen McInerney wrote: > Wes, there's no need for a content-free post like that. > Before I posted my question, I had in fact already googled it, and the PDF > reference that the Pearson promo had offered is not available, and > references to the dude's book (as opposed to the quick reference) are not > available. Hence my question. > I was going to say all that in my email, but I thought it went without > saying > so I deleted that comment. > In future you can safely assume that any question I ask I have already > googled on it and not found the result. > In fact, if you did in fact google it, you would find a ton of > (now-useless) > archived references of Tony's original email. > > So: does anyone else have a short reference on this topic? Not a whole > book, > just a quick-reference. > > Thanks, > Stephen > > > Date: Sun, 25 Apr 2010 18:12:14 -0700 > > Subject: Re: [Baypiggies] "Moving From Python 2 to Python 3" Map or > similar > > From: wescpy at gmail.com > > To: spmcinerney at hotmail.com > > CC: baypiggies at python.org > > > > > http://tinyurl.com/29xdp69 > > > > > > On Sun, Apr 25, 2010 at 3:58 PM, Stephen McInerney > > wrote: > > > > > > Did anyone ever download this Pearson "Moving From Python 2 to Python > 3" Map PDF > > > (promo is no longer available) or can you recommend any similar quick > reference online? > > > > > > Stephen > > > > > > ________________________________ > > > Date: Sat, 21 Nov 2009 18:26:12 -0800 > > > From: cappy2112 at yahoo.com > > > To: baypiggies at python.org > > > Subject: [Baypiggies] Fwd: Pearson UG Special: "Moving From Python 2 to > > > Python 3" Map > > > > > > At the link below, there is a Download button which points to a PDF > quick > > > reference sheet for migrating to Python 3. > > > > > > FOR YOUR MEMBERS: Please send your members this link where they can > download > > > the map, as well as enter an exclusive User Group contest for the > chance to > > > win one of five ?Python prize packs?. > > > > > > http://www.informit.com/promotions/promotion.aspx?promo=137495 > > > > > > -- > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > "Python Web Development with Django", Addison Wesley, (c) 2009 > > http://withdjango.com > > > > wesley.j.chun :: wescpy-at-gmail.com > > python training and technical consulting > > cyberweb.consulting : silicon valley, ca > > http://cyberwebconsulting.com > > ------------------------------ > The New Busy is not the old busy. Search, chat and e-mail from your inbox. Get > started. > > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > http://mail.python.org/mailman/listinfo/baypiggies > -------------- next part -------------- An HTML attachment was scrubbed... URL: From spmcinerney at hotmail.com Mon Apr 26 18:26:58 2010 From: spmcinerney at hotmail.com (Stephen McInerney) Date: Mon, 26 Apr 2010 09:26:58 -0700 Subject: [Baypiggies] "Moving From Python 2 to Python 3" Map or similar In-Reply-To: References: <8249c4ac0911211826k518272dk670e7d29beb01316@mail.gmail.com>, , , , Message-ID: Thanks to the many who responded offline, I got this link. Stephen Date: Mon, 26 Apr 2010 08:22:59 -0700 Subject: Re: [Baypiggies] "Moving From Python 2 to Python 3" Map or similar From: python at dylanreinhardt.com To: spmcinerney at hotmail.com CC: baypiggies at python.org Is this what you're looking for? http://ptgmedia.pearsoncmg.com/imprint_downloads/informit/promotions/python/python2python3.pdf HTH On Sun, Apr 25, 2010 at 10:34 PM, Stephen McInerney wrote: Wes, there's no need for a content-free post like that. Before I posted my question, I had in fact already googled it, and the PDF reference that the Pearson promo had offered is not available, and references to the dude's book (as opposed to the quick reference) are not available. Hence my question. I was going to say all that in my email, but I thought it went without saying so I deleted that comment. In future you can safely assume that any question I ask I have already googled on it and not found the result. In fact, if you did in fact google it, you would find a ton of (now-useless) archived references of Tony's original email. So: does anyone else have a short reference on this topic? Not a whole book, just a quick-reference. Thanks, Stephen > Date: Sun, 25 Apr 2010 18:12:14 -0700 > Subject: Re: [Baypiggies] "Moving From Python 2 to Python 3" Map or similar > From: wescpy at gmail.com > To: spmcinerney at hotmail.com > CC: baypiggies at python.org > > http://tinyurl.com/29xdp69 > > > On Sun, Apr 25, 2010 at 3:58 PM, Stephen McInerney > wrote: > > > > Did anyone ever download this Pearson "Moving From Python 2 to Python 3" Map PDF > > (promo is no longer available) or can you recommend any similar quick reference online? > > > > Stephen > > > > ________________________________ > > Date: Sat, 21 Nov 2009 18:26:12 -0800 > > From: cappy2112 at yahoo.com > > To: baypiggies at python.org > > Subject: [Baypiggies] Fwd: Pearson UG Special: "Moving From Python 2 to > > Python 3" Map > > > > At the link below, there is a Download button which points to a PDF quick > > reference sheet for migrating to Python 3. > > > > FOR YOUR MEMBERS: Please send your members this link where they can download > > the map, as well as enter an exclusive User Group contest for the chance to > > win one of five ?Python prize packs?. > > > > http://www.informit.com/promotions/promotion.aspx?promo=137495 > > > -- > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > "Python Web Development with Django", Addison Wesley, (c) 2009 > http://withdjango.com > > wesley.j.chun :: wescpy-at-gmail.com > python training and technical consulting > cyberweb.consulting : silicon valley, ca > http://cyberwebconsulting.com _________________________________________________________________ The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail. http://www.windowslive.com/campaign/thenewbusy?tile=multiaccount&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jim at well.com Mon Apr 26 19:45:01 2010 From: jim at well.com (jim) Date: Mon, 26 Apr 2010 10:45:01 -0700 Subject: [Baypiggies] useful article regarding extending existing software Message-ID: <1272303901.8826.58.camel@jim-laptop> http://www.embeddedtechmag.com/component/content/article/7542 Software Of Unknown Pedigree is legacy software the design of which is not easily determined. this article explores the problem facing those who are charged with coding improvements (new features, performance...) to such legacy code. From slander at unworkable.org Tue Apr 27 07:03:28 2010 From: slander at unworkable.org (Harry Tormey) Date: Mon, 26 Apr 2010 22:03:28 -0700 Subject: [Baypiggies] PyGameSF meetup Thursday April 29th 6pm @ Main San Francisco Public Library Message-ID: <20100427050328.GA20859@unworkable.org> Hi All, The April PyGameSF meet up will be at the STONG conference room on the first floor of the main San Francisco public library beside civic center BART. The library closes at 8pm so we will reconvene to frjtz on hayes street for dinner/drinks afterwords. This month's presentations are: * Colin Bean: Complex visualization with Pyglet and NumPy. An introduction to how complex numbers can be visualized ad 2D geometry, how geometric transformations can be described as operations on complex numbers, and how basic complex functions can produce visually striking results. Visualization code will be provided using Pyglet and NumPy. The material is based on Tristan Needham's book "Visual Complex Analysis". * Harry Tormey: Mobile games to make you move around. Obesity has been cited as a contributing factor to approximately 100,000 to 400,000 deaths per year in the USA alone. To help address this problem the company I work for is having a competition to create an Android app that inspires and tracks physical movement using our API's: https://snaptic.com/challenge/. The grand prize for this competition : An all expenses paid trip to TED Global 2010. I will be demoing an example open source exercise tracking Android app and an accompanying pylons based web stack which displays information captured via the phone. Talk will cover: An introduction to Android, mobile data capture techniques and displaying information captured from the phone via a python based web backend using the Snaptic API (http://snaptic.com/developers/). -- Harry Tormey Co Founder P2P Research http://p2presearch.com Founder PyGameSF http://pygamesf.org Director http://snaptic.com From jim at well.com Tue Apr 27 17:25:08 2010 From: jim at well.com (jim) Date: Tue, 27 Apr 2010 08:25:08 -0700 Subject: [Baypiggies] Asheesh Loroia on OpenHatch at Noisebridge Wednesday evening Message-ID: <1272381908.8826.93.camel@jim-laptop> Asheesh Loroia on OpenHatch at Noisebridge Wednesday evening The Linux Discussion Group meets every Wednesday evening from 6 PM to 8 PM at Noisebridge. Normally it's a free-form discussion. Tomorrow evening (Wednesday 20100428) Asheesh Loroia will be there to talk about the Open Hatch effort: http://openhatch.org/ open hatch is "an open source involvement engine" that lets you match your skills and interests with a variety of open source projects that need help. From fperez.net at gmail.com Tue Apr 27 23:14:03 2010 From: fperez.net at gmail.com (Fernando Perez) Date: Tue, 27 Apr 2010 14:14:03 -0700 Subject: [Baypiggies] [ANN - Berkeley py4science] Talk Weds. April 27: Python capabilities on a Hadoop based cluster Message-ID: Hi all, a reminder of tomorrow's talk: * April 28, 2pm: Title: Python capabilities on a Hadoop based cluster. By Dan Starr, Astronomy, UC Berkeley. To make use of several Hadoop clusters recently made available, I ported portions of our Python based project into Hadoop run-able jobs using Hadoop treaming and Cascading. I'll discuss tricks which helped make this possible and give some comparisons between Yahoo's M45 cluster and an Amazon EC2 cluster using customized Cloudera AMIs. I would also like to give an overview of Hadoop Dumbo and Python hooks for HIVE. As usual, we meet at the Redwood Center's conference room: 508-20 Evans Hall (5th floor). More information: https://cirl.berkeley.edu/view/Py4Science Please pass this along to any colleagues who might be interested. Regards, f From jjinux at gmail.com Wed Apr 28 09:58:30 2010 From: jjinux at gmail.com (Shannon -jj Behrens) Date: Wed, 28 Apr 2010 00:58:30 -0700 Subject: [Baypiggies] [OT] Job Portal In-Reply-To: References: Message-ID: On Sun, Apr 25, 2010 at 11:37 PM, Venkatraman S wrote: > Crowd sourcing Q : If there were to be a job site, what would be the > features that you would look for? or yearn for? > > IMHO, i would need : > # a simple design. > # not much UI clutter. > # 1-2 ads at the max(just to keep the site functioning). > # 1-2 step workflow at the max - for both the job posters and job seekers. > > Anything else? The book "Founders at Work" has a pretty good history of what made Craigslist successful. A big part of it is that Craig himself is a great guy with a great moral compass. -jj -- In this life we cannot do great things. We can only do small things with great love. -- Mother Teresa http://jjinux.blogspot.com/ From jjinux at gmail.com Wed Apr 28 10:40:43 2010 From: jjinux at gmail.com (Shannon -jj Behrens) Date: Wed, 28 Apr 2010 01:40:43 -0700 Subject: [Baypiggies] useful article regarding extending existing software In-Reply-To: <1272303901.8826.58.camel@jim-laptop> References: <1272303901.8826.58.camel@jim-laptop> Message-ID: On Mon, Apr 26, 2010 at 10:45 AM, jim wrote: > http://www.embeddedtechmag.com/component/content/article/7542 > > ? Software Of Unknown Pedigree is legacy software > the design of which is not easily determined. this > article explores the problem facing those who are > charged with coding improvements (new features, > performance...) to such legacy code. I think that article is very helpful for dealing with SOUP (Software Of Unknown Pedigree) code, but I'm not at all convinced it's suitable for dealing with CRAP (Cantankerous and Really Asinine Python) code ;) -jj -- In this life we cannot do great things. We can only do small things with great love. -- Mother Teresa http://jjinux.blogspot.com/ From spmcinerney at hotmail.com Wed Apr 28 11:58:15 2010 From: spmcinerney at hotmail.com (Stephen McInerney) Date: Wed, 28 Apr 2010 02:58:15 -0700 Subject: [Baypiggies] useful article regarding extending existing software In-Reply-To: References: <1272303901.8826.58.camel@jim-laptop>, Message-ID: True. In the spirit of CRAP, there are still companies out there using legacy Python 1.x code, most of which can never be ported. Maybe we need a tool which, among other things, calculates the CRAP index. You know a language is getting mature when reengineering starts becoming a headache. Stephen > Date: Wed, 28 Apr 2010 01:40:43 -0700 > From: jjinux at gmail.com > To: jim at well.com > CC: baypiggies at python.org > Subject: Re: [Baypiggies] useful article regarding extending existing software > > On Mon, Apr 26, 2010 at 10:45 AM, jim wrote: > > http://www.embeddedtechmag.com/component/content/article/7542 > > > > Software Of Unknown Pedigree is legacy software > > the design of which is not easily determined. this > > article explores the problem facing those who are > > charged with coding improvements (new features, > > performance...) to such legacy code. > > I think that article is very helpful for dealing with SOUP (Software > Of Unknown Pedigree) code, but I'm not at all convinced it's suitable > for dealing with CRAP (Cantankerous and Really Asinine Python) code ;) > > -jj _________________________________________________________________ The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail. http://www.windowslive.com/campaign/thenewbusy?tile=multiaccount&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jjinux at gmail.com Thu Apr 29 03:52:48 2010 From: jjinux at gmail.com (Shannon -jj Behrens) Date: Wed, 28 Apr 2010 18:52:48 -0700 Subject: [Baypiggies] useful article regarding extending existing software In-Reply-To: References: <1272303901.8826.58.camel@jim-laptop> Message-ID: On Wed, Apr 28, 2010 at 2:58 AM, Stephen McInerney wrote: > True. In the spirit of CRAP, there are still companies out there using > legacy Python 1.x code, most of which can never be ported. > Maybe we need a tool which, among other things, calculates the CRAP index. > You know a language is getting mature when reengineering starts becoming a > headache. I do believe Pylint can calculate a piece of code's CRAP index, but I think they call it something else ;) -jj -- In this life we cannot do great things. We can only do small things with great love. -- Mother Teresa http://jjinux.blogspot.com/ From tungwaiyip at yahoo.com Thu Apr 29 07:36:53 2010 From: tungwaiyip at yahoo.com (Tung Wai Yip) Date: Wed, 28 Apr 2010 22:36:53 -0700 Subject: [Baypiggies] Python 2.6 build on a Debian box; batteries not included?? In-Reply-To: References: Message-ID: I'm using Python 2.6 that I downloaded and built on a Debian system. Things are working fine for me for a few weeks. Then I notice a problem when I failed to import zlib. >>> import zlib Traceback (most recent call last): File "", line 1, in ImportError: No module named zlib I'm so use to having all these Python modules included in the standard build I don't know what to do without them. I dig around more and find that they are suppose to be in a directory /usr/local/lib/python2.6/lib-dynload zlib.so is not in that directory. Not only is zlib.so missing, by comparing it with a equivalent directory from a Python 2.5 interpreter that comes with the system, I found that a number of modules are also missing. _hashlib.so _bsddb.so _curses.so _curses_panel.so _sqlite3.so _ssl.so bz2.so dbm.so readline.so rgbimg.so zlib.so Yes, even readline is missing! No wonder the interactive interpreter is acting weird. I think if I look at the output when I did ./configure I may find out some clue. Well it is several hundred lines long. Some line say yes and some line say no. So I can't really figure out what has went wrong. If anyone can give me more pointers it is greatly appreciated. Wai Yip tungwaiyip at tungwaiyip:~/download/Python-2.6.5$ cat 2010-04-27_configure.log checking for --enable-universalsdk... no checking for --with-universal-archs... 32-bit checking MACHDEP... linux2 checking EXTRAPLATDIR... checking machine type as reported by uname -m... i686 checking for --without-gcc... no checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for --with-cxx-main=... no checking for g++... g++ checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for AIX... no checking for --with-suffix... checking for case-insensitive build directory... no checking LIBRARY... libpython$(VERSION).a checking LINKCC... $(PURIFY) $(MAINCC) checking for --enable-shared... no checking for --enable-profiling... checking LDLIBRARY... libpython$(VERSION).a checking for ranlib... ranlib checking for ar... ar checking for svnversion... found checking for a BSD-compatible install... /usr/bin/install -c checking for --with-pydebug... no checking whether gcc accepts -fno-strict-aliasing... yes checking whether gcc accepts -OPT:Olimit=0... no checking whether gcc accepts -Olimit 1500... no checking whether gcc supports ParseTuple __format__... no checking whether pthreads are available without options... no checking whether gcc accepts -Kpthread... no checking whether gcc accepts -Kthread... no checking whether gcc accepts -pthread... yes checking whether g++ also accepts flags for thread support... yes checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking asm/types.h usability... yes checking asm/types.h presence... yes checking for asm/types.h... yes checking conio.h usability... no checking conio.h presence... no checking for conio.h... no checking curses.h usability... no checking curses.h presence... no checking for curses.h... no checking direct.h usability... no checking direct.h presence... no checking for direct.h... no checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking errno.h usability... yes checking errno.h presence... yes checking for errno.h... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking grp.h usability... yes checking grp.h presence... yes checking for grp.h... yes checking ieeefp.h usability... no checking ieeefp.h presence... no checking for ieeefp.h... no checking io.h usability... no checking io.h presence... no checking for io.h... no checking langinfo.h usability... yes checking langinfo.h presence... yes checking for langinfo.h... yes checking libintl.h usability... yes checking libintl.h presence... yes checking for libintl.h... yes checking ncurses.h usability... no checking ncurses.h presence... no checking for ncurses.h... no checking poll.h usability... yes checking poll.h presence... yes checking for poll.h... yes checking process.h usability... no checking process.h presence... no checking for process.h... no checking pthread.h usability... yes checking pthread.h presence... yes checking for pthread.h... yes checking shadow.h usability... yes checking shadow.h presence... yes checking for shadow.h... yes checking signal.h usability... yes checking signal.h presence... yes checking for signal.h... yes checking for stdint.h... (cached) yes checking stropts.h usability... yes checking stropts.h presence... yes checking for stropts.h... yes checking termios.h usability... yes checking termios.h presence... yes checking for termios.h... yes checking thread.h usability... no checking thread.h presence... no checking for thread.h... no checking for unistd.h... (cached) yes checking utime.h usability... yes checking utime.h presence... yes checking for utime.h... yes checking sys/audioio.h usability... no checking sys/audioio.h presence... no checking for sys/audioio.h... no checking sys/bsdtty.h usability... no checking sys/bsdtty.h presence... no checking for sys/bsdtty.h... no checking sys/epoll.h usability... yes checking sys/epoll.h presence... yes checking for sys/epoll.h... yes checking sys/event.h usability... no checking sys/event.h presence... no checking for sys/event.h... no checking sys/file.h usability... yes checking sys/file.h presence... yes checking for sys/file.h... yes checking sys/loadavg.h usability... no checking sys/loadavg.h presence... no checking for sys/loadavg.h... no checking sys/lock.h usability... no checking sys/lock.h presence... no checking for sys/lock.h... no checking sys/mkdev.h usability... no checking sys/mkdev.h presence... no checking for sys/mkdev.h... no checking sys/modem.h usability... no checking sys/modem.h presence... no checking for sys/modem.h... no checking sys/param.h usability... yes checking sys/param.h presence... yes checking for sys/param.h... yes checking sys/poll.h usability... yes checking sys/poll.h presence... yes checking for sys/poll.h... yes checking sys/select.h usability... yes checking sys/select.h presence... yes checking for sys/select.h... yes checking sys/socket.h usability... yes checking sys/socket.h presence... yes checking for sys/socket.h... yes checking sys/statvfs.h usability... yes checking sys/statvfs.h presence... yes checking for sys/statvfs.h... yes checking for sys/stat.h... (cached) yes checking sys/termio.h usability... no checking sys/termio.h presence... no checking for sys/termio.h... no checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking sys/times.h usability... yes checking sys/times.h presence... yes checking for sys/times.h... yes checking for sys/types.h... (cached) yes checking sys/un.h usability... yes checking sys/un.h presence... yes checking for sys/un.h... yes checking sys/utsname.h usability... yes checking sys/utsname.h presence... yes checking for sys/utsname.h... yes checking sys/wait.h usability... yes checking sys/wait.h presence... yes checking for sys/wait.h... yes checking pty.h usability... yes checking pty.h presence... yes checking for pty.h... yes checking libutil.h usability... no checking libutil.h presence... no checking for libutil.h... no checking sys/resource.h usability... yes checking sys/resource.h presence... yes checking for sys/resource.h... yes checking netpacket/packet.h usability... yes checking netpacket/packet.h presence... yes checking for netpacket/packet.h... yes checking sysexits.h usability... yes checking sysexits.h presence... yes checking for sysexits.h... yes checking bluetooth.h usability... no checking bluetooth.h presence... no checking for bluetooth.h... no checking bluetooth/bluetooth.h usability... no checking bluetooth/bluetooth.h presence... no checking for bluetooth/bluetooth.h... no checking linux/tipc.h usability... yes checking linux/tipc.h presence... yes checking for linux/tipc.h... yes checking for dirent.h that defines DIR... yes checking for library containing opendir... none required checking whether sys/types.h defines makedev... yes checking for term.h... no checking for linux/netlink.h... yes checking for clock_t in time.h... yes checking for makedev... yes checking Solaris LFS bug... no checking for mode_t... yes checking for off_t... yes checking for pid_t... yes checking return type of signal handlers... void checking for size_t... yes checking for uid_t in sys/types.h... yes checking for ssize_t... yes checking for int... yes checking size of int... 4 checking for long... yes checking size of long... 4 checking for void *... yes checking size of void *... 4 checking for short... yes checking size of short... 2 checking for float... yes checking size of float... 4 checking for double... yes checking size of double... 8 checking for fpos_t... yes checking size of fpos_t... 16 checking for size_t... (cached) yes checking size of size_t... 4 checking for pid_t... (cached) yes checking size of pid_t... 4 checking for long long support... yes checking for long long... yes checking size of long long... 8 checking for long double support... yes checking for long double... yes checking size of long double... 12 checking for _Bool support... yes checking for _Bool... yes checking size of _Bool... 1 checking for uintptr_t... yes checking for uintptr_t... (cached) yes checking size of uintptr_t... 4 checking size of off_t... 8 checking whether to enable large file support... yes checking size of time_t... 4 checking for pthread_t... yes checking size of pthread_t... 4 checking for --enable-toolbox-glue... no checking for --enable-framework... no checking for dyld... no checking SO... .so checking LDSHARED... $(CC) -shared checking CCSHARED... -fPIC checking LINKFORSHARED... -Xlinker -export-dynamic checking CFLAGSFORSHARED... checking SHLIBS... $(LIBS) checking for dlopen in -ldl... yes checking for shl_load in -ldld... no checking for library containing sem_init... -lpthread checking for textdomain in -lintl... no checking for t_open in -lnsl... no checking for socket in -lsocket... no checking for --with-libs... no checking for --with-system-ffi... checking for --with-signal-module... yes checking for --with-dec-threads... no checking for --with-threads... yes checking if PTHREAD_SCOPE_SYSTEM is supported... yes checking for pthread_sigmask... yes checking if --enable-ipv6 is specified... yes checking if RFC2553 API is available... yes checking ipv6 stack type... linux-glibc checking for OSX 10.5 SDK or later... no checking for --with-doc-strings... yes checking for --with-tsc... no checking for --with-pymalloc... yes checking for --with-wctype-functions... no checking for dlopen... yes checking DYNLOADFILE... dynload_shlib.o checking MACHDEP_OBJS... MACHDEP_OBJS checking for alarm... yes checking for setitimer... yes checking for getitimer... yes checking for bind_textdomain_codeset... yes checking for chown... yes checking for clock... yes checking for confstr... yes checking for ctermid... yes checking for execv... yes checking for fchmod... yes checking for fchown... yes checking for fork... yes checking for fpathconf... yes checking for ftime... yes checking for ftruncate... yes checking for gai_strerror... yes checking for getgroups... yes checking for getlogin... yes checking for getloadavg... yes checking for getpeername... yes checking for getpgid... yes checking for getpid... yes checking for getpriority... yes checking for getpwent... yes checking for getspnam... yes checking for getspent... yes checking for getsid... yes checking for getwd... yes checking for kill... yes checking for killpg... yes checking for lchmod... no checking for lchown... yes checking for lstat... yes checking for mkfifo... yes checking for mknod... yes checking for mktime... yes checking for mremap... yes checking for nice... yes checking for pathconf... yes checking for pause... yes checking for plock... no checking for poll... yes checking for pthread_init... no checking for putenv... yes checking for readlink... yes checking for realpath... yes checking for select... yes checking for setegid... yes checking for seteuid... yes checking for setgid... yes checking for setlocale... yes checking for setregid... yes checking for setreuid... yes checking for setsid... yes checking for setpgid... yes checking for setpgrp... yes checking for setuid... yes checking for setvbuf... yes checking for snprintf... yes checking for sigaction... yes checking for siginterrupt... yes checking for sigrelse... yes checking for strftime... yes checking for sysconf... yes checking for tcgetpgrp... yes checking for tcsetpgrp... yes checking for tempnam... yes checking for timegm... yes checking for times... yes checking for tmpfile... yes checking for tmpnam... yes checking for tmpnam_r... yes checking for truncate... yes checking for uname... yes checking for unsetenv... yes checking for utimes... yes checking for waitpid... yes checking for wait3... yes checking for wait4... yes checking for wcscoll... yes checking for _getpty... no checking for chroot... yes checking for link... yes checking for symlink... yes checking for fchdir... yes checking for fsync... yes checking for fdatasync... yes checking for epoll... yes checking for kqueue... no checking for ctermid_r... no checking for flock... yes checking for getpagesize... yes checking for true... true checking for inet_aton in -lc... yes checking for chflags... no checking for lchflags... no checking for inflateCopy in -lz... no checking for hstrerror... yes checking for inet_aton... yes checking for inet_pton... yes checking for setgroups... yes checking for openpty... no checking for openpty in -lutil... yes checking for forkpty... yes checking for memmove... yes checking for fseek64... no checking for fseeko... yes checking for fstatvfs... yes checking for ftell64... no checking for ftello... yes checking for statvfs... yes checking for dup2... yes checking for getcwd... yes checking for strdup... yes checking for getpgrp... yes checking for setpgrp... (cached) yes checking for gettimeofday... yes checking for major... yes checking for getaddrinfo... yes checking getaddrinfo bug... good checking for getnameinfo... yes checking whether time.h and sys/time.h may both be included... yes checking whether struct tm is in sys/time.h or time.h... time.h checking for struct tm.tm_zone... yes checking for struct stat.st_rdev... yes checking for struct stat.st_blksize... yes checking for struct stat.st_flags... no checking for struct stat.st_gen... no checking for struct stat.st_birthtime... no checking for struct stat.st_blocks... yes checking for time.h that defines altzone... no checking whether sys/select.h and sys/time.h may both be included... yes checking for addrinfo... yes checking for sockaddr_storage... yes checking whether char is unsigned... no checking for an ANSI C-conforming const... yes checking for working volatile... yes checking for working signed char... yes checking for prototypes... yes checking for variable length prototypes and stdarg.h... yes checking for socketpair... yes checking if sockaddr has sa_len member... no checking whether va_list is an array... no checking for gethostbyname_r... yes checking gethostbyname_r with 6 args... yes checking for __fpu_control... yes checking for --with-fpectl... no checking for --with-libm=STRING... default LIBM="-lm" checking for --with-libc=STRING... default LIBC="" checking for x87-style double rounding... yes checking whether tanh preserves the sign of zero... yes checking for acosh... yes checking for asinh... yes checking for atanh... yes checking for copysign... yes checking for expm1... yes checking for finite... yes checking for hypot... yes checking for log1p... yes checking whether isinf is declared... yes checking whether isnan is declared... yes checking whether isfinite is declared... yes checking wchar.h usability... yes checking wchar.h presence... yes checking for wchar.h... yes checking for wchar_t... yes checking size of wchar_t... 4 checking for UCS-4 tcl... no checking whether wchar_t is signed... yes checking what type to use for unicode... unsigned short checking whether byte ordering is bigendian... no checking whether right shift extends the sign bit... yes checking for getc_unlocked() and friends... yes checking how to link readline libs... none checking for rl_callback_handler_install in -lreadline... no checking for rl_pre_input_hook in -lreadline... no checking for rl_completion_display_matches_hook in -lreadline... no checking for rl_completion_matches in -lreadline... no checking for broken nice()... no checking for broken poll()... no checking for struct tm.tm_zone... (cached) yes checking for working tzset()... yes checking for tv_nsec in struct stat... yes checking for tv_nsec2 in struct stat... no checking whether mvwdelch is an expression... no checking whether WINDOW has _flags... no checking for is_term_resized... no checking for resize_term... no checking for resizeterm... no checking for /dev/ptmx... yes checking for /dev/ptc... no checking for %zd printf() format support... yes checking for socklen_t... yes checking for build directories... done configure: creating ./config.status config.status: creating Makefile.pre config.status: creating Modules/Setup.config config.status: creating pyconfig.h creating Modules/Setup creating Modules/Setup.local creating Makefile From andrew at atoulou.se Thu Apr 29 07:47:39 2010 From: andrew at atoulou.se (Andrew Toulouse) Date: Wed, 28 Apr 2010 22:47:39 -0700 Subject: [Baypiggies] Python 2.6 build on a Debian box; batteries not included?? In-Reply-To: References: Message-ID: <7AA7A787-E1F1-495A-B98F-CAEC1783801B@atoulou.se> Looks like you might not have some build dependencies. Have you tried running "apt-get build-dep python2.6"? As root (or with sudo), of course. --Andy On Apr 28, 2010, at 10:36 PM, Tung Wai Yip wrote: > I'm using Python 2.6 that I downloaded and built on a Debian system. Things are > working fine for me for a few weeks. Then I notice a problem when I failed to > import zlib. > >>>> import zlib > Traceback (most recent call last): > File "", line 1, in > ImportError: No module named zlib > > I'm so use to having all these Python modules included in the standard build I don't know what to do without them. I dig around more and find that they are suppose to be in a directory > > /usr/local/lib/python2.6/lib-dynload > > zlib.so is not in that directory. Not only is zlib.so missing, by comparing it with a equivalent directory from a Python 2.5 interpreter that comes with the system, I found that a number of modules are also missing. > > _hashlib.so > _bsddb.so > _curses.so > _curses_panel.so > _sqlite3.so > _ssl.so > bz2.so > dbm.so > readline.so > rgbimg.so > zlib.so > > > Yes, even readline is missing! No wonder the interactive interpreter is acting weird. > > I think if I look at the output when I did ./configure I may find out some clue. Well it is several hundred lines long. Some line say yes and some line say no. So I can't really figure out what has went wrong. > > If anyone can give me more pointers it is greatly appreciated. > > Wai Yip > > > > tungwaiyip at tungwaiyip:~/download/Python-2.6.5$ cat 2010-04-27_configure.log > checking for --enable-universalsdk... no > checking for --with-universal-archs... 32-bit > checking MACHDEP... linux2 > checking EXTRAPLATDIR... > checking machine type as reported by uname -m... i686 > checking for --without-gcc... no > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ISO C89... none needed > checking for --with-cxx-main=... no > checking for g++... g++ > checking how to run the C preprocessor... gcc -E > checking for grep that handles long lines and -e... /bin/grep > checking for egrep... /bin/grep -E > checking for AIX... no > checking for --with-suffix... > checking for case-insensitive build directory... no > checking LIBRARY... libpython$(VERSION).a > checking LINKCC... $(PURIFY) $(MAINCC) > checking for --enable-shared... no > checking for --enable-profiling... > checking LDLIBRARY... libpython$(VERSION).a > checking for ranlib... ranlib > checking for ar... ar > checking for svnversion... found > checking for a BSD-compatible install... /usr/bin/install -c > checking for --with-pydebug... no > checking whether gcc accepts -fno-strict-aliasing... yes > checking whether gcc accepts -OPT:Olimit=0... no > checking whether gcc accepts -Olimit 1500... no > checking whether gcc supports ParseTuple __format__... no > checking whether pthreads are available without options... no > checking whether gcc accepts -Kpthread... no > checking whether gcc accepts -Kthread... no > checking whether gcc accepts -pthread... yes > checking whether g++ also accepts flags for thread support... yes > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking asm/types.h usability... yes > checking asm/types.h presence... yes > checking for asm/types.h... yes > checking conio.h usability... no > checking conio.h presence... no > checking for conio.h... no > checking curses.h usability... no > checking curses.h presence... no > checking for curses.h... no > checking direct.h usability... no > checking direct.h presence... no > checking for direct.h... no > checking dlfcn.h usability... yes > checking dlfcn.h presence... yes > checking for dlfcn.h... yes > checking errno.h usability... yes > checking errno.h presence... yes > checking for errno.h... yes > checking fcntl.h usability... yes > checking fcntl.h presence... yes > checking for fcntl.h... yes > checking grp.h usability... yes > checking grp.h presence... yes > checking for grp.h... yes > checking ieeefp.h usability... no > checking ieeefp.h presence... no > checking for ieeefp.h... no > checking io.h usability... no > checking io.h presence... no > checking for io.h... no > checking langinfo.h usability... yes > checking langinfo.h presence... yes > checking for langinfo.h... yes > checking libintl.h usability... yes > checking libintl.h presence... yes > checking for libintl.h... yes > checking ncurses.h usability... no > checking ncurses.h presence... no > checking for ncurses.h... no > checking poll.h usability... yes > checking poll.h presence... yes > checking for poll.h... yes > checking process.h usability... no > checking process.h presence... no > checking for process.h... no > checking pthread.h usability... yes > checking pthread.h presence... yes > checking for pthread.h... yes > checking shadow.h usability... yes > checking shadow.h presence... yes > checking for shadow.h... yes > checking signal.h usability... yes > checking signal.h presence... yes > checking for signal.h... yes > checking for stdint.h... (cached) yes > checking stropts.h usability... yes > checking stropts.h presence... yes > checking for stropts.h... yes > checking termios.h usability... yes > checking termios.h presence... yes > checking for termios.h... yes > checking thread.h usability... no > checking thread.h presence... no > checking for thread.h... no > checking for unistd.h... (cached) yes > checking utime.h usability... yes > checking utime.h presence... yes > checking for utime.h... yes > checking sys/audioio.h usability... no > checking sys/audioio.h presence... no > checking for sys/audioio.h... no > checking sys/bsdtty.h usability... no > checking sys/bsdtty.h presence... no > checking for sys/bsdtty.h... no > checking sys/epoll.h usability... yes > checking sys/epoll.h presence... yes > checking for sys/epoll.h... yes > checking sys/event.h usability... no > checking sys/event.h presence... no > checking for sys/event.h... no > checking sys/file.h usability... yes > checking sys/file.h presence... yes > checking for sys/file.h... yes > checking sys/loadavg.h usability... no > checking sys/loadavg.h presence... no > checking for sys/loadavg.h... no > checking sys/lock.h usability... no > checking sys/lock.h presence... no > checking for sys/lock.h... no > checking sys/mkdev.h usability... no > checking sys/mkdev.h presence... no > checking for sys/mkdev.h... no > checking sys/modem.h usability... no > checking sys/modem.h presence... no > checking for sys/modem.h... no > checking sys/param.h usability... yes > checking sys/param.h presence... yes > checking for sys/param.h... yes > checking sys/poll.h usability... yes > checking sys/poll.h presence... yes > checking for sys/poll.h... yes > checking sys/select.h usability... yes > checking sys/select.h presence... yes > checking for sys/select.h... yes > checking sys/socket.h usability... yes > checking sys/socket.h presence... yes > checking for sys/socket.h... yes > checking sys/statvfs.h usability... yes > checking sys/statvfs.h presence... yes > checking for sys/statvfs.h... yes > checking for sys/stat.h... (cached) yes > checking sys/termio.h usability... no > checking sys/termio.h presence... no > checking for sys/termio.h... no > checking sys/time.h usability... yes > checking sys/time.h presence... yes > checking for sys/time.h... yes > checking sys/times.h usability... yes > checking sys/times.h presence... yes > checking for sys/times.h... yes > checking for sys/types.h... (cached) yes > checking sys/un.h usability... yes > checking sys/un.h presence... yes > checking for sys/un.h... yes > checking sys/utsname.h usability... yes > checking sys/utsname.h presence... yes > checking for sys/utsname.h... yes > checking sys/wait.h usability... yes > checking sys/wait.h presence... yes > checking for sys/wait.h... yes > checking pty.h usability... yes > checking pty.h presence... yes > checking for pty.h... yes > checking libutil.h usability... no > checking libutil.h presence... no > checking for libutil.h... no > checking sys/resource.h usability... yes > checking sys/resource.h presence... yes > checking for sys/resource.h... yes > checking netpacket/packet.h usability... yes > checking netpacket/packet.h presence... yes > checking for netpacket/packet.h... yes > checking sysexits.h usability... yes > checking sysexits.h presence... yes > checking for sysexits.h... yes > checking bluetooth.h usability... no > checking bluetooth.h presence... no > checking for bluetooth.h... no > checking bluetooth/bluetooth.h usability... no > checking bluetooth/bluetooth.h presence... no > checking for bluetooth/bluetooth.h... no > checking linux/tipc.h usability... yes > checking linux/tipc.h presence... yes > checking for linux/tipc.h... yes > checking for dirent.h that defines DIR... yes > checking for library containing opendir... none required > checking whether sys/types.h defines makedev... yes > checking for term.h... no > checking for linux/netlink.h... yes > checking for clock_t in time.h... yes > checking for makedev... yes > checking Solaris LFS bug... no > checking for mode_t... yes > checking for off_t... yes > checking for pid_t... yes > checking return type of signal handlers... void > checking for size_t... yes > checking for uid_t in sys/types.h... yes > checking for ssize_t... yes > checking for int... yes > checking size of int... 4 > checking for long... yes > checking size of long... 4 > checking for void *... yes > checking size of void *... 4 > checking for short... yes > checking size of short... 2 > checking for float... yes > checking size of float... 4 > checking for double... yes > checking size of double... 8 > checking for fpos_t... yes > checking size of fpos_t... 16 > checking for size_t... (cached) yes > checking size of size_t... 4 > checking for pid_t... (cached) yes > checking size of pid_t... 4 > checking for long long support... yes > checking for long long... yes > checking size of long long... 8 > checking for long double support... yes > checking for long double... yes > checking size of long double... 12 > checking for _Bool support... yes > checking for _Bool... yes > checking size of _Bool... 1 > checking for uintptr_t... yes > checking for uintptr_t... (cached) yes > checking size of uintptr_t... 4 > checking size of off_t... 8 > checking whether to enable large file support... yes > checking size of time_t... 4 > checking for pthread_t... yes > checking size of pthread_t... 4 > checking for --enable-toolbox-glue... no > checking for --enable-framework... no > checking for dyld... no > checking SO... .so > checking LDSHARED... $(CC) -shared > checking CCSHARED... -fPIC > checking LINKFORSHARED... -Xlinker -export-dynamic > checking CFLAGSFORSHARED... > checking SHLIBS... $(LIBS) > checking for dlopen in -ldl... yes > checking for shl_load in -ldld... no > checking for library containing sem_init... -lpthread > checking for textdomain in -lintl... no > checking for t_open in -lnsl... no > checking for socket in -lsocket... no > checking for --with-libs... no > checking for --with-system-ffi... > checking for --with-signal-module... yes > checking for --with-dec-threads... no > checking for --with-threads... yes > checking if PTHREAD_SCOPE_SYSTEM is supported... yes > checking for pthread_sigmask... yes > checking if --enable-ipv6 is specified... yes > checking if RFC2553 API is available... yes > checking ipv6 stack type... linux-glibc > checking for OSX 10.5 SDK or later... no > checking for --with-doc-strings... yes > checking for --with-tsc... no > checking for --with-pymalloc... yes > checking for --with-wctype-functions... no > checking for dlopen... yes > checking DYNLOADFILE... dynload_shlib.o > checking MACHDEP_OBJS... MACHDEP_OBJS > checking for alarm... yes > checking for setitimer... yes > checking for getitimer... yes > checking for bind_textdomain_codeset... yes > checking for chown... yes > checking for clock... yes > checking for confstr... yes > checking for ctermid... yes > checking for execv... yes > checking for fchmod... yes > checking for fchown... yes > checking for fork... yes > checking for fpathconf... yes > checking for ftime... yes > checking for ftruncate... yes > checking for gai_strerror... yes > checking for getgroups... yes > checking for getlogin... yes > checking for getloadavg... yes > checking for getpeername... yes > checking for getpgid... yes > checking for getpid... yes > checking for getpriority... yes > checking for getpwent... yes > checking for getspnam... yes > checking for getspent... yes > checking for getsid... yes > checking for getwd... yes > checking for kill... yes > checking for killpg... yes > checking for lchmod... no > checking for lchown... yes > checking for lstat... yes > checking for mkfifo... yes > checking for mknod... yes > checking for mktime... yes > checking for mremap... yes > checking for nice... yes > checking for pathconf... yes > checking for pause... yes > checking for plock... no > checking for poll... yes > checking for pthread_init... no > checking for putenv... yes > checking for readlink... yes > checking for realpath... yes > checking for select... yes > checking for setegid... yes > checking for seteuid... yes > checking for setgid... yes > checking for setlocale... yes > checking for setregid... yes > checking for setreuid... yes > checking for setsid... yes > checking for setpgid... yes > checking for setpgrp... yes > checking for setuid... yes > checking for setvbuf... yes > checking for snprintf... yes > checking for sigaction... yes > checking for siginterrupt... yes > checking for sigrelse... yes > checking for strftime... yes > checking for sysconf... yes > checking for tcgetpgrp... yes > checking for tcsetpgrp... yes > checking for tempnam... yes > checking for timegm... yes > checking for times... yes > checking for tmpfile... yes > checking for tmpnam... yes > checking for tmpnam_r... yes > checking for truncate... yes > checking for uname... yes > checking for unsetenv... yes > checking for utimes... yes > checking for waitpid... yes > checking for wait3... yes > checking for wait4... yes > checking for wcscoll... yes > checking for _getpty... no > checking for chroot... yes > checking for link... yes > checking for symlink... yes > checking for fchdir... yes > checking for fsync... yes > checking for fdatasync... yes > checking for epoll... yes > checking for kqueue... no > checking for ctermid_r... no > checking for flock... yes > checking for getpagesize... yes > checking for true... true > checking for inet_aton in -lc... yes > checking for chflags... no > checking for lchflags... no > checking for inflateCopy in -lz... no > checking for hstrerror... yes > checking for inet_aton... yes > checking for inet_pton... yes > checking for setgroups... yes > checking for openpty... no > checking for openpty in -lutil... yes > checking for forkpty... yes > checking for memmove... yes > checking for fseek64... no > checking for fseeko... yes > checking for fstatvfs... yes > checking for ftell64... no > checking for ftello... yes > checking for statvfs... yes > checking for dup2... yes > checking for getcwd... yes > checking for strdup... yes > checking for getpgrp... yes > checking for setpgrp... (cached) yes > checking for gettimeofday... yes > checking for major... yes > checking for getaddrinfo... yes > checking getaddrinfo bug... good > checking for getnameinfo... yes > checking whether time.h and sys/time.h may both be included... yes > checking whether struct tm is in sys/time.h or time.h... time.h > checking for struct tm.tm_zone... yes > checking for struct stat.st_rdev... yes > checking for struct stat.st_blksize... yes > checking for struct stat.st_flags... no > checking for struct stat.st_gen... no > checking for struct stat.st_birthtime... no > checking for struct stat.st_blocks... yes > checking for time.h that defines altzone... no > checking whether sys/select.h and sys/time.h may both be included... yes > checking for addrinfo... yes > checking for sockaddr_storage... yes > checking whether char is unsigned... no > checking for an ANSI C-conforming const... yes > checking for working volatile... yes > checking for working signed char... yes > checking for prototypes... yes > checking for variable length prototypes and stdarg.h... yes > checking for socketpair... yes > checking if sockaddr has sa_len member... no > checking whether va_list is an array... no > checking for gethostbyname_r... yes > checking gethostbyname_r with 6 args... yes > checking for __fpu_control... yes > checking for --with-fpectl... no > checking for --with-libm=STRING... default LIBM="-lm" > checking for --with-libc=STRING... default LIBC="" > checking for x87-style double rounding... yes > checking whether tanh preserves the sign of zero... yes > checking for acosh... yes > checking for asinh... yes > checking for atanh... yes > checking for copysign... yes > checking for expm1... yes > checking for finite... yes > checking for hypot... yes > checking for log1p... yes > checking whether isinf is declared... yes > checking whether isnan is declared... yes > checking whether isfinite is declared... yes > checking wchar.h usability... yes > checking wchar.h presence... yes > checking for wchar.h... yes > checking for wchar_t... yes > checking size of wchar_t... 4 > checking for UCS-4 tcl... no > checking whether wchar_t is signed... yes > checking what type to use for unicode... unsigned short > checking whether byte ordering is bigendian... no > checking whether right shift extends the sign bit... yes > checking for getc_unlocked() and friends... yes > checking how to link readline libs... none > checking for rl_callback_handler_install in -lreadline... no > checking for rl_pre_input_hook in -lreadline... no > checking for rl_completion_display_matches_hook in -lreadline... no > checking for rl_completion_matches in -lreadline... no > checking for broken nice()... no > checking for broken poll()... no > checking for struct tm.tm_zone... (cached) yes > checking for working tzset()... yes > checking for tv_nsec in struct stat... yes > checking for tv_nsec2 in struct stat... no > checking whether mvwdelch is an expression... no > checking whether WINDOW has _flags... no > checking for is_term_resized... no > checking for resize_term... no > checking for resizeterm... no > checking for /dev/ptmx... yes > checking for /dev/ptc... no > checking for %zd printf() format support... yes > checking for socklen_t... yes > checking for build directories... done > configure: creating ./config.status > config.status: creating Makefile.pre > config.status: creating Modules/Setup.config > config.status: creating pyconfig.h > creating Modules/Setup > creating Modules/Setup.local > creating Makefile > > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > http://mail.python.org/mailman/listinfo/baypiggies From wescpy at gmail.com Thu Apr 29 20:17:23 2010 From: wescpy at gmail.com (wesley chun) Date: Thu, 29 Apr 2010 11:17:23 -0700 Subject: [Baypiggies] ANN: Intro+Intermediate Python course, SF, May 10-12 In-Reply-To: References: Message-ID: *** FINAL REMINDER *** Need to get up-to-speed with Python as quickly as possible? Come join me, Wesley Chun, author of Prentice-Hall's bestseller "Core Python Programming," for a comprehensive Python course coming up this May in beautiful Northern California! I welcome new Python programmers as well as veterans who may have run into bugs that are difficult to explain and/or who want to learn more about objects, references, and Python's memory model. Come join us if you're looking for *more* than just a vanilla "beginners" class. Please pass on this note to whomever you think may be interested. I look forward to meeting you and your colleagues! feel free to pass around the flyer below. (Comprehensive) Introduction to Python Mon-Wed, 2010 May 10-12, 9am-5pm - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - (COMPREHENSIVE) INTRO+INTERMEDIATE PYTHON Although this course may appear to those new to Python, it is also perfect for those who have tinkered with it and want to "fill in the gaps" and/or want to get more in-depth formal training. ?It combines the best of both an introduction to the language as well as a "Python Internals" training course. We will immerse you in the world of Python in only a few days, showing you more than just its syntax (which you don't really need a book to learn, right?). Knowing more about how Python works under the covers, including the relationship between data objects and memory management, will make you a much more effective Python programmer coming out of the gate. 3 hands-on labs each day will help hammer the concepts home. Come find out why Google, Yahoo!, Disney, ILM/LucasFilm, VMware, NASA, Ubuntu, YouTube, and Red Hat all use Python. Users supporting or jumping to Plone, Zope, TurboGears, Pylons, Django, Google App Engine, Jython, IronPython, and Mailman will also benefit! PREVIEW 1: you will find (and can download) a video clip of a class session recorded live to get an idea of my lecture style and the interactive classroom environment at: http://cyberwebconsulting.com PREVIEW 2: Partnering with O'Reilly and Pearson, Safari Books Online has asked me to deliver a 1-hour webcast last Spring called "What is Python?". This was an online seminar based on a session that I've delivered at numerous conferences in the past. It will give you an idea of lecture style as well as an overview of the material covered in the course. info:http://www.safaribooksonline.com/events/WhatIsPython.html download (reg req'd): http://www.safaribooksonline.com/Corporate/DownloadAndResources/webcastInfo.php?page=WhatIsPython - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - WHERE: near the San Francisco Airport (SFO/San Bruno), CA, USA WEB: ? http://cyberwebconsulting.com FLYER: http://starship.python.net/crew/wesc/flyerPP1may10.pdf LOCALS: easy freeway (101/280/380) with lots of parking plus public transit (BART and CalTrain) access via the San Bruno stations, easily accessible from all parts of the Bay Area VISITORS: free shuttle to/from the airport, free high-speed internet, free breakfast and regular evening receptions; fully-equipped suites See website for costs, venue info, and registration. Hope to see you there! -- wesley - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - "Core Python Programming", Prentice Hall, (c)2007,2001 "Python Fundamentals", Prentice Hall, (c)2009 http://corepython.com wesley.j.chun :: wescpy-at-gmail.com python training and technical consulting cyberweb.consulting : silicon valley, ca http://cyberwebconsulting.com From mvoorhie at yahoo.com Thu Apr 29 20:50:29 2010 From: mvoorhie at yahoo.com (Mark Voorhies) Date: Thu, 29 Apr 2010 11:50:29 -0700 Subject: [Baypiggies] Python 2.6 build on a Debian box; batteries not included?? In-Reply-To: <7AA7A787-E1F1-495A-B98F-CAEC1783801B@atoulou.se> References: <7AA7A787-E1F1-495A-B98F-CAEC1783801B@atoulou.se> Message-ID: <201004291150.30163.mvoorhie@yahoo.com> Debian is currently transitioning to python2.6 for their next release (squeeze), so you might try installing the current python2.6 package from testing: http://packages.debian.org/squeeze/python2.6 (it includes libbz2-1.0 as a dependency, so should provide zlib support) There has been a lot of discussion of updating Debian's python packages for 2.6 on the debian-python mailing list: http://lists.debian.org/debian-python/ --Mark On Wednesday 28 April 2010 10:47 pm Andrew Toulouse wrote: > Looks like you might not have some build dependencies. Have you tried running "apt-get build-dep python2.6"? As root (or with sudo), of course. > > --Andy > > > On Apr 28, 2010, at 10:36 PM, Tung Wai Yip wrote: > > > I'm using Python 2.6 that I downloaded and built on a Debian system. Things are > > working fine for me for a few weeks. Then I notice a problem when I failed to > > import zlib. > > > >>>> import zlib > > Traceback (most recent call last): > > File "", line 1, in > > ImportError: No module named zlib > > > > I'm so use to having all these Python modules included in the standard build I don't know what to do without them. I dig around more and find that they are suppose to be in a directory > > > > /usr/local/lib/python2.6/lib-dynload > > > > zlib.so is not in that directory. Not only is zlib.so missing, by comparing it with a equivalent directory from a Python 2.5 interpreter that comes with the system, I found that a number of modules are also missing. > > > > _hashlib.so > > _bsddb.so > > _curses.so > > _curses_panel.so > > _sqlite3.so > > _ssl.so > > bz2.so > > dbm.so > > readline.so > > rgbimg.so > > zlib.so > > > > > > Yes, even readline is missing! No wonder the interactive interpreter is acting weird. > > > > I think if I look at the output when I did ./configure I may find out some clue. Well it is several hundred lines long. Some line say yes and some line say no. So I can't really figure out what has went wrong. > > > > If anyone can give me more pointers it is greatly appreciated. > > > > Wai Yip > > > > > > > > tungwaiyip at tungwaiyip:~/download/Python-2.6.5$ cat 2010-04-27_configure.log > > checking for --enable-universalsdk... no > > checking for --with-universal-archs... 32-bit > > checking MACHDEP... linux2 > > checking EXTRAPLATDIR... > > checking machine type as reported by uname -m... i686 > > checking for --without-gcc... no > > checking for gcc... gcc > > checking for C compiler default output file name... a.out > > checking whether the C compiler works... yes > > checking whether we are cross compiling... no > > checking for suffix of executables... > > checking for suffix of object files... o > > checking whether we are using the GNU C compiler... yes > > checking whether gcc accepts -g... yes > > checking for gcc option to accept ISO C89... none needed > > checking for --with-cxx-main=... no > > checking for g++... g++ > > checking how to run the C preprocessor... gcc -E > > checking for grep that handles long lines and -e... /bin/grep > > checking for egrep... /bin/grep -E > > checking for AIX... no > > checking for --with-suffix... > > checking for case-insensitive build directory... no > > checking LIBRARY... libpython$(VERSION).a > > checking LINKCC... $(PURIFY) $(MAINCC) > > checking for --enable-shared... no > > checking for --enable-profiling... > > checking LDLIBRARY... libpython$(VERSION).a > > checking for ranlib... ranlib > > checking for ar... ar > > checking for svnversion... found > > checking for a BSD-compatible install... /usr/bin/install -c > > checking for --with-pydebug... no > > checking whether gcc accepts -fno-strict-aliasing... yes > > checking whether gcc accepts -OPT:Olimit=0... no > > checking whether gcc accepts -Olimit 1500... no > > checking whether gcc supports ParseTuple __format__... no > > checking whether pthreads are available without options... no > > checking whether gcc accepts -Kpthread... no > > checking whether gcc accepts -Kthread... no > > checking whether gcc accepts -pthread... yes > > checking whether g++ also accepts flags for thread support... yes > > checking for ANSI C header files... yes > > checking for sys/types.h... yes > > checking for sys/stat.h... yes > > checking for stdlib.h... yes > > checking for string.h... yes > > checking for memory.h... yes > > checking for strings.h... yes > > checking for inttypes.h... yes > > checking for stdint.h... yes > > checking for unistd.h... yes > > checking asm/types.h usability... yes > > checking asm/types.h presence... yes > > checking for asm/types.h... yes > > checking conio.h usability... no > > checking conio.h presence... no > > checking for conio.h... no > > checking curses.h usability... no > > checking curses.h presence... no > > checking for curses.h... no > > checking direct.h usability... no > > checking direct.h presence... no > > checking for direct.h... no > > checking dlfcn.h usability... yes > > checking dlfcn.h presence... yes > > checking for dlfcn.h... yes > > checking errno.h usability... yes > > checking errno.h presence... yes > > checking for errno.h... yes > > checking fcntl.h usability... yes > > checking fcntl.h presence... yes > > checking for fcntl.h... yes > > checking grp.h usability... yes > > checking grp.h presence... yes > > checking for grp.h... yes > > checking ieeefp.h usability... no > > checking ieeefp.h presence... no > > checking for ieeefp.h... no > > checking io.h usability... no > > checking io.h presence... no > > checking for io.h... no > > checking langinfo.h usability... yes > > checking langinfo.h presence... yes > > checking for langinfo.h... yes > > checking libintl.h usability... yes > > checking libintl.h presence... yes > > checking for libintl.h... yes > > checking ncurses.h usability... no > > checking ncurses.h presence... no > > checking for ncurses.h... no > > checking poll.h usability... yes > > checking poll.h presence... yes > > checking for poll.h... yes > > checking process.h usability... no > > checking process.h presence... no > > checking for process.h... no > > checking pthread.h usability... yes > > checking pthread.h presence... yes > > checking for pthread.h... yes > > checking shadow.h usability... yes > > checking shadow.h presence... yes > > checking for shadow.h... yes > > checking signal.h usability... yes > > checking signal.h presence... yes > > checking for signal.h... yes > > checking for stdint.h... (cached) yes > > checking stropts.h usability... yes > > checking stropts.h presence... yes > > checking for stropts.h... yes > > checking termios.h usability... yes > > checking termios.h presence... yes > > checking for termios.h... yes > > checking thread.h usability... no > > checking thread.h presence... no > > checking for thread.h... no > > checking for unistd.h... (cached) yes > > checking utime.h usability... yes > > checking utime.h presence... yes > > checking for utime.h... yes > > checking sys/audioio.h usability... no > > checking sys/audioio.h presence... no > > checking for sys/audioio.h... no > > checking sys/bsdtty.h usability... no > > checking sys/bsdtty.h presence... no > > checking for sys/bsdtty.h... no > > checking sys/epoll.h usability... yes > > checking sys/epoll.h presence... yes > > checking for sys/epoll.h... yes > > checking sys/event.h usability... no > > checking sys/event.h presence... no > > checking for sys/event.h... no > > checking sys/file.h usability... yes > > checking sys/file.h presence... yes > > checking for sys/file.h... yes > > checking sys/loadavg.h usability... no > > checking sys/loadavg.h presence... no > > checking for sys/loadavg.h... no > > checking sys/lock.h usability... no > > checking sys/lock.h presence... no > > checking for sys/lock.h... no > > checking sys/mkdev.h usability... no > > checking sys/mkdev.h presence... no > > checking for sys/mkdev.h... no > > checking sys/modem.h usability... no > > checking sys/modem.h presence... no > > checking for sys/modem.h... no > > checking sys/param.h usability... yes > > checking sys/param.h presence... yes > > checking for sys/param.h... yes > > checking sys/poll.h usability... yes > > checking sys/poll.h presence... yes > > checking for sys/poll.h... yes > > checking sys/select.h usability... yes > > checking sys/select.h presence... yes > > checking for sys/select.h... yes > > checking sys/socket.h usability... yes > > checking sys/socket.h presence... yes > > checking for sys/socket.h... yes > > checking sys/statvfs.h usability... yes > > checking sys/statvfs.h presence... yes > > checking for sys/statvfs.h... yes > > checking for sys/stat.h... (cached) yes > > checking sys/termio.h usability... no > > checking sys/termio.h presence... no > > checking for sys/termio.h... no > > checking sys/time.h usability... yes > > checking sys/time.h presence... yes > > checking for sys/time.h... yes > > checking sys/times.h usability... yes > > checking sys/times.h presence... yes > > checking for sys/times.h... yes > > checking for sys/types.h... (cached) yes > > checking sys/un.h usability... yes > > checking sys/un.h presence... yes > > checking for sys/un.h... yes > > checking sys/utsname.h usability... yes > > checking sys/utsname.h presence... yes > > checking for sys/utsname.h... yes > > checking sys/wait.h usability... yes > > checking sys/wait.h presence... yes > > checking for sys/wait.h... yes > > checking pty.h usability... yes > > checking pty.h presence... yes > > checking for pty.h... yes > > checking libutil.h usability... no > > checking libutil.h presence... no > > checking for libutil.h... no > > checking sys/resource.h usability... yes > > checking sys/resource.h presence... yes > > checking for sys/resource.h... yes > > checking netpacket/packet.h usability... yes > > checking netpacket/packet.h presence... yes > > checking for netpacket/packet.h... yes > > checking sysexits.h usability... yes > > checking sysexits.h presence... yes > > checking for sysexits.h... yes > > checking bluetooth.h usability... no > > checking bluetooth.h presence... no > > checking for bluetooth.h... no > > checking bluetooth/bluetooth.h usability... no > > checking bluetooth/bluetooth.h presence... no > > checking for bluetooth/bluetooth.h... no > > checking linux/tipc.h usability... yes > > checking linux/tipc.h presence... yes > > checking for linux/tipc.h... yes > > checking for dirent.h that defines DIR... yes > > checking for library containing opendir... none required > > checking whether sys/types.h defines makedev... yes > > checking for term.h... no > > checking for linux/netlink.h... yes > > checking for clock_t in time.h... yes > > checking for makedev... yes > > checking Solaris LFS bug... no > > checking for mode_t... yes > > checking for off_t... yes > > checking for pid_t... yes > > checking return type of signal handlers... void > > checking for size_t... yes > > checking for uid_t in sys/types.h... yes > > checking for ssize_t... yes > > checking for int... yes > > checking size of int... 4 > > checking for long... yes > > checking size of long... 4 > > checking for void *... yes > > checking size of void *... 4 > > checking for short... yes > > checking size of short... 2 > > checking for float... yes > > checking size of float... 4 > > checking for double... yes > > checking size of double... 8 > > checking for fpos_t... yes > > checking size of fpos_t... 16 > > checking for size_t... (cached) yes > > checking size of size_t... 4 > > checking for pid_t... (cached) yes > > checking size of pid_t... 4 > > checking for long long support... yes > > checking for long long... yes > > checking size of long long... 8 > > checking for long double support... yes > > checking for long double... yes > > checking size of long double... 12 > > checking for _Bool support... yes > > checking for _Bool... yes > > checking size of _Bool... 1 > > checking for uintptr_t... yes > > checking for uintptr_t... (cached) yes > > checking size of uintptr_t... 4 > > checking size of off_t... 8 > > checking whether to enable large file support... yes > > checking size of time_t... 4 > > checking for pthread_t... yes > > checking size of pthread_t... 4 > > checking for --enable-toolbox-glue... no > > checking for --enable-framework... no > > checking for dyld... no > > checking SO... .so > > checking LDSHARED... $(CC) -shared > > checking CCSHARED... -fPIC > > checking LINKFORSHARED... -Xlinker -export-dynamic > > checking CFLAGSFORSHARED... > > checking SHLIBS... $(LIBS) > > checking for dlopen in -ldl... yes > > checking for shl_load in -ldld... no > > checking for library containing sem_init... -lpthread > > checking for textdomain in -lintl... no > > checking for t_open in -lnsl... no > > checking for socket in -lsocket... no > > checking for --with-libs... no > > checking for --with-system-ffi... > > checking for --with-signal-module... yes > > checking for --with-dec-threads... no > > checking for --with-threads... yes > > checking if PTHREAD_SCOPE_SYSTEM is supported... yes > > checking for pthread_sigmask... yes > > checking if --enable-ipv6 is specified... yes > > checking if RFC2553 API is available... yes > > checking ipv6 stack type... linux-glibc > > checking for OSX 10.5 SDK or later... no > > checking for --with-doc-strings... yes > > checking for --with-tsc... no > > checking for --with-pymalloc... yes > > checking for --with-wctype-functions... no > > checking for dlopen... yes > > checking DYNLOADFILE... dynload_shlib.o > > checking MACHDEP_OBJS... MACHDEP_OBJS > > checking for alarm... yes > > checking for setitimer... yes > > checking for getitimer... yes > > checking for bind_textdomain_codeset... yes > > checking for chown... yes > > checking for clock... yes > > checking for confstr... yes > > checking for ctermid... yes > > checking for execv... yes > > checking for fchmod... yes > > checking for fchown... yes > > checking for fork... yes > > checking for fpathconf... yes > > checking for ftime... yes > > checking for ftruncate... yes > > checking for gai_strerror... yes > > checking for getgroups... yes > > checking for getlogin... yes > > checking for getloadavg... yes > > checking for getpeername... yes > > checking for getpgid... yes > > checking for getpid... yes > > checking for getpriority... yes > > checking for getpwent... yes > > checking for getspnam... yes > > checking for getspent... yes > > checking for getsid... yes > > checking for getwd... yes > > checking for kill... yes > > checking for killpg... yes > > checking for lchmod... no > > checking for lchown... yes > > checking for lstat... yes > > checking for mkfifo... yes > > checking for mknod... yes > > checking for mktime... yes > > checking for mremap... yes > > checking for nice... yes > > checking for pathconf... yes > > checking for pause... yes > > checking for plock... no > > checking for poll... yes > > checking for pthread_init... no > > checking for putenv... yes > > checking for readlink... yes > > checking for realpath... yes > > checking for select... yes > > checking for setegid... yes > > checking for seteuid... yes > > checking for setgid... yes > > checking for setlocale... yes > > checking for setregid... yes > > checking for setreuid... yes > > checking for setsid... yes > > checking for setpgid... yes > > checking for setpgrp... yes > > checking for setuid... yes > > checking for setvbuf... yes > > checking for snprintf... yes > > checking for sigaction... yes > > checking for siginterrupt... yes > > checking for sigrelse... yes > > checking for strftime... yes > > checking for sysconf... yes > > checking for tcgetpgrp... yes > > checking for tcsetpgrp... yes > > checking for tempnam... yes > > checking for timegm... yes > > checking for times... yes > > checking for tmpfile... yes > > checking for tmpnam... yes > > checking for tmpnam_r... yes > > checking for truncate... yes > > checking for uname... yes > > checking for unsetenv... yes > > checking for utimes... yes > > checking for waitpid... yes > > checking for wait3... yes > > checking for wait4... yes > > checking for wcscoll... yes > > checking for _getpty... no > > checking for chroot... yes > > checking for link... yes > > checking for symlink... yes > > checking for fchdir... yes > > checking for fsync... yes > > checking for fdatasync... yes > > checking for epoll... yes > > checking for kqueue... no > > checking for ctermid_r... no > > checking for flock... yes > > checking for getpagesize... yes > > checking for true... true > > checking for inet_aton in -lc... yes > > checking for chflags... no > > checking for lchflags... no > > checking for inflateCopy in -lz... no > > checking for hstrerror... yes > > checking for inet_aton... yes > > checking for inet_pton... yes > > checking for setgroups... yes > > checking for openpty... no > > checking for openpty in -lutil... yes > > checking for forkpty... yes > > checking for memmove... yes > > checking for fseek64... no > > checking for fseeko... yes > > checking for fstatvfs... yes > > checking for ftell64... no > > checking for ftello... yes > > checking for statvfs... yes > > checking for dup2... yes > > checking for getcwd... yes > > checking for strdup... yes > > checking for getpgrp... yes > > checking for setpgrp... (cached) yes > > checking for gettimeofday... yes > > checking for major... yes > > checking for getaddrinfo... yes > > checking getaddrinfo bug... good > > checking for getnameinfo... yes > > checking whether time.h and sys/time.h may both be included... yes > > checking whether struct tm is in sys/time.h or time.h... time.h > > checking for struct tm.tm_zone... yes > > checking for struct stat.st_rdev... yes > > checking for struct stat.st_blksize... yes > > checking for struct stat.st_flags... no > > checking for struct stat.st_gen... no > > checking for struct stat.st_birthtime... no > > checking for struct stat.st_blocks... yes > > checking for time.h that defines altzone... no > > checking whether sys/select.h and sys/time.h may both be included... yes > > checking for addrinfo... yes > > checking for sockaddr_storage... yes > > checking whether char is unsigned... no > > checking for an ANSI C-conforming const... yes > > checking for working volatile... yes > > checking for working signed char... yes > > checking for prototypes... yes > > checking for variable length prototypes and stdarg.h... yes > > checking for socketpair... yes > > checking if sockaddr has sa_len member... no > > checking whether va_list is an array... no > > checking for gethostbyname_r... yes > > checking gethostbyname_r with 6 args... yes > > checking for __fpu_control... yes > > checking for --with-fpectl... no > > checking for --with-libm=STRING... default LIBM="-lm" > > checking for --with-libc=STRING... default LIBC="" > > checking for x87-style double rounding... yes > > checking whether tanh preserves the sign of zero... yes > > checking for acosh... yes > > checking for asinh... yes > > checking for atanh... yes > > checking for copysign... yes > > checking for expm1... yes > > checking for finite... yes > > checking for hypot... yes > > checking for log1p... yes > > checking whether isinf is declared... yes > > checking whether isnan is declared... yes > > checking whether isfinite is declared... yes > > checking wchar.h usability... yes > > checking wchar.h presence... yes > > checking for wchar.h... yes > > checking for wchar_t... yes > > checking size of wchar_t... 4 > > checking for UCS-4 tcl... no > > checking whether wchar_t is signed... yes > > checking what type to use for unicode... unsigned short > > checking whether byte ordering is bigendian... no > > checking whether right shift extends the sign bit... yes > > checking for getc_unlocked() and friends... yes > > checking how to link readline libs... none > > checking for rl_callback_handler_install in -lreadline... no > > checking for rl_pre_input_hook in -lreadline... no > > checking for rl_completion_display_matches_hook in -lreadline... no > > checking for rl_completion_matches in -lreadline... no > > checking for broken nice()... no > > checking for broken poll()... no > > checking for struct tm.tm_zone... (cached) yes > > checking for working tzset()... yes > > checking for tv_nsec in struct stat... yes > > checking for tv_nsec2 in struct stat... no > > checking whether mvwdelch is an expression... no > > checking whether WINDOW has _flags... no > > checking for is_term_resized... no > > checking for resize_term... no > > checking for resizeterm... no > > checking for /dev/ptmx... yes > > checking for /dev/ptc... no > > checking for %zd printf() format support... yes > > checking for socklen_t... yes > > checking for build directories... done > > configure: creating ./config.status > > config.status: creating Makefile.pre > > config.status: creating Modules/Setup.config > > config.status: creating pyconfig.h > > creating Modules/Setup > > creating Modules/Setup.local > > creating Makefile > > > > _______________________________________________ > > Baypiggies mailing list > > Baypiggies at python.org > > To change your subscription options or unsubscribe: > > http://mail.python.org/mailman/listinfo/baypiggies > > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > http://mail.python.org/mailman/listinfo/baypiggies > From glen at glenjarvis.com Thu Apr 29 21:30:06 2010 From: glen at glenjarvis.com (Glen Jarvis) Date: Thu, 29 Apr 2010 12:30:06 -0700 Subject: [Baypiggies] Free subversion training Message-ID: When writing Python code, you will eventually run into a situation where you need to interact with a repository. If you have never used a repository before (subversion or any kind), then this free course for a few hours will be helpful. I'm giving this course for some of my colleagues at work and we have room for a few more. I'm hoping to hold a training on Wednesday 5-May around 6pm. This is not set in stone yet because because I want to get feedback on all those interested in coming and find a schedule that works for everyone. This *will* be at UC Berkeley in Stanley Hall (that part isn't flexible). We will start off with the very basics. We give you a sample repository -- a complete toy that you couldn't mess up if you tried -- so you can do what you want in training. We'll learn how to check out code, how to make updates, and how the repository serializes those updates. Thus, we learn why it's important to do an update before a check-in. We will learn how to then do a check-in and, if there are conflicts, how to resolve them. We will, of course, learn what a conflict is, why it exists and what it means. Plan for this to last for two hours, although we can be flexible depending upon the needs of the group that evening. This is completely lab based where people will be working in pairs. One of you will add some "code" and the other will update that "code" in scenarios that I set up to demonstrate all of the above. You do *not* need to know how to program to take this course. "Code" in our example will be text files with different words on each line. What we won't cover is how to merge branches, make tags, do svnadmin, or other advanced features. We can hold an intermediate class for such things if you're interested. This, however, is a beginners class at a beginners level meant to make you much more comfortable using the repository. You will be given a small recipe booklet on all the above and much more, that you can take with you. Please let me know if you are interested so we can make final arrangements. We have one participant for certain and it works well if we have at least one pair (or two pairs) of people. We can host up to 20 people. You will need your own laptop with wireless capability and to have the subversion client program already installed. Cheers, Glen -- Whatever you can do or imagine, begin it; boldness has beauty, magic, and power in it. -- Goethe -------------- next part -------------- An HTML attachment was scrubbed... URL: From akwright at mac.com Thu Apr 29 20:41:22 2010 From: akwright at mac.com (Kevin Wright) Date: Thu, 29 Apr 2010 11:41:22 -0700 Subject: [Baypiggies] Interesting video regarding Python porting/debugging Message-ID: <4264B062-C2B1-401E-B366-C44F233FEA76@mac.com> Hi, I just ran across this video by a guy who wrote some automation for porting python 2 to python 3 for the libraries written in C. It also shows some interesting debugging examples: http://press.redhat.com/2010/04/27/fedora-13-spotlight-feature-exploring-new-frontiers-of-python-development/ here's an excerpt from the blurb on this page: SystemTap includes its own scripting language, and David Malcolm used this capability to develop a Python-based ?top? function, to show Python activity across the entire running system. But beyond that, he also created an additional script that developers can use to see their applications calling and returning from individual Python functions. The combination of these tools in Fedora 13 can give developers immediate insight not only into their program?s flow, but also into how their application spends its time, and where bottlenecks might be occurring. Hope you find this as interesting as I did. Disclaimer. I work for Red Hat which sponsors Fedora. --Kevin From tungwaiyip at yahoo.com Fri Apr 30 07:12:54 2010 From: tungwaiyip at yahoo.com (Tung Wai Yip) Date: Thu, 29 Apr 2010 22:12:54 -0700 Subject: [Baypiggies] Python 2.6 build on a Debian box; batteries not included?? In-Reply-To: <201004291150.30163.mvoorhie@yahoo.com> References: <7AA7A787-E1F1-495A-B98F-CAEC1783801B@atoulou.se> <201004291150.30163.mvoorhie@yahoo.com> Message-ID: Thank you for all the information. I'm rather uninitiated with Debian. But I finally managed to get Python 2.6 setup with these steps: 1. The python2.6 package is available in squeeze, the next release of Debian (I'm on lenny). It order to access it, backup and edit /etc/apt/sources.list. Add the last 2 lines. # cat /etc/apt/sources.list deb http://ftp.us.debian.org/debian lenny main contrib deb http://security.debian.org/ lenny/updates main deb-src http://ftp.us.debian.org/debian lenny main contrib deb http://ftp.us.debian.org/debian squeeze main contrib deb-src http://ftp.us.debian.org/debian squeeze main contrib 2. Then run these as root # apt-get update # apt-get build-dep python2.6 # apt-get install python2.6 # /usr/bin/python2.6 Wai Yip > Debian is currently transitioning to python2.6 for their next release > (squeeze), so you might try installing the current python2.6 package from > testing: > http://packages.debian.org/squeeze/python2.6 > (it includes libbz2-1.0 as a dependency, so should provide zlib support) > > There has been a lot of discussion of updating Debian's python packages > for > 2.6 on the debian-python mailing list: > http://lists.debian.org/debian-python/ > > --Mark > > On Wednesday 28 April 2010 10:47 pm Andrew Toulouse wrote: >> Looks like you might not have some build dependencies. Have you tried > running "apt-get build-dep python2.6"? As root (or with sudo), of course. >> >> --Andy >> >> >> On Apr 28, 2010, at 10:36 PM, Tung Wai Yip wrote: >> >> > I'm using Python 2.6 that I downloaded and built on a Debian system. > Things are >> > working fine for me for a few weeks. Then I notice a problem when I >> failed > to >> > import zlib. >> > >> >>>> import zlib >> > Traceback (most recent call last): >> > File "", line 1, in >> > ImportError: No module named zlib >> > >> > I'm so use to having all these Python modules included in the standard > build I don't know what to do without them. I dig around more and find > that > they are suppose to be in a directory >> > >> > /usr/local/lib/python2.6/lib-dynload >> > >> > zlib.so is not in that directory. Not only is zlib.so missing, by > comparing it with a equivalent directory from a Python 2.5 interpreter > that > comes with the system, I found that a number of modules are also missing. >> > >> > _hashlib.so >> > _bsddb.so >> > _curses.so >> > _curses_panel.so >> > _sqlite3.so >> > _ssl.so >> > bz2.so >> > dbm.so >> > readline.so >> > rgbimg.so >> > zlib.so >> > >> > >> > Yes, even readline is missing! No wonder the interactive interpreter >> is > acting weird. >> > >> > I think if I look at the output when I did ./configure I may find out >> some > clue. Well it is several hundred lines long. Some line say yes and some > line > say no. So I can't really figure out what has went wrong. >> > >> > If anyone can give me more pointers it is greatly appreciated. >> > >> > Wai Yip >> > >> > >> > >> > tungwaiyip at tungwaiyip:~/download/Python-2.6.5$ cat > 2010-04-27_configure.log >> > checking for --enable-universalsdk... no >> > checking for --with-universal-archs... 32-bit >> > checking MACHDEP... linux2 >> > checking EXTRAPLATDIR... >> > checking machine type as reported by uname -m... i686 >> > checking for --without-gcc... no >> > checking for gcc... gcc >> > checking for C compiler default output file name... a.out >> > checking whether the C compiler works... yes >> > checking whether we are cross compiling... no >> > checking for suffix of executables... >> > checking for suffix of object files... o >> > checking whether we are using the GNU C compiler... yes >> > checking whether gcc accepts -g... yes >> > checking for gcc option to accept ISO C89... none needed >> > checking for --with-cxx-main=... no >> > checking for g++... g++ >> > checking how to run the C preprocessor... gcc -E >> > checking for grep that handles long lines and -e... /bin/grep >> > checking for egrep... /bin/grep -E >> > checking for AIX... no >> > checking for --with-suffix... >> > checking for case-insensitive build directory... no >> > checking LIBRARY... libpython$(VERSION).a >> > checking LINKCC... $(PURIFY) $(MAINCC) >> > checking for --enable-shared... no >> > checking for --enable-profiling... >> > checking LDLIBRARY... libpython$(VERSION).a >> > checking for ranlib... ranlib >> > checking for ar... ar >> > checking for svnversion... found >> > checking for a BSD-compatible install... /usr/bin/install -c >> > checking for --with-pydebug... no >> > checking whether gcc accepts -fno-strict-aliasing... yes >> > checking whether gcc accepts -OPT:Olimit=0... no >> > checking whether gcc accepts -Olimit 1500... no >> > checking whether gcc supports ParseTuple __format__... no >> > checking whether pthreads are available without options... no >> > checking whether gcc accepts -Kpthread... no >> > checking whether gcc accepts -Kthread... no >> > checking whether gcc accepts -pthread... yes >> > checking whether g++ also accepts flags for thread support... yes >> > checking for ANSI C header files... yes >> > checking for sys/types.h... yes >> > checking for sys/stat.h... yes >> > checking for stdlib.h... yes >> > checking for string.h... yes >> > checking for memory.h... yes >> > checking for strings.h... yes >> > checking for inttypes.h... yes >> > checking for stdint.h... yes >> > checking for unistd.h... yes >> > checking asm/types.h usability... yes >> > checking asm/types.h presence... yes >> > checking for asm/types.h... yes >> > checking conio.h usability... no >> > checking conio.h presence... no >> > checking for conio.h... no >> > checking curses.h usability... no >> > checking curses.h presence... no >> > checking for curses.h... no >> > checking direct.h usability... no >> > checking direct.h presence... no >> > checking for direct.h... no >> > checking dlfcn.h usability... yes >> > checking dlfcn.h presence... yes >> > checking for dlfcn.h... yes >> > checking errno.h usability... yes >> > checking errno.h presence... yes >> > checking for errno.h... yes >> > checking fcntl.h usability... yes >> > checking fcntl.h presence... yes >> > checking for fcntl.h... yes >> > checking grp.h usability... yes >> > checking grp.h presence... yes >> > checking for grp.h... yes >> > checking ieeefp.h usability... no >> > checking ieeefp.h presence... no >> > checking for ieeefp.h... no >> > checking io.h usability... no >> > checking io.h presence... no >> > checking for io.h... no >> > checking langinfo.h usability... yes >> > checking langinfo.h presence... yes >> > checking for langinfo.h... yes >> > checking libintl.h usability... yes >> > checking libintl.h presence... yes >> > checking for libintl.h... yes >> > checking ncurses.h usability... no >> > checking ncurses.h presence... no >> > checking for ncurses.h... no >> > checking poll.h usability... yes >> > checking poll.h presence... yes >> > checking for poll.h... yes >> > checking process.h usability... no >> > checking process.h presence... no >> > checking for process.h... no >> > checking pthread.h usability... yes >> > checking pthread.h presence... yes >> > checking for pthread.h... yes >> > checking shadow.h usability... yes >> > checking shadow.h presence... yes >> > checking for shadow.h... yes >> > checking signal.h usability... yes >> > checking signal.h presence... yes >> > checking for signal.h... yes >> > checking for stdint.h... (cached) yes >> > checking stropts.h usability... yes >> > checking stropts.h presence... yes >> > checking for stropts.h... yes >> > checking termios.h usability... yes >> > checking termios.h presence... yes >> > checking for termios.h... yes >> > checking thread.h usability... no >> > checking thread.h presence... no >> > checking for thread.h... no >> > checking for unistd.h... (cached) yes >> > checking utime.h usability... yes >> > checking utime.h presence... yes >> > checking for utime.h... yes >> > checking sys/audioio.h usability... no >> > checking sys/audioio.h presence... no >> > checking for sys/audioio.h... no >> > checking sys/bsdtty.h usability... no >> > checking sys/bsdtty.h presence... no >> > checking for sys/bsdtty.h... no >> > checking sys/epoll.h usability... yes >> > checking sys/epoll.h presence... yes >> > checking for sys/epoll.h... yes >> > checking sys/event.h usability... no >> > checking sys/event.h presence... no >> > checking for sys/event.h... no >> > checking sys/file.h usability... yes >> > checking sys/file.h presence... yes >> > checking for sys/file.h... yes >> > checking sys/loadavg.h usability... no >> > checking sys/loadavg.h presence... no >> > checking for sys/loadavg.h... no >> > checking sys/lock.h usability... no >> > checking sys/lock.h presence... no >> > checking for sys/lock.h... no >> > checking sys/mkdev.h usability... no >> > checking sys/mkdev.h presence... no >> > checking for sys/mkdev.h... no >> > checking sys/modem.h usability... no >> > checking sys/modem.h presence... no >> > checking for sys/modem.h... no >> > checking sys/param.h usability... yes >> > checking sys/param.h presence... yes >> > checking for sys/param.h... yes >> > checking sys/poll.h usability... yes >> > checking sys/poll.h presence... yes >> > checking for sys/poll.h... yes >> > checking sys/select.h usability... yes >> > checking sys/select.h presence... yes >> > checking for sys/select.h... yes >> > checking sys/socket.h usability... yes >> > checking sys/socket.h presence... yes >> > checking for sys/socket.h... yes >> > checking sys/statvfs.h usability... yes >> > checking sys/statvfs.h presence... yes >> > checking for sys/statvfs.h... yes >> > checking for sys/stat.h... (cached) yes >> > checking sys/termio.h usability... no >> > checking sys/termio.h presence... no >> > checking for sys/termio.h... no >> > checking sys/time.h usability... yes >> > checking sys/time.h presence... yes >> > checking for sys/time.h... yes >> > checking sys/times.h usability... yes >> > checking sys/times.h presence... yes >> > checking for sys/times.h... yes >> > checking for sys/types.h... (cached) yes >> > checking sys/un.h usability... yes >> > checking sys/un.h presence... yes >> > checking for sys/un.h... yes >> > checking sys/utsname.h usability... yes >> > checking sys/utsname.h presence... yes >> > checking for sys/utsname.h... yes >> > checking sys/wait.h usability... yes >> > checking sys/wait.h presence... yes >> > checking for sys/wait.h... yes >> > checking pty.h usability... yes >> > checking pty.h presence... yes >> > checking for pty.h... yes >> > checking libutil.h usability... no >> > checking libutil.h presence... no >> > checking for libutil.h... no >> > checking sys/resource.h usability... yes >> > checking sys/resource.h presence... yes >> > checking for sys/resource.h... yes >> > checking netpacket/packet.h usability... yes >> > checking netpacket/packet.h presence... yes >> > checking for netpacket/packet.h... yes >> > checking sysexits.h usability... yes >> > checking sysexits.h presence... yes >> > checking for sysexits.h... yes >> > checking bluetooth.h usability... no >> > checking bluetooth.h presence... no >> > checking for bluetooth.h... no >> > checking bluetooth/bluetooth.h usability... no >> > checking bluetooth/bluetooth.h presence... no >> > checking for bluetooth/bluetooth.h... no >> > checking linux/tipc.h usability... yes >> > checking linux/tipc.h presence... yes >> > checking for linux/tipc.h... yes >> > checking for dirent.h that defines DIR... yes >> > checking for library containing opendir... none required >> > checking whether sys/types.h defines makedev... yes >> > checking for term.h... no >> > checking for linux/netlink.h... yes >> > checking for clock_t in time.h... yes >> > checking for makedev... yes >> > checking Solaris LFS bug... no >> > checking for mode_t... yes >> > checking for off_t... yes >> > checking for pid_t... yes >> > checking return type of signal handlers... void >> > checking for size_t... yes >> > checking for uid_t in sys/types.h... yes >> > checking for ssize_t... yes >> > checking for int... yes >> > checking size of int... 4 >> > checking for long... yes >> > checking size of long... 4 >> > checking for void *... yes >> > checking size of void *... 4 >> > checking for short... yes >> > checking size of short... 2 >> > checking for float... yes >> > checking size of float... 4 >> > checking for double... yes >> > checking size of double... 8 >> > checking for fpos_t... yes >> > checking size of fpos_t... 16 >> > checking for size_t... (cached) yes >> > checking size of size_t... 4 >> > checking for pid_t... (cached) yes >> > checking size of pid_t... 4 >> > checking for long long support... yes >> > checking for long long... yes >> > checking size of long long... 8 >> > checking for long double support... yes >> > checking for long double... yes >> > checking size of long double... 12 >> > checking for _Bool support... yes >> > checking for _Bool... yes >> > checking size of _Bool... 1 >> > checking for uintptr_t... yes >> > checking for uintptr_t... (cached) yes >> > checking size of uintptr_t... 4 >> > checking size of off_t... 8 >> > checking whether to enable large file support... yes >> > checking size of time_t... 4 >> > checking for pthread_t... yes >> > checking size of pthread_t... 4 >> > checking for --enable-toolbox-glue... no >> > checking for --enable-framework... no >> > checking for dyld... no >> > checking SO... .so >> > checking LDSHARED... $(CC) -shared >> > checking CCSHARED... -fPIC >> > checking LINKFORSHARED... -Xlinker -export-dynamic >> > checking CFLAGSFORSHARED... >> > checking SHLIBS... $(LIBS) >> > checking for dlopen in -ldl... yes >> > checking for shl_load in -ldld... no >> > checking for library containing sem_init... -lpthread >> > checking for textdomain in -lintl... no >> > checking for t_open in -lnsl... no >> > checking for socket in -lsocket... no >> > checking for --with-libs... no >> > checking for --with-system-ffi... >> > checking for --with-signal-module... yes >> > checking for --with-dec-threads... no >> > checking for --with-threads... yes >> > checking if PTHREAD_SCOPE_SYSTEM is supported... yes >> > checking for pthread_sigmask... yes >> > checking if --enable-ipv6 is specified... yes >> > checking if RFC2553 API is available... yes >> > checking ipv6 stack type... linux-glibc >> > checking for OSX 10.5 SDK or later... no >> > checking for --with-doc-strings... yes >> > checking for --with-tsc... no >> > checking for --with-pymalloc... yes >> > checking for --with-wctype-functions... no >> > checking for dlopen... yes >> > checking DYNLOADFILE... dynload_shlib.o >> > checking MACHDEP_OBJS... MACHDEP_OBJS >> > checking for alarm... yes >> > checking for setitimer... yes >> > checking for getitimer... yes >> > checking for bind_textdomain_codeset... yes >> > checking for chown... yes >> > checking for clock... yes >> > checking for confstr... yes >> > checking for ctermid... yes >> > checking for execv... yes >> > checking for fchmod... yes >> > checking for fchown... yes >> > checking for fork... yes >> > checking for fpathconf... yes >> > checking for ftime... yes >> > checking for ftruncate... yes >> > checking for gai_strerror... yes >> > checking for getgroups... yes >> > checking for getlogin... yes >> > checking for getloadavg... yes >> > checking for getpeername... yes >> > checking for getpgid... yes >> > checking for getpid... yes >> > checking for getpriority... yes >> > checking for getpwent... yes >> > checking for getspnam... yes >> > checking for getspent... yes >> > checking for getsid... yes >> > checking for getwd... yes >> > checking for kill... yes >> > checking for killpg... yes >> > checking for lchmod... no >> > checking for lchown... yes >> > checking for lstat... yes >> > checking for mkfifo... yes >> > checking for mknod... yes >> > checking for mktime... yes >> > checking for mremap... yes >> > checking for nice... yes >> > checking for pathconf... yes >> > checking for pause... yes >> > checking for plock... no >> > checking for poll... yes >> > checking for pthread_init... no >> > checking for putenv... yes >> > checking for readlink... yes >> > checking for realpath... yes >> > checking for select... yes >> > checking for setegid... yes >> > checking for seteuid... yes >> > checking for setgid... yes >> > checking for setlocale... yes >> > checking for setregid... yes >> > checking for setreuid... yes >> > checking for setsid... yes >> > checking for setpgid... yes >> > checking for setpgrp... yes >> > checking for setuid... yes >> > checking for setvbuf... yes >> > checking for snprintf... yes >> > checking for sigaction... yes >> > checking for siginterrupt... yes >> > checking for sigrelse... yes >> > checking for strftime... yes >> > checking for sysconf... yes >> > checking for tcgetpgrp... yes >> > checking for tcsetpgrp... yes >> > checking for tempnam... yes >> > checking for timegm... yes >> > checking for times... yes >> > checking for tmpfile... yes >> > checking for tmpnam... yes >> > checking for tmpnam_r... yes >> > checking for truncate... yes >> > checking for uname... yes >> > checking for unsetenv... yes >> > checking for utimes... yes >> > checking for waitpid... yes >> > checking for wait3... yes >> > checking for wait4... yes >> > checking for wcscoll... yes >> > checking for _getpty... no >> > checking for chroot... yes >> > checking for link... yes >> > checking for symlink... yes >> > checking for fchdir... yes >> > checking for fsync... yes >> > checking for fdatasync... yes >> > checking for epoll... yes >> > checking for kqueue... no >> > checking for ctermid_r... no >> > checking for flock... yes >> > checking for getpagesize... yes >> > checking for true... true >> > checking for inet_aton in -lc... yes >> > checking for chflags... no >> > checking for lchflags... no >> > checking for inflateCopy in -lz... no >> > checking for hstrerror... yes >> > checking for inet_aton... yes >> > checking for inet_pton... yes >> > checking for setgroups... yes >> > checking for openpty... no >> > checking for openpty in -lutil... yes >> > checking for forkpty... yes >> > checking for memmove... yes >> > checking for fseek64... no >> > checking for fseeko... yes >> > checking for fstatvfs... yes >> > checking for ftell64... no >> > checking for ftello... yes >> > checking for statvfs... yes >> > checking for dup2... yes >> > checking for getcwd... yes >> > checking for strdup... yes >> > checking for getpgrp... yes >> > checking for setpgrp... (cached) yes >> > checking for gettimeofday... yes >> > checking for major... yes >> > checking for getaddrinfo... yes >> > checking getaddrinfo bug... good >> > checking for getnameinfo... yes >> > checking whether time.h and sys/time.h may both be included... yes >> > checking whether struct tm is in sys/time.h or time.h... time.h >> > checking for struct tm.tm_zone... yes >> > checking for struct stat.st_rdev... yes >> > checking for struct stat.st_blksize... yes >> > checking for struct stat.st_flags... no >> > checking for struct stat.st_gen... no >> > checking for struct stat.st_birthtime... no >> > checking for struct stat.st_blocks... yes >> > checking for time.h that defines altzone... no >> > checking whether sys/select.h and sys/time.h may both be included... >> yes >> > checking for addrinfo... yes >> > checking for sockaddr_storage... yes >> > checking whether char is unsigned... no >> > checking for an ANSI C-conforming const... yes >> > checking for working volatile... yes >> > checking for working signed char... yes >> > checking for prototypes... yes >> > checking for variable length prototypes and stdarg.h... yes >> > checking for socketpair... yes >> > checking if sockaddr has sa_len member... no >> > checking whether va_list is an array... no >> > checking for gethostbyname_r... yes >> > checking gethostbyname_r with 6 args... yes >> > checking for __fpu_control... yes >> > checking for --with-fpectl... no >> > checking for --with-libm=STRING... default LIBM="-lm" >> > checking for --with-libc=STRING... default LIBC="" >> > checking for x87-style double rounding... yes >> > checking whether tanh preserves the sign of zero... yes >> > checking for acosh... yes >> > checking for asinh... yes >> > checking for atanh... yes >> > checking for copysign... yes >> > checking for expm1... yes >> > checking for finite... yes >> > checking for hypot... yes >> > checking for log1p... yes >> > checking whether isinf is declared... yes >> > checking whether isnan is declared... yes >> > checking whether isfinite is declared... yes >> > checking wchar.h usability... yes >> > checking wchar.h presence... yes >> > checking for wchar.h... yes >> > checking for wchar_t... yes >> > checking size of wchar_t... 4 >> > checking for UCS-4 tcl... no >> > checking whether wchar_t is signed... yes >> > checking what type to use for unicode... unsigned short >> > checking whether byte ordering is bigendian... no >> > checking whether right shift extends the sign bit... yes >> > checking for getc_unlocked() and friends... yes >> > checking how to link readline libs... none >> > checking for rl_callback_handler_install in -lreadline... no >> > checking for rl_pre_input_hook in -lreadline... no >> > checking for rl_completion_display_matches_hook in -lreadline... no >> > checking for rl_completion_matches in -lreadline... no >> > checking for broken nice()... no >> > checking for broken poll()... no >> > checking for struct tm.tm_zone... (cached) yes >> > checking for working tzset()... yes >> > checking for tv_nsec in struct stat... yes >> > checking for tv_nsec2 in struct stat... no >> > checking whether mvwdelch is an expression... no >> > checking whether WINDOW has _flags... no >> > checking for is_term_resized... no >> > checking for resize_term... no >> > checking for resizeterm... no >> > checking for /dev/ptmx... yes >> > checking for /dev/ptc... no >> > checking for %zd printf() format support... yes >> > checking for socklen_t... yes >> > checking for build directories... done >> > configure: creating ./config.status >> > config.status: creating Makefile.pre >> > config.status: creating Modules/Setup.config >> > config.status: creating pyconfig.h >> > creating Modules/Setup >> > creating Modules/Setup.local >> > creating Makefile >> > >> > _______________________________________________ >> > Baypiggies mailing list >> > Baypiggies at python.org >> > To change your subscription options or unsubscribe: >> > http://mail.python.org/mailman/listinfo/baypiggies >> >> _______________________________________________ >> Baypiggies mailing list >> Baypiggies at python.org >> To change your subscription options or unsubscribe: >> http://mail.python.org/mailman/listinfo/baypiggies >> From andrew at atoulou.se Fri Apr 30 07:30:11 2010 From: andrew at atoulou.se (Andrew Toulouse) Date: Thu, 29 Apr 2010 22:30:11 -0700 Subject: [Baypiggies] Python 2.6 build on a Debian box; batteries not included?? In-Reply-To: References: <7AA7A787-E1F1-495A-B98F-CAEC1783801B@atoulou.se> <201004291150.30163.mvoorhie@yahoo.com> Message-ID: Your install of Debian is now very likely broken to some degree, as you have mixed repositories for lenny and squeeze. This is generally not a great idea; it's like trying to overwrite certain Windows Vista files with WIndows 7 versions - it might work for now, but it might explode in your face. If you want the packages from squeeze, you should fully upgrade your computer to squeeze, or find lenny backports. This doesn't seem to be terribly python-related, more debian-related, so I'd advise you to look for further help on a forum or IRC channel; there are many that can provide the kind of help you need (though no specific names come to mind). Hope that helped, Andy On Apr 29, 2010, at 10:12 PM, Tung Wai Yip wrote: > Thank you for all the information. I'm rather uninitiated with Debian. But I finally managed to get Python 2.6 setup with these steps: > > > 1. The python2.6 package is available in squeeze, the next release of Debian (I'm on lenny). It order to access it, backup and edit /etc/apt/sources.list. Add the last 2 lines. > > > # cat /etc/apt/sources.list > deb http://ftp.us.debian.org/debian lenny main contrib > deb http://security.debian.org/ lenny/updates main > deb-src http://ftp.us.debian.org/debian lenny main contrib > deb http://ftp.us.debian.org/debian squeeze main contrib > deb-src http://ftp.us.debian.org/debian squeeze main contrib > > > 2. Then run these as root > > # apt-get update > # apt-get build-dep python2.6 > # apt-get install python2.6 > # /usr/bin/python2.6 > > > Wai Yip > > > >> Debian is currently transitioning to python2.6 for their next release >> (squeeze), so you might try installing the current python2.6 package from >> testing: >> http://packages.debian.org/squeeze/python2.6 >> (it includes libbz2-1.0 as a dependency, so should provide zlib support) >> >> There has been a lot of discussion of updating Debian's python packages for >> 2.6 on the debian-python mailing list: >> http://lists.debian.org/debian-python/ >> >> --Mark >> >> On Wednesday 28 April 2010 10:47 pm Andrew Toulouse wrote: >>> Looks like you might not have some build dependencies. Have you tried >> running "apt-get build-dep python2.6"? As root (or with sudo), of course. >>> >>> --Andy >>> >>> >>> On Apr 28, 2010, at 10:36 PM, Tung Wai Yip wrote: >>> >>> > I'm using Python 2.6 that I downloaded and built on a Debian system. >> Things are >>> > working fine for me for a few weeks. Then I notice a problem when I failed >> to >>> > import zlib. >>> > >>> >>>> import zlib >>> > Traceback (most recent call last): >>> > File "", line 1, in >>> > ImportError: No module named zlib >>> > >>> > I'm so use to having all these Python modules included in the standard >> build I don't know what to do without them. I dig around more and find that >> they are suppose to be in a directory >>> > >>> > /usr/local/lib/python2.6/lib-dynload >>> > >>> > zlib.so is not in that directory. Not only is zlib.so missing, by >> comparing it with a equivalent directory from a Python 2.5 interpreter that >> comes with the system, I found that a number of modules are also missing. >>> > >>> > _hashlib.so >>> > _bsddb.so >>> > _curses.so >>> > _curses_panel.so >>> > _sqlite3.so >>> > _ssl.so >>> > bz2.so >>> > dbm.so >>> > readline.so >>> > rgbimg.so >>> > zlib.so >>> > >>> > >>> > Yes, even readline is missing! No wonder the interactive interpreter is >> acting weird. >>> > >>> > I think if I look at the output when I did ./configure I may find out some >> clue. Well it is several hundred lines long. Some line say yes and some line >> say no. So I can't really figure out what has went wrong. >>> > >>> > If anyone can give me more pointers it is greatly appreciated. >>> > >>> > Wai Yip >>> > >>> > >>> > >>> > tungwaiyip at tungwaiyip:~/download/Python-2.6.5$ cat >> 2010-04-27_configure.log >>> > checking for --enable-universalsdk... no >>> > checking for --with-universal-archs... 32-bit >>> > checking MACHDEP... linux2 >>> > checking EXTRAPLATDIR... >>> > checking machine type as reported by uname -m... i686 >>> > checking for --without-gcc... no >>> > checking for gcc... gcc >>> > checking for C compiler default output file name... a.out >>> > checking whether the C compiler works... yes >>> > checking whether we are cross compiling... no >>> > checking for suffix of executables... >>> > checking for suffix of object files... o >>> > checking whether we are using the GNU C compiler... yes >>> > checking whether gcc accepts -g... yes >>> > checking for gcc option to accept ISO C89... none needed >>> > checking for --with-cxx-main=... no >>> > checking for g++... g++ >>> > checking how to run the C preprocessor... gcc -E >>> > checking for grep that handles long lines and -e... /bin/grep >>> > checking for egrep... /bin/grep -E >>> > checking for AIX... no >>> > checking for --with-suffix... >>> > checking for case-insensitive build directory... no >>> > checking LIBRARY... libpython$(VERSION).a >>> > checking LINKCC... $(PURIFY) $(MAINCC) >>> > checking for --enable-shared... no >>> > checking for --enable-profiling... >>> > checking LDLIBRARY... libpython$(VERSION).a >>> > checking for ranlib... ranlib >>> > checking for ar... ar >>> > checking for svnversion... found >>> > checking for a BSD-compatible install... /usr/bin/install -c >>> > checking for --with-pydebug... no >>> > checking whether gcc accepts -fno-strict-aliasing... yes >>> > checking whether gcc accepts -OPT:Olimit=0... no >>> > checking whether gcc accepts -Olimit 1500... no >>> > checking whether gcc supports ParseTuple __format__... no >>> > checking whether pthreads are available without options... no >>> > checking whether gcc accepts -Kpthread... no >>> > checking whether gcc accepts -Kthread... no >>> > checking whether gcc accepts -pthread... yes >>> > checking whether g++ also accepts flags for thread support... yes >>> > checking for ANSI C header files... yes >>> > checking for sys/types.h... yes >>> > checking for sys/stat.h... yes >>> > checking for stdlib.h... yes >>> > checking for string.h... yes >>> > checking for memory.h... yes >>> > checking for strings.h... yes >>> > checking for inttypes.h... yes >>> > checking for stdint.h... yes >>> > checking for unistd.h... yes >>> > checking asm/types.h usability... yes >>> > checking asm/types.h presence... yes >>> > checking for asm/types.h... yes >>> > checking conio.h usability... no >>> > checking conio.h presence... no >>> > checking for conio.h... no >>> > checking curses.h usability... no >>> > checking curses.h presence... no >>> > checking for curses.h... no >>> > checking direct.h usability... no >>> > checking direct.h presence... no >>> > checking for direct.h... no >>> > checking dlfcn.h usability... yes >>> > checking dlfcn.h presence... yes >>> > checking for dlfcn.h... yes >>> > checking errno.h usability... yes >>> > checking errno.h presence... yes >>> > checking for errno.h... yes >>> > checking fcntl.h usability... yes >>> > checking fcntl.h presence... yes >>> > checking for fcntl.h... yes >>> > checking grp.h usability... yes >>> > checking grp.h presence... yes >>> > checking for grp.h... yes >>> > checking ieeefp.h usability... no >>> > checking ieeefp.h presence... no >>> > checking for ieeefp.h... no >>> > checking io.h usability... no >>> > checking io.h presence... no >>> > checking for io.h... no >>> > checking langinfo.h usability... yes >>> > checking langinfo.h presence... yes >>> > checking for langinfo.h... yes >>> > checking libintl.h usability... yes >>> > checking libintl.h presence... yes >>> > checking for libintl.h... yes >>> > checking ncurses.h usability... no >>> > checking ncurses.h presence... no >>> > checking for ncurses.h... no >>> > checking poll.h usability... yes >>> > checking poll.h presence... yes >>> > checking for poll.h... yes >>> > checking process.h usability... no >>> > checking process.h presence... no >>> > checking for process.h... no >>> > checking pthread.h usability... yes >>> > checking pthread.h presence... yes >>> > checking for pthread.h... yes >>> > checking shadow.h usability... yes >>> > checking shadow.h presence... yes >>> > checking for shadow.h... yes >>> > checking signal.h usability... yes >>> > checking signal.h presence... yes >>> > checking for signal.h... yes >>> > checking for stdint.h... (cached) yes >>> > checking stropts.h usability... yes >>> > checking stropts.h presence... yes >>> > checking for stropts.h... yes >>> > checking termios.h usability... yes >>> > checking termios.h presence... yes >>> > checking for termios.h... yes >>> > checking thread.h usability... no >>> > checking thread.h presence... no >>> > checking for thread.h... no >>> > checking for unistd.h... (cached) yes >>> > checking utime.h usability... yes >>> > checking utime.h presence... yes >>> > checking for utime.h... yes >>> > checking sys/audioio.h usability... no >>> > checking sys/audioio.h presence... no >>> > checking for sys/audioio.h... no >>> > checking sys/bsdtty.h usability... no >>> > checking sys/bsdtty.h presence... no >>> > checking for sys/bsdtty.h... no >>> > checking sys/epoll.h usability... yes >>> > checking sys/epoll.h presence... yes >>> > checking for sys/epoll.h... yes >>> > checking sys/event.h usability... no >>> > checking sys/event.h presence... no >>> > checking for sys/event.h... no >>> > checking sys/file.h usability... yes >>> > checking sys/file.h presence... yes >>> > checking for sys/file.h... yes >>> > checking sys/loadavg.h usability... no >>> > checking sys/loadavg.h presence... no >>> > checking for sys/loadavg.h... no >>> > checking sys/lock.h usability... no >>> > checking sys/lock.h presence... no >>> > checking for sys/lock.h... no >>> > checking sys/mkdev.h usability... no >>> > checking sys/mkdev.h presence... no >>> > checking for sys/mkdev.h... no >>> > checking sys/modem.h usability... no >>> > checking sys/modem.h presence... no >>> > checking for sys/modem.h... no >>> > checking sys/param.h usability... yes >>> > checking sys/param.h presence... yes >>> > checking for sys/param.h... yes >>> > checking sys/poll.h usability... yes >>> > checking sys/poll.h presence... yes >>> > checking for sys/poll.h... yes >>> > checking sys/select.h usability... yes >>> > checking sys/select.h presence... yes >>> > checking for sys/select.h... yes >>> > checking sys/socket.h usability... yes >>> > checking sys/socket.h presence... yes >>> > checking for sys/socket.h... yes >>> > checking sys/statvfs.h usability... yes >>> > checking sys/statvfs.h presence... yes >>> > checking for sys/statvfs.h... yes >>> > checking for sys/stat.h... (cached) yes >>> > checking sys/termio.h usability... no >>> > checking sys/termio.h presence... no >>> > checking for sys/termio.h... no >>> > checking sys/time.h usability... yes >>> > checking sys/time.h presence... yes >>> > checking for sys/time.h... yes >>> > checking sys/times.h usability... yes >>> > checking sys/times.h presence... yes >>> > checking for sys/times.h... yes >>> > checking for sys/types.h... (cached) yes >>> > checking sys/un.h usability... yes >>> > checking sys/un.h presence... yes >>> > checking for sys/un.h... yes >>> > checking sys/utsname.h usability... yes >>> > checking sys/utsname.h presence... yes >>> > checking for sys/utsname.h... yes >>> > checking sys/wait.h usability... yes >>> > checking sys/wait.h presence... yes >>> > checking for sys/wait.h... yes >>> > checking pty.h usability... yes >>> > checking pty.h presence... yes >>> > checking for pty.h... yes >>> > checking libutil.h usability... no >>> > checking libutil.h presence... no >>> > checking for libutil.h... no >>> > checking sys/resource.h usability... yes >>> > checking sys/resource.h presence... yes >>> > checking for sys/resource.h... yes >>> > checking netpacket/packet.h usability... yes >>> > checking netpacket/packet.h presence... yes >>> > checking for netpacket/packet.h... yes >>> > checking sysexits.h usability... yes >>> > checking sysexits.h presence... yes >>> > checking for sysexits.h... yes >>> > checking bluetooth.h usability... no >>> > checking bluetooth.h presence... no >>> > checking for bluetooth.h... no >>> > checking bluetooth/bluetooth.h usability... no >>> > checking bluetooth/bluetooth.h presence... no >>> > checking for bluetooth/bluetooth.h... no >>> > checking linux/tipc.h usability... yes >>> > checking linux/tipc.h presence... yes >>> > checking for linux/tipc.h... yes >>> > checking for dirent.h that defines DIR... yes >>> > checking for library containing opendir... none required >>> > checking whether sys/types.h defines makedev... yes >>> > checking for term.h... no >>> > checking for linux/netlink.h... yes >>> > checking for clock_t in time.h... yes >>> > checking for makedev... yes >>> > checking Solaris LFS bug... no >>> > checking for mode_t... yes >>> > checking for off_t... yes >>> > checking for pid_t... yes >>> > checking return type of signal handlers... void >>> > checking for size_t... yes >>> > checking for uid_t in sys/types.h... yes >>> > checking for ssize_t... yes >>> > checking for int... yes >>> > checking size of int... 4 >>> > checking for long... yes >>> > checking size of long... 4 >>> > checking for void *... yes >>> > checking size of void *... 4 >>> > checking for short... yes >>> > checking size of short... 2 >>> > checking for float... yes >>> > checking size of float... 4 >>> > checking for double... yes >>> > checking size of double... 8 >>> > checking for fpos_t... yes >>> > checking size of fpos_t... 16 >>> > checking for size_t... (cached) yes >>> > checking size of size_t... 4 >>> > checking for pid_t... (cached) yes >>> > checking size of pid_t... 4 >>> > checking for long long support... yes >>> > checking for long long... yes >>> > checking size of long long... 8 >>> > checking for long double support... yes >>> > checking for long double... yes >>> > checking size of long double... 12 >>> > checking for _Bool support... yes >>> > checking for _Bool... yes >>> > checking size of _Bool... 1 >>> > checking for uintptr_t... yes >>> > checking for uintptr_t... (cached) yes >>> > checking size of uintptr_t... 4 >>> > checking size of off_t... 8 >>> > checking whether to enable large file support... yes >>> > checking size of time_t... 4 >>> > checking for pthread_t... yes >>> > checking size of pthread_t... 4 >>> > checking for --enable-toolbox-glue... no >>> > checking for --enable-framework... no >>> > checking for dyld... no >>> > checking SO... .so >>> > checking LDSHARED... $(CC) -shared >>> > checking CCSHARED... -fPIC >>> > checking LINKFORSHARED... -Xlinker -export-dynamic >>> > checking CFLAGSFORSHARED... >>> > checking SHLIBS... $(LIBS) >>> > checking for dlopen in -ldl... yes >>> > checking for shl_load in -ldld... no >>> > checking for library containing sem_init... -lpthread >>> > checking for textdomain in -lintl... no >>> > checking for t_open in -lnsl... no >>> > checking for socket in -lsocket... no >>> > checking for --with-libs... no >>> > checking for --with-system-ffi... >>> > checking for --with-signal-module... yes >>> > checking for --with-dec-threads... no >>> > checking for --with-threads... yes >>> > checking if PTHREAD_SCOPE_SYSTEM is supported... yes >>> > checking for pthread_sigmask... yes >>> > checking if --enable-ipv6 is specified... yes >>> > checking if RFC2553 API is available... yes >>> > checking ipv6 stack type... linux-glibc >>> > checking for OSX 10.5 SDK or later... no >>> > checking for --with-doc-strings... yes >>> > checking for --with-tsc... no >>> > checking for --with-pymalloc... yes >>> > checking for --with-wctype-functions... no >>> > checking for dlopen... yes >>> > checking DYNLOADFILE... dynload_shlib.o >>> > checking MACHDEP_OBJS... MACHDEP_OBJS >>> > checking for alarm... yes >>> > checking for setitimer... yes >>> > checking for getitimer... yes >>> > checking for bind_textdomain_codeset... yes >>> > checking for chown... yes >>> > checking for clock... yes >>> > checking for confstr... yes >>> > checking for ctermid... yes >>> > checking for execv... yes >>> > checking for fchmod... yes >>> > checking for fchown... yes >>> > checking for fork... yes >>> > checking for fpathconf... yes >>> > checking for ftime... yes >>> > checking for ftruncate... yes >>> > checking for gai_strerror... yes >>> > checking for getgroups... yes >>> > checking for getlogin... yes >>> > checking for getloadavg... yes >>> > checking for getpeername... yes >>> > checking for getpgid... yes >>> > checking for getpid... yes >>> > checking for getpriority... yes >>> > checking for getpwent... yes >>> > checking for getspnam... yes >>> > checking for getspent... yes >>> > checking for getsid... yes >>> > checking for getwd... yes >>> > checking for kill... yes >>> > checking for killpg... yes >>> > checking for lchmod... no >>> > checking for lchown... yes >>> > checking for lstat... yes >>> > checking for mkfifo... yes >>> > checking for mknod... yes >>> > checking for mktime... yes >>> > checking for mremap... yes >>> > checking for nice... yes >>> > checking for pathconf... yes >>> > checking for pause... yes >>> > checking for plock... no >>> > checking for poll... yes >>> > checking for pthread_init... no >>> > checking for putenv... yes >>> > checking for readlink... yes >>> > checking for realpath... yes >>> > checking for select... yes >>> > checking for setegid... yes >>> > checking for seteuid... yes >>> > checking for setgid... yes >>> > checking for setlocale... yes >>> > checking for setregid... yes >>> > checking for setreuid... yes >>> > checking for setsid... yes >>> > checking for setpgid... yes >>> > checking for setpgrp... yes >>> > checking for setuid... yes >>> > checking for setvbuf... yes >>> > checking for snprintf... yes >>> > checking for sigaction... yes >>> > checking for siginterrupt... yes >>> > checking for sigrelse... yes >>> > checking for strftime... yes >>> > checking for sysconf... yes >>> > checking for tcgetpgrp... yes >>> > checking for tcsetpgrp... yes >>> > checking for tempnam... yes >>> > checking for timegm... yes >>> > checking for times... yes >>> > checking for tmpfile... yes >>> > checking for tmpnam... yes >>> > checking for tmpnam_r... yes >>> > checking for truncate... yes >>> > checking for uname... yes >>> > checking for unsetenv... yes >>> > checking for utimes... yes >>> > checking for waitpid... yes >>> > checking for wait3... yes >>> > checking for wait4... yes >>> > checking for wcscoll... yes >>> > checking for _getpty... no >>> > checking for chroot... yes >>> > checking for link... yes >>> > checking for symlink... yes >>> > checking for fchdir... yes >>> > checking for fsync... yes >>> > checking for fdatasync... yes >>> > checking for epoll... yes >>> > checking for kqueue... no >>> > checking for ctermid_r... no >>> > checking for flock... yes >>> > checking for getpagesize... yes >>> > checking for true... true >>> > checking for inet_aton in -lc... yes >>> > checking for chflags... no >>> > checking for lchflags... no >>> > checking for inflateCopy in -lz... no >>> > checking for hstrerror... yes >>> > checking for inet_aton... yes >>> > checking for inet_pton... yes >>> > checking for setgroups... yes >>> > checking for openpty... no >>> > checking for openpty in -lutil... yes >>> > checking for forkpty... yes >>> > checking for memmove... yes >>> > checking for fseek64... no >>> > checking for fseeko... yes >>> > checking for fstatvfs... yes >>> > checking for ftell64... no >>> > checking for ftello... yes >>> > checking for statvfs... yes >>> > checking for dup2... yes >>> > checking for getcwd... yes >>> > checking for strdup... yes >>> > checking for getpgrp... yes >>> > checking for setpgrp... (cached) yes >>> > checking for gettimeofday... yes >>> > checking for major... yes >>> > checking for getaddrinfo... yes >>> > checking getaddrinfo bug... good >>> > checking for getnameinfo... yes >>> > checking whether time.h and sys/time.h may both be included... yes >>> > checking whether struct tm is in sys/time.h or time.h... time.h >>> > checking for struct tm.tm_zone... yes >>> > checking for struct stat.st_rdev... yes >>> > checking for struct stat.st_blksize... yes >>> > checking for struct stat.st_flags... no >>> > checking for struct stat.st_gen... no >>> > checking for struct stat.st_birthtime... no >>> > checking for struct stat.st_blocks... yes >>> > checking for time.h that defines altzone... no >>> > checking whether sys/select.h and sys/time.h may both be included... yes >>> > checking for addrinfo... yes >>> > checking for sockaddr_storage... yes >>> > checking whether char is unsigned... no >>> > checking for an ANSI C-conforming const... yes >>> > checking for working volatile... yes >>> > checking for working signed char... yes >>> > checking for prototypes... yes >>> > checking for variable length prototypes and stdarg.h... yes >>> > checking for socketpair... yes >>> > checking if sockaddr has sa_len member... no >>> > checking whether va_list is an array... no >>> > checking for gethostbyname_r... yes >>> > checking gethostbyname_r with 6 args... yes >>> > checking for __fpu_control... yes >>> > checking for --with-fpectl... no >>> > checking for --with-libm=STRING... default LIBM="-lm" >>> > checking for --with-libc=STRING... default LIBC="" >>> > checking for x87-style double rounding... yes >>> > checking whether tanh preserves the sign of zero... yes >>> > checking for acosh... yes >>> > checking for asinh... yes >>> > checking for atanh... yes >>> > checking for copysign... yes >>> > checking for expm1... yes >>> > checking for finite... yes >>> > checking for hypot... yes >>> > checking for log1p... yes >>> > checking whether isinf is declared... yes >>> > checking whether isnan is declared... yes >>> > checking whether isfinite is declared... yes >>> > checking wchar.h usability... yes >>> > checking wchar.h presence... yes >>> > checking for wchar.h... yes >>> > checking for wchar_t... yes >>> > checking size of wchar_t... 4 >>> > checking for UCS-4 tcl... no >>> > checking whether wchar_t is signed... yes >>> > checking what type to use for unicode... unsigned short >>> > checking whether byte ordering is bigendian... no >>> > checking whether right shift extends the sign bit... yes >>> > checking for getc_unlocked() and friends... yes >>> > checking how to link readline libs... none >>> > checking for rl_callback_handler_install in -lreadline... no >>> > checking for rl_pre_input_hook in -lreadline... no >>> > checking for rl_completion_display_matches_hook in -lreadline... no >>> > checking for rl_completion_matches in -lreadline... no >>> > checking for broken nice()... no >>> > checking for broken poll()... no >>> > checking for struct tm.tm_zone... (cached) yes >>> > checking for working tzset()... yes >>> > checking for tv_nsec in struct stat... yes >>> > checking for tv_nsec2 in struct stat... no >>> > checking whether mvwdelch is an expression... no >>> > checking whether WINDOW has _flags... no >>> > checking for is_term_resized... no >>> > checking for resize_term... no >>> > checking for resizeterm... no >>> > checking for /dev/ptmx... yes >>> > checking for /dev/ptc... no >>> > checking for %zd printf() format support... yes >>> > checking for socklen_t... yes >>> > checking for build directories... done >>> > configure: creating ./config.status >>> > config.status: creating Makefile.pre >>> > config.status: creating Modules/Setup.config >>> > config.status: creating pyconfig.h >>> > creating Modules/Setup >>> > creating Modules/Setup.local >>> > creating Makefile >>> > >>> > _______________________________________________ >>> > Baypiggies mailing list >>> > Baypiggies at python.org >>> > To change your subscription options or unsubscribe: >>> > http://mail.python.org/mailman/listinfo/baypiggies >>> >>> _______________________________________________ >>> Baypiggies mailing list >>> Baypiggies at python.org >>> To change your subscription options or unsubscribe: >>> http://mail.python.org/mailman/listinfo/baypiggies >>> > > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > http://mail.python.org/mailman/listinfo/baypiggies From tungwaiyip at yahoo.com Fri Apr 30 17:24:25 2010 From: tungwaiyip at yahoo.com (Tung Wai Yip) Date: Fri, 30 Apr 2010 08:24:25 -0700 Subject: [Baypiggies] Python 2.6 build on a Debian box; batteries not included?? In-Reply-To: References: <7AA7A787-E1F1-495A-B98F-CAEC1783801B@atoulou.se> <201004291150.30163.mvoorhie@yahoo.com> Message-ID: Oops. It has not blow up yet. I guess I have to put "reinstall the OS" as another item on my task list :-O Wai Yip > Your install of Debian is now very likely broken to some degree, as you > have mixed repositories for lenny and squeeze. This is generally not a > great idea; it's like trying to overwrite certain Windows Vista files > with WIndows 7 versions - it might work for now, but it might explode in > your face. > > If you want the packages from squeeze, you should fully upgrade your > computer to squeeze, or find lenny backports. > > This doesn't seem to be terribly python-related, more debian-related, so > I'd advise you to look for further help on a forum or IRC channel; there > are many that can provide the kind of help you need (though no specific > names come to mind). > > Hope that helped, > Andy > > On Apr 29, 2010, at 10:12 PM, Tung Wai Yip wrote: > >> Thank you for all the information. I'm rather uninitiated with Debian. >> But I finally managed to get Python 2.6 setup with these steps: >> >> >> 1. The python2.6 package is available in squeeze, the next release of >> Debian (I'm on lenny). It order to access it, backup and edit >> /etc/apt/sources.list. Add the last 2 lines. >> >> >> # cat /etc/apt/sources.list >> deb http://ftp.us.debian.org/debian lenny main contrib >> deb http://security.debian.org/ lenny/updates main >> deb-src http://ftp.us.debian.org/debian lenny main contrib >> deb http://ftp.us.debian.org/debian squeeze main contrib >> deb-src http://ftp.us.debian.org/debian squeeze main contrib >> >> >> 2. Then run these as root >> >> # apt-get update >> # apt-get build-dep python2.6 >> # apt-get install python2.6 >> # /usr/bin/python2.6 >> >> >> Wai Yip >> >> >> >>> Debian is currently transitioning to python2.6 for their next release >>> (squeeze), so you might try installing the current python2.6 package >>> from >>> testing: >>> http://packages.debian.org/squeeze/python2.6 >>> (it includes libbz2-1.0 as a dependency, so should provide zlib >>> support) >>> >>> There has been a lot of discussion of updating Debian's python >>> packages for >>> 2.6 on the debian-python mailing list: >>> http://lists.debian.org/debian-python/ >>> >>> --Mark >>> >>> On Wednesday 28 April 2010 10:47 pm Andrew Toulouse wrote: >>>> Looks like you might not have some build dependencies. Have you tried >>> running "apt-get build-dep python2.6"? As root (or with sudo), of >>> course. >>>> >>>> --Andy >>>> >>>> >>>> On Apr 28, 2010, at 10:36 PM, Tung Wai Yip wrote: >>>> >>>> > I'm using Python 2.6 that I downloaded and built on a Debian system. >>> Things are >>>> > working fine for me for a few weeks. Then I notice a problem when I >>>> failed >>> to >>>> > import zlib. >>>> > >>>> >>>> import zlib >>>> > Traceback (most recent call last): >>>> > File "", line 1, in >>>> > ImportError: No module named zlib >>>> > >>>> > I'm so use to having all these Python modules included in the >>>> standard >>> build I don't know what to do without them. I dig around more and find >>> that >>> they are suppose to be in a directory >>>> > >>>> > /usr/local/lib/python2.6/lib-dynload >>>> > >>>> > zlib.so is not in that directory. Not only is zlib.so missing, by >>> comparing it with a equivalent directory from a Python 2.5 interpreter >>> that >>> comes with the system, I found that a number of modules are also >>> missing. >>>> > >>>> > _hashlib.so >>>> > _bsddb.so >>>> > _curses.so >>>> > _curses_panel.so >>>> > _sqlite3.so >>>> > _ssl.so >>>> > bz2.so >>>> > dbm.so >>>> > readline.so >>>> > rgbimg.so >>>> > zlib.so >>>> > >>>> > >>>> > Yes, even readline is missing! No wonder the interactive >>>> interpreter is >>> acting weird. >>>> > >>>> > I think if I look at the output when I did ./configure I may find >>>> out some >>> clue. Well it is several hundred lines long. Some line say yes and >>> some line >>> say no. So I can't really figure out what has went wrong. >>>> > >>>> > If anyone can give me more pointers it is greatly appreciated. >>>> > >>>> > Wai Yip >>>> > >>>> > >>>> > >>>> > tungwaiyip at tungwaiyip:~/download/Python-2.6.5$ cat >>> 2010-04-27_configure.log >>>> > checking for --enable-universalsdk... no >>>> > checking for --with-universal-archs... 32-bit >>>> > checking MACHDEP... linux2 >>>> > checking EXTRAPLATDIR... >>>> > checking machine type as reported by uname -m... i686 >>>> > checking for --without-gcc... no >>>> > checking for gcc... gcc >>>> > checking for C compiler default output file name... a.out >>>> > checking whether the C compiler works... yes >>>> > checking whether we are cross compiling... no >>>> > checking for suffix of executables... >>>> > checking for suffix of object files... o >>>> > checking whether we are using the GNU C compiler... yes >>>> > checking whether gcc accepts -g... yes >>>> > checking for gcc option to accept ISO C89... none needed >>>> > checking for --with-cxx-main=... no >>>> > checking for g++... g++ >>>> > checking how to run the C preprocessor... gcc -E >>>> > checking for grep that handles long lines and -e... /bin/grep >>>> > checking for egrep... /bin/grep -E >>>> > checking for AIX... no >>>> > checking for --with-suffix... >>>> > checking for case-insensitive build directory... no >>>> > checking LIBRARY... libpython$(VERSION).a >>>> > checking LINKCC... $(PURIFY) $(MAINCC) >>>> > checking for --enable-shared... no >>>> > checking for --enable-profiling... >>>> > checking LDLIBRARY... libpython$(VERSION).a >>>> > checking for ranlib... ranlib >>>> > checking for ar... ar >>>> > checking for svnversion... found >>>> > checking for a BSD-compatible install... /usr/bin/install -c >>>> > checking for --with-pydebug... no >>>> > checking whether gcc accepts -fno-strict-aliasing... yes >>>> > checking whether gcc accepts -OPT:Olimit=0... no >>>> > checking whether gcc accepts -Olimit 1500... no >>>> > checking whether gcc supports ParseTuple __format__... no >>>> > checking whether pthreads are available without options... no >>>> > checking whether gcc accepts -Kpthread... no >>>> > checking whether gcc accepts -Kthread... no >>>> > checking whether gcc accepts -pthread... yes >>>> > checking whether g++ also accepts flags for thread support... yes >>>> > checking for ANSI C header files... yes >>>> > checking for sys/types.h... yes >>>> > checking for sys/stat.h... yes >>>> > checking for stdlib.h... yes >>>> > checking for string.h... yes >>>> > checking for memory.h... yes >>>> > checking for strings.h... yes >>>> > checking for inttypes.h... yes >>>> > checking for stdint.h... yes >>>> > checking for unistd.h... yes >>>> > checking asm/types.h usability... yes >>>> > checking asm/types.h presence... yes >>>> > checking for asm/types.h... yes >>>> > checking conio.h usability... no >>>> > checking conio.h presence... no >>>> > checking for conio.h... no >>>> > checking curses.h usability... no >>>> > checking curses.h presence... no >>>> > checking for curses.h... no >>>> > checking direct.h usability... no >>>> > checking direct.h presence... no >>>> > checking for direct.h... no >>>> > checking dlfcn.h usability... yes >>>> > checking dlfcn.h presence... yes >>>> > checking for dlfcn.h... yes >>>> > checking errno.h usability... yes >>>> > checking errno.h presence... yes >>>> > checking for errno.h... yes >>>> > checking fcntl.h usability... yes >>>> > checking fcntl.h presence... yes >>>> > checking for fcntl.h... yes >>>> > checking grp.h usability... yes >>>> > checking grp.h presence... yes >>>> > checking for grp.h... yes >>>> > checking ieeefp.h usability... no >>>> > checking ieeefp.h presence... no >>>> > checking for ieeefp.h... no >>>> > checking io.h usability... no >>>> > checking io.h presence... no >>>> > checking for io.h... no >>>> > checking langinfo.h usability... yes >>>> > checking langinfo.h presence... yes >>>> > checking for langinfo.h... yes >>>> > checking libintl.h usability... yes >>>> > checking libintl.h presence... yes >>>> > checking for libintl.h... yes >>>> > checking ncurses.h usability... no >>>> > checking ncurses.h presence... no >>>> > checking for ncurses.h... no >>>> > checking poll.h usability... yes >>>> > checking poll.h presence... yes >>>> > checking for poll.h... yes >>>> > checking process.h usability... no >>>> > checking process.h presence... no >>>> > checking for process.h... no >>>> > checking pthread.h usability... yes >>>> > checking pthread.h presence... yes >>>> > checking for pthread.h... yes >>>> > checking shadow.h usability... yes >>>> > checking shadow.h presence... yes >>>> > checking for shadow.h... yes >>>> > checking signal.h usability... yes >>>> > checking signal.h presence... yes >>>> > checking for signal.h... yes >>>> > checking for stdint.h... (cached) yes >>>> > checking stropts.h usability... yes >>>> > checking stropts.h presence... yes >>>> > checking for stropts.h... yes >>>> > checking termios.h usability... yes >>>> > checking termios.h presence... yes >>>> > checking for termios.h... yes >>>> > checking thread.h usability... no >>>> > checking thread.h presence... no >>>> > checking for thread.h... no >>>> > checking for unistd.h... (cached) yes >>>> > checking utime.h usability... yes >>>> > checking utime.h presence... yes >>>> > checking for utime.h... yes >>>> > checking sys/audioio.h usability... no >>>> > checking sys/audioio.h presence... no >>>> > checking for sys/audioio.h... no >>>> > checking sys/bsdtty.h usability... no >>>> > checking sys/bsdtty.h presence... no >>>> > checking for sys/bsdtty.h... no >>>> > checking sys/epoll.h usability... yes >>>> > checking sys/epoll.h presence... yes >>>> > checking for sys/epoll.h... yes >>>> > checking sys/event.h usability... no >>>> > checking sys/event.h presence... no >>>> > checking for sys/event.h... no >>>> > checking sys/file.h usability... yes >>>> > checking sys/file.h presence... yes >>>> > checking for sys/file.h... yes >>>> > checking sys/loadavg.h usability... no >>>> > checking sys/loadavg.h presence... no >>>> > checking for sys/loadavg.h... no >>>> > checking sys/lock.h usability... no >>>> > checking sys/lock.h presence... no >>>> > checking for sys/lock.h... no >>>> > checking sys/mkdev.h usability... no >>>> > checking sys/mkdev.h presence... no >>>> > checking for sys/mkdev.h... no >>>> > checking sys/modem.h usability... no >>>> > checking sys/modem.h presence... no >>>> > checking for sys/modem.h... no >>>> > checking sys/param.h usability... yes >>>> > checking sys/param.h presence... yes >>>> > checking for sys/param.h... yes >>>> > checking sys/poll.h usability... yes >>>> > checking sys/poll.h presence... yes >>>> > checking for sys/poll.h... yes >>>> > checking sys/select.h usability... yes >>>> > checking sys/select.h presence... yes >>>> > checking for sys/select.h... yes >>>> > checking sys/socket.h usability... yes >>>> > checking sys/socket.h presence... yes >>>> > checking for sys/socket.h... yes >>>> > checking sys/statvfs.h usability... yes >>>> > checking sys/statvfs.h presence... yes >>>> > checking for sys/statvfs.h... yes >>>> > checking for sys/stat.h... (cached) yes >>>> > checking sys/termio.h usability... no >>>> > checking sys/termio.h presence... no >>>> > checking for sys/termio.h... no >>>> > checking sys/time.h usability... yes >>>> > checking sys/time.h presence... yes >>>> > checking for sys/time.h... yes >>>> > checking sys/times.h usability... yes >>>> > checking sys/times.h presence... yes >>>> > checking for sys/times.h... yes >>>> > checking for sys/types.h... (cached) yes >>>> > checking sys/un.h usability... yes >>>> > checking sys/un.h presence... yes >>>> > checking for sys/un.h... yes >>>> > checking sys/utsname.h usability... yes >>>> > checking sys/utsname.h presence... yes >>>> > checking for sys/utsname.h... yes >>>> > checking sys/wait.h usability... yes >>>> > checking sys/wait.h presence... yes >>>> > checking for sys/wait.h... yes >>>> > checking pty.h usability... yes >>>> > checking pty.h presence... yes >>>> > checking for pty.h... yes >>>> > checking libutil.h usability... no >>>> > checking libutil.h presence... no >>>> > checking for libutil.h... no >>>> > checking sys/resource.h usability... yes >>>> > checking sys/resource.h presence... yes >>>> > checking for sys/resource.h... yes >>>> > checking netpacket/packet.h usability... yes >>>> > checking netpacket/packet.h presence... yes >>>> > checking for netpacket/packet.h... yes >>>> > checking sysexits.h usability... yes >>>> > checking sysexits.h presence... yes >>>> > checking for sysexits.h... yes >>>> > checking bluetooth.h usability... no >>>> > checking bluetooth.h presence... no >>>> > checking for bluetooth.h... no >>>> > checking bluetooth/bluetooth.h usability... no >>>> > checking bluetooth/bluetooth.h presence... no >>>> > checking for bluetooth/bluetooth.h... no >>>> > checking linux/tipc.h usability... yes >>>> > checking linux/tipc.h presence... yes >>>> > checking for linux/tipc.h... yes >>>> > checking for dirent.h that defines DIR... yes >>>> > checking for library containing opendir... none required >>>> > checking whether sys/types.h defines makedev... yes >>>> > checking for term.h... no >>>> > checking for linux/netlink.h... yes >>>> > checking for clock_t in time.h... yes >>>> > checking for makedev... yes >>>> > checking Solaris LFS bug... no >>>> > checking for mode_t... yes >>>> > checking for off_t... yes >>>> > checking for pid_t... yes >>>> > checking return type of signal handlers... void >>>> > checking for size_t... yes >>>> > checking for uid_t in sys/types.h... yes >>>> > checking for ssize_t... yes >>>> > checking for int... yes >>>> > checking size of int... 4 >>>> > checking for long... yes >>>> > checking size of long... 4 >>>> > checking for void *... yes >>>> > checking size of void *... 4 >>>> > checking for short... yes >>>> > checking size of short... 2 >>>> > checking for float... yes >>>> > checking size of float... 4 >>>> > checking for double... yes >>>> > checking size of double... 8 >>>> > checking for fpos_t... yes >>>> > checking size of fpos_t... 16 >>>> > checking for size_t... (cached) yes >>>> > checking size of size_t... 4 >>>> > checking for pid_t... (cached) yes >>>> > checking size of pid_t... 4 >>>> > checking for long long support... yes >>>> > checking for long long... yes >>>> > checking size of long long... 8 >>>> > checking for long double support... yes >>>> > checking for long double... yes >>>> > checking size of long double... 12 >>>> > checking for _Bool support... yes >>>> > checking for _Bool... yes >>>> > checking size of _Bool... 1 >>>> > checking for uintptr_t... yes >>>> > checking for uintptr_t... (cached) yes >>>> > checking size of uintptr_t... 4 >>>> > checking size of off_t... 8 >>>> > checking whether to enable large file support... yes >>>> > checking size of time_t... 4 >>>> > checking for pthread_t... yes >>>> > checking size of pthread_t... 4 >>>> > checking for --enable-toolbox-glue... no >>>> > checking for --enable-framework... no >>>> > checking for dyld... no >>>> > checking SO... .so >>>> > checking LDSHARED... $(CC) -shared >>>> > checking CCSHARED... -fPIC >>>> > checking LINKFORSHARED... -Xlinker -export-dynamic >>>> > checking CFLAGSFORSHARED... >>>> > checking SHLIBS... $(LIBS) >>>> > checking for dlopen in -ldl... yes >>>> > checking for shl_load in -ldld... no >>>> > checking for library containing sem_init... -lpthread >>>> > checking for textdomain in -lintl... no >>>> > checking for t_open in -lnsl... no >>>> > checking for socket in -lsocket... no >>>> > checking for --with-libs... no >>>> > checking for --with-system-ffi... >>>> > checking for --with-signal-module... yes >>>> > checking for --with-dec-threads... no >>>> > checking for --with-threads... yes >>>> > checking if PTHREAD_SCOPE_SYSTEM is supported... yes >>>> > checking for pthread_sigmask... yes >>>> > checking if --enable-ipv6 is specified... yes >>>> > checking if RFC2553 API is available... yes >>>> > checking ipv6 stack type... linux-glibc >>>> > checking for OSX 10.5 SDK or later... no >>>> > checking for --with-doc-strings... yes >>>> > checking for --with-tsc... no >>>> > checking for --with-pymalloc... yes >>>> > checking for --with-wctype-functions... no >>>> > checking for dlopen... yes >>>> > checking DYNLOADFILE... dynload_shlib.o >>>> > checking MACHDEP_OBJS... MACHDEP_OBJS >>>> > checking for alarm... yes >>>> > checking for setitimer... yes >>>> > checking for getitimer... yes >>>> > checking for bind_textdomain_codeset... yes >>>> > checking for chown... yes >>>> > checking for clock... yes >>>> > checking for confstr... yes >>>> > checking for ctermid... yes >>>> > checking for execv... yes >>>> > checking for fchmod... yes >>>> > checking for fchown... yes >>>> > checking for fork... yes >>>> > checking for fpathconf... yes >>>> > checking for ftime... yes >>>> > checking for ftruncate... yes >>>> > checking for gai_strerror... yes >>>> > checking for getgroups... yes >>>> > checking for getlogin... yes >>>> > checking for getloadavg... yes >>>> > checking for getpeername... yes >>>> > checking for getpgid... yes >>>> > checking for getpid... yes >>>> > checking for getpriority... yes >>>> > checking for getpwent... yes >>>> > checking for getspnam... yes >>>> > checking for getspent... yes >>>> > checking for getsid... yes >>>> > checking for getwd... yes >>>> > checking for kill... yes >>>> > checking for killpg... yes >>>> > checking for lchmod... no >>>> > checking for lchown... yes >>>> > checking for lstat... yes >>>> > checking for mkfifo... yes >>>> > checking for mknod... yes >>>> > checking for mktime... yes >>>> > checking for mremap... yes >>>> > checking for nice... yes >>>> > checking for pathconf... yes >>>> > checking for pause... yes >>>> > checking for plock... no >>>> > checking for poll... yes >>>> > checking for pthread_init... no >>>> > checking for putenv... yes >>>> > checking for readlink... yes >>>> > checking for realpath... yes >>>> > checking for select... yes >>>> > checking for setegid... yes >>>> > checking for seteuid... yes >>>> > checking for setgid... yes >>>> > checking for setlocale... yes >>>> > checking for setregid... yes >>>> > checking for setreuid... yes >>>> > checking for setsid... yes >>>> > checking for setpgid... yes >>>> > checking for setpgrp... yes >>>> > checking for setuid... yes >>>> > checking for setvbuf... yes >>>> > checking for snprintf... yes >>>> > checking for sigaction... yes >>>> > checking for siginterrupt... yes >>>> > checking for sigrelse... yes >>>> > checking for strftime... yes >>>> > checking for sysconf... yes >>>> > checking for tcgetpgrp... yes >>>> > checking for tcsetpgrp... yes >>>> > checking for tempnam... yes >>>> > checking for timegm... yes >>>> > checking for times... yes >>>> > checking for tmpfile... yes >>>> > checking for tmpnam... yes >>>> > checking for tmpnam_r... yes >>>> > checking for truncate... yes >>>> > checking for uname... yes >>>> > checking for unsetenv... yes >>>> > checking for utimes... yes >>>> > checking for waitpid... yes >>>> > checking for wait3... yes >>>> > checking for wait4... yes >>>> > checking for wcscoll... yes >>>> > checking for _getpty... no >>>> > checking for chroot... yes >>>> > checking for link... yes >>>> > checking for symlink... yes >>>> > checking for fchdir... yes >>>> > checking for fsync... yes >>>> > checking for fdatasync... yes >>>> > checking for epoll... yes >>>> > checking for kqueue... no >>>> > checking for ctermid_r... no >>>> > checking for flock... yes >>>> > checking for getpagesize... yes >>>> > checking for true... true >>>> > checking for inet_aton in -lc... yes >>>> > checking for chflags... no >>>> > checking for lchflags... no >>>> > checking for inflateCopy in -lz... no >>>> > checking for hstrerror... yes >>>> > checking for inet_aton... yes >>>> > checking for inet_pton... yes >>>> > checking for setgroups... yes >>>> > checking for openpty... no >>>> > checking for openpty in -lutil... yes >>>> > checking for forkpty... yes >>>> > checking for memmove... yes >>>> > checking for fseek64... no >>>> > checking for fseeko... yes >>>> > checking for fstatvfs... yes >>>> > checking for ftell64... no >>>> > checking for ftello... yes >>>> > checking for statvfs... yes >>>> > checking for dup2... yes >>>> > checking for getcwd... yes >>>> > checking for strdup... yes >>>> > checking for getpgrp... yes >>>> > checking for setpgrp... (cached) yes >>>> > checking for gettimeofday... yes >>>> > checking for major... yes >>>> > checking for getaddrinfo... yes >>>> > checking getaddrinfo bug... good >>>> > checking for getnameinfo... yes >>>> > checking whether time.h and sys/time.h may both be included... yes >>>> > checking whether struct tm is in sys/time.h or time.h... time.h >>>> > checking for struct tm.tm_zone... yes >>>> > checking for struct stat.st_rdev... yes >>>> > checking for struct stat.st_blksize... yes >>>> > checking for struct stat.st_flags... no >>>> > checking for struct stat.st_gen... no >>>> > checking for struct stat.st_birthtime... no >>>> > checking for struct stat.st_blocks... yes >>>> > checking for time.h that defines altzone... no >>>> > checking whether sys/select.h and sys/time.h may both be >>>> included... yes >>>> > checking for addrinfo... yes >>>> > checking for sockaddr_storage... yes >>>> > checking whether char is unsigned... no >>>> > checking for an ANSI C-conforming const... yes >>>> > checking for working volatile... yes >>>> > checking for working signed char... yes >>>> > checking for prototypes... yes >>>> > checking for variable length prototypes and stdarg.h... yes >>>> > checking for socketpair... yes >>>> > checking if sockaddr has sa_len member... no >>>> > checking whether va_list is an array... no >>>> > checking for gethostbyname_r... yes >>>> > checking gethostbyname_r with 6 args... yes >>>> > checking for __fpu_control... yes >>>> > checking for --with-fpectl... no >>>> > checking for --with-libm=STRING... default LIBM="-lm" >>>> > checking for --with-libc=STRING... default LIBC="" >>>> > checking for x87-style double rounding... yes >>>> > checking whether tanh preserves the sign of zero... yes >>>> > checking for acosh... yes >>>> > checking for asinh... yes >>>> > checking for atanh... yes >>>> > checking for copysign... yes >>>> > checking for expm1... yes >>>> > checking for finite... yes >>>> > checking for hypot... yes >>>> > checking for log1p... yes >>>> > checking whether isinf is declared... yes >>>> > checking whether isnan is declared... yes >>>> > checking whether isfinite is declared... yes >>>> > checking wchar.h usability... yes >>>> > checking wchar.h presence... yes >>>> > checking for wchar.h... yes >>>> > checking for wchar_t... yes >>>> > checking size of wchar_t... 4 >>>> > checking for UCS-4 tcl... no >>>> > checking whether wchar_t is signed... yes >>>> > checking what type to use for unicode... unsigned short >>>> > checking whether byte ordering is bigendian... no >>>> > checking whether right shift extends the sign bit... yes >>>> > checking for getc_unlocked() and friends... yes >>>> > checking how to link readline libs... none >>>> > checking for rl_callback_handler_install in -lreadline... no >>>> > checking for rl_pre_input_hook in -lreadline... no >>>> > checking for rl_completion_display_matches_hook in -lreadline... no >>>> > checking for rl_completion_matches in -lreadline... no >>>> > checking for broken nice()... no >>>> > checking for broken poll()... no >>>> > checking for struct tm.tm_zone... (cached) yes >>>> > checking for working tzset()... yes >>>> > checking for tv_nsec in struct stat... yes >>>> > checking for tv_nsec2 in struct stat... no >>>> > checking whether mvwdelch is an expression... no >>>> > checking whether WINDOW has _flags... no >>>> > checking for is_term_resized... no >>>> > checking for resize_term... no >>>> > checking for resizeterm... no >>>> > checking for /dev/ptmx... yes >>>> > checking for /dev/ptc... no >>>> > checking for %zd printf() format support... yes >>>> > checking for socklen_t... yes >>>> > checking for build directories... done >>>> > configure: creating ./config.status >>>> > config.status: creating Makefile.pre >>>> > config.status: creating Modules/Setup.config >>>> > config.status: creating pyconfig.h >>>> > creating Modules/Setup >>>> > creating Modules/Setup.local >>>> > creating Makefile >>>> > >>>> > _______________________________________________ >>>> > Baypiggies mailing list >>>> > Baypiggies at python.org >>>> > To change your subscription options or unsubscribe: >>>> > http://mail.python.org/mailman/listinfo/baypiggies >>>> >>>> _______________________________________________ >>>> Baypiggies mailing list >>>> Baypiggies at python.org >>>> To change your subscription options or unsubscribe: >>>> http://mail.python.org/mailman/listinfo/baypiggies >>>> >> >> _______________________________________________ >> Baypiggies mailing list >> Baypiggies at python.org >> To change your subscription options or unsubscribe: >> http://mail.python.org/mailman/listinfo/baypiggies > -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ From glen at glenjarvis.com Fri Apr 30 21:35:38 2010 From: glen at glenjarvis.com (Glen Jarvis) Date: Fri, 30 Apr 2010 12:35:38 -0700 Subject: [Baypiggies] Unlinking symlinks Message-ID: I hate to ask such an absolutely simple question, but for what I'm doing I have to be *absolutely certain* to get this right :) When deleting symlinks, I think I've always used os.unlink() although it's the same as os.remove(). I can't tell in the documentation, but I want to be abso-bloody-lutely certain that I'm deleting the link and not the file that it points to. This is for a very large file system clean-up on a data system that would be a bear to replace. We wish to clean up specific symbolic links that I can find easily, but not the files that they point to. Is os.unlink() guaranteed to touch the symlink only? Also, semantically, is this "unlinking" a hard unlinking and therefore the same as remove (i.e., which would be easier for someone who is reading the code to understand/yet still be accurate). Cheers, Glen -- Whatever you can do or imagine, begin it; boldness has beauty, magic, and power in it. -- Goethe -------------- next part -------------- An HTML attachment was scrubbed... URL: From ferringb at gmail.com Fri Apr 30 22:30:44 2010 From: ferringb at gmail.com (Brian Harring) Date: Fri, 30 Apr 2010 13:30:44 -0700 Subject: [Baypiggies] Unlinking symlinks In-Reply-To: References: Message-ID: <20100430203044.GA30318@hrair> On Fri, Apr 30, 2010 at 12:35:38PM -0700, Glen Jarvis wrote: > I hate to ask such an absolutely simple question, but for what I'm > doing I have to be *absolutely certain* to get this right :) > > When deleting symlinks, I think I've always used os.unlink() although > it's the same as os.remove(). > > I can't tell in the documentation, but I want to be abso-bloody-lutely > certain that I'm deleting the link and not the file that it points to. > This is for a very large file system clean-up on a data system that > would be a bear to replace. We wish to clean up specific symbolic links > that I can find easily, but not the files that they point to. > > Is os.unlink() guaranteed to touch the symlink only? Also, > semantically, is this "unlinking" a hard unlinking and therefore the > same as remove (i.e., which would be easier for someone who is reading > the code to understand/yet still be accurate). unlink/remove are literally the same cfunction in the src. Beyond that, unlink works on the targeted node only- it does *not* resolve through the sym. ~harring -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From andrew at atoulou.se Fri Apr 30 22:34:54 2010 From: andrew at atoulou.se (Andrew Akira Toulouse) Date: Fri, 30 Apr 2010 13:34:54 -0700 Subject: [Baypiggies] Unlinking symlinks In-Reply-To: References: Message-ID: I'm pretty sure os.unlink() calls the OS's unlink function (as the name might imply). The documentation for it (`info unlink`; the man page is a summary which points to this) has the following: [snip] DESCRIPTION unlink() deletes a name from the file system. If that name was the last link to a file and no processes have the file open the file is deleted and the space it was using is made available for reuse. If the name was the last link to a file but any processes still have the file open the file will remain in existence until the last file descriptor referring to it is closed. If the name referred to a symbolic link the link is removed. [snip] One think you should be careful of, though, is that you do not have a slash after the symlink. If it links to a directory then the slash dereferences the link. --Andy On Fri, Apr 30, 2010 at 12:35 PM, Glen Jarvis wrote: > I hate to ask such an absolutely simple question, but for what I'm doing I > have to be *absolutely certain* to get this right :) > > When deleting symlinks, I think I've always used os.unlink() although it's > the same as os.remove(). > > I can't tell in the documentation, but I want to be abso-bloody-lutely > certain that I'm deleting the link and not the file that it points to. This > is for a very large file system clean-up on a data system that would be a > bear to replace. We wish to clean up specific symbolic links that I can find > easily, but not the files that they point to. > > Is os.unlink() guaranteed to touch the symlink only? Also, semantically, > is this "unlinking" a hard unlinking and therefore the same as remove (i.e., > which would be easier for someone who is reading the code to understand/yet > still be accurate). > > > Cheers, > > > > Glen > -- > Whatever you can do or imagine, begin it; > boldness has beauty, magic, and power in it. > > -- Goethe > > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > http://mail.python.org/mailman/listinfo/baypiggies > -------------- next part -------------- An HTML attachment was scrubbed... URL: From keith at dartworks.biz Fri Apr 30 22:52:14 2010 From: keith at dartworks.biz (Keith Dart) Date: Fri, 30 Apr 2010 13:52:14 -0700 Subject: [Baypiggies] Unlinking symlinks In-Reply-To: References: Message-ID: <20100430135214.0462e10c@dartworks.biz> === On Fri, 04/30, Glen Jarvis wrote: === > Is os.unlink() guaranteed to touch the symlink only? Also, > semantically, is this "unlinking" a hard unlinking and therefore the > same as remove (i.e., which would be easier for someone who is > reading the code to understand/yet still be accurate). === That is just wrapper for the unlink stdlib function. man 2 unlink says: If the name referred to a symbolic link the link is removed. You can also do a little test to verify it. -- Keith Dart -- -- -------------------- Keith Dart ======================= From brent.tubbs at gmail.com Fri Apr 30 23:50:26 2010 From: brent.tubbs at gmail.com (Brent Tubbs) Date: Fri, 30 Apr 2010 14:50:26 -0700 Subject: [Baypiggies] Unlinking symlinks In-Reply-To: <20100430135214.0462e10c@dartworks.biz> References: <20100430135214.0462e10c@dartworks.biz> Message-ID: I did a quick test creating and symlinking a file in bash, then calling unlink in Python, and finally looking at the results again from bash. The source file appears to remain untouched. Complete bash and python steps: brent at mae ~/tmp $ touch blah brent at mae ~/tmp $ ls -l total 0 -rw-r--r-- 1 brent brent 0 2010-04-30 14:46 blah brent at mae ~/tmp $ ln -s blah blahlink brent at mae ~/tmp $ ls -l total 0 -rw-r--r-- 1 brent brent 0 2010-04-30 14:46 blah lrwxrwxrwx 1 brent brent 4 2010-04-30 14:46 blahlink -> blah brent at mae ~/tmp $ ipython In [1]: import os In [2]: os.unlink('blahlink') In [3]: Do you really want to exit ([y]/n)? brent at mae ~/tmp $ ls -l total 0 -rw-r--r-- 1 brent brent 0 2010-04-30 14:46 blah Hope that helps! Brent On Fri, Apr 30, 2010 at 1:52 PM, Keith Dart wrote: > === On Fri, 04/30, Glen Jarvis wrote: === > > Is os.unlink() guaranteed to touch the symlink only? Also, > > semantically, is this "unlinking" a hard unlinking and therefore the > > same as remove (i.e., which would be easier for someone who is > > reading the code to understand/yet still be accurate). > > === > > That is just wrapper for the unlink stdlib function. > > man 2 unlink says: > > If the name referred to a symbolic link the link is removed. > > You can also do a little test to verify it. > > > > -- Keith Dart > > -- > -- -------------------- > Keith Dart > > ======================= > _______________________________________________ > Baypiggies mailing list > Baypiggies at python.org > To change your subscription options or unsubscribe: > http://mail.python.org/mailman/listinfo/baypiggies > -------------- next part -------------- An HTML attachment was scrubbed... URL: