Re: Python 3 is killing Python

2014-07-15 Thread Chris Angelico
On Wed, Jul 16, 2014 at 4:44 PM, Marko Rauhamaa wrote: > Chris Angelico : > >> Python defaults to the most common case, where they're connected to a >> console, and does its best to allow print() to write Unicode to any >> console. > > I don't know where you pull your statistics. Heaps and HEAPS

Re: Python 3 is killing Python

2014-07-15 Thread Marko Rauhamaa
Chris Angelico : > Python defaults to the most common case, where they're connected to a > console, and does its best to allow print() to write Unicode to any > console. I don't know where you pull your statistics. Be that as it may, the main purpose of sys.stdin is to receive the workload and s

Re: Python 3 is killing Python

2014-07-15 Thread Chris Angelico
On Wed, Jul 16, 2014 at 3:52 PM, Marko Rauhamaa wrote: > Steven D'Aprano : > >> On Tue, 15 Jul 2014 23:01:25 +0300, Marko Rauhamaa wrote: >>> In fact, I find the lazy use of Unicode strings at least as scary as >>> the lazy use of byte strings, especially since Python 3 sneaks >>> Unicode to the o

Re: Python 3 is killing Python

2014-07-15 Thread Marko Rauhamaa
Steven D'Aprano : > On Tue, 15 Jul 2014 23:01:25 +0300, Marko Rauhamaa wrote: >> In fact, I find the lazy use of Unicode strings at least as scary as >> the lazy use of byte strings, especially since Python 3 sneaks >> Unicode to the outer interfaces of the program (files, IPC). > > I'm not entire

Re: ISO8583

2014-07-15 Thread Gary Herron
On 07/15/2014 08:56 PM, barontro...@gmail.com wrote: Hi, I'm very new to python programming. I would like to ask how come when I send ISO8583 to the server, I didn't get any response back. This is not really a Python question, but should rather be asked of whoever created the ISO8583 module.

Re: multiprocessing problem: queue.get() not finding pushed values

2014-07-15 Thread Chris Angelico
On Wed, Jul 16, 2014 at 6:32 AM, Charles Hixson wrote: > from queue import Empty, Full Not sure what this is for, you never use those names (and I don't have a 'queue' module to import from). Dropped that line. In any case, I don't think it's your problem... > if __name__ == "__main__": > db

Re: Python 3 is killing Python

2014-07-15 Thread Chris Angelico
On Wed, Jul 16, 2014 at 1:51 PM, Steven D'Aprano wrote: > Perhaps the *stupidest* thing the author of the "Python 3 is killing > Python" blog post wrote was that it's easier to port Python code to a > *completely different language*. I cannot fathom the idiocy of somebody > who bitches and moans t

ISO8583

2014-07-15 Thread barontronik
Hi, I'm very new to python programming. I would like to ask how come when I send ISO8583 to the server, I didn't get any response back. If I send it incorrect parameter, the server will reply but if I send it correctly, the server didn't response. The original client is in java using ISOMUX, I

Re: Python 3 is killing Python

2014-07-15 Thread Steven D'Aprano
On Tue, 15 Jul 2014 23:01:25 +0300, Marko Rauhamaa wrote: > Steven D'Aprano : > >> Unicode strings in Python 2 are second class entities. > > I don't see that. They form a type just like, say, complex. I didn't say they were a second class type. I choose my words carefully, although I guess wh

Re: Python 3 is killing Python

2014-07-15 Thread Abhiram R
On Wed, Jul 16, 2014 at 5:23 AM, Rick Johnson wrote: > On Tuesday, July 15, 2014 5:40:29 PM UTC-5, Abhiram R wrote: > > [snip excessive quotations] > > Aah. Understood. Apologies for the "noobishness" :) > > Noobishness can be tolerated for a "reasonable" time, > especially when the "noob" active

Re: Twitter Client on Terminal by Python

2014-07-15 Thread Orakaro
On Tuesday, July 15, 2014 3:27:15 PM UTC+9, Omar Abou Mrad wrote: > Dear Orakaro, > > > Cool app you have there. Please consider the following comments as feedback > in the most positive sense possible: > > > - I didn't care for the figlet, it's noise beyond anything else, if you drop > it, y

Re: Twitter Client on Terminal by Python

2014-07-15 Thread Orakaro
On Tuesday, July 15, 2014 5:36:40 AM UTC+9, Terry Reedy wrote: > On 7/13/2014 11:51 PM, Chris Angelico wrote: > > > On Mon, Jul 14, 2014 at 12:18 PM, Orakaro wrote: > > >> I use README.md for Github and README.rst for PyPi. Is there a way to use > >> only one file for both sites ? > > > > > >

Re: Mac python py2app problem

2014-07-15 Thread Kevin Walzer
On 7/15/14, 9:56 PM, Nicholas Cannon wrote: Hey i have made an app and i have made a .msi for windows with py2exe and i have also exported it with py2app on mac. No problems here they all work fine. I then put the .msi on sourceforge and it works great but when i put the .app on there and down

Re: Python 3 is killing Python

2014-07-15 Thread Steven D'Aprano
On Wed, 16 Jul 2014 03:07:23 +0530, Abhiram R wrote about Python 2.7: > Annd I just saw that the lifetime has been pushed up to 2020 :) > #SelfCorrected Even when free support runs out, commercial support will be available. Red Hat is already committed to supporting Python 2.7 until 2023, and if

Mac python py2app problem

2014-07-15 Thread Nicholas Cannon
Hey i have made an app and i have made a .msi for windows with py2exe and i have also exported it with py2app on mac. No problems here they all work fine. I then put the .msi on sourceforge and it works great but when i put the .app on there and download it it says something like i can open this

Re: Python 3 is killing Python

2014-07-15 Thread MRAB
On 2014-07-16 00:53, Rick Johnson wrote: On Tuesday, July 15, 2014 5:40:29 PM UTC-5, Abhiram R wrote: [snip excessive quotations] Aah. Understood. Apologies for the "noobishness" :) Noobishness can be tolerated for a "reasonable" time, especially when the "noob" actively seeks to improve his s

Re: Python 3 is killing Python

2014-07-15 Thread Kevin Walzer
On 7/15/14, 6:38 PM, Mark Lawrence wrote: I did see your correction but it gave me an opportunity to mention google groups, something that just can't be missed If the newgroup had a filter to trim out complaints about Google groups, half the traffic would be gone. :-) -- Kevin Walzer Code

Re: Python 3 is killing Python

2014-07-15 Thread Rick Johnson
On Tuesday, July 15, 2014 5:40:29 PM UTC-5, Abhiram R wrote: > [snip excessive quotations] > Aah. Understood. Apologies for the "noobishness" :) Noobishness can be tolerated for a "reasonable" time, especially when the "noob" actively seeks to improve his skills, as you are doing, so kudos to you

Re: Python 3 is killing Python

2014-07-15 Thread Joshua Landau
On 15 July 2014 23:40, Abhiram R wrote: > On Wed, Jul 16, 2014 at 4:00 AM, Kevin Walzer wrote: >> >> ...but Unix/newsgroup ettiquette says that it's gauche to [top post], >> because it presents an unacceptable cognitive burden to the user trying to >> catch the context of the thread by forcing t

Re: Python 3 is killing Python

2014-07-15 Thread Abhiram R
On Wed, Jul 16, 2014 at 4:00 AM, Kevin Walzer wrote: > "Top posting" is the practice of responding to an e-mail thread by putting > your response at the top of the text you are quoting. It's standard > practice in the corporate world... > > On 7/15/14, 6:13 PM, Abhiram R wrote: > >> a) What is "t

Re: Python 3 is killing Python

2014-07-15 Thread Mark Lawrence
On 15/07/2014 23:13, Abhiram R wrote: a) What is "top post"? b)I did correct myself in the next post. Or maybe you missed that. On Wed, Jul 16, 2014 at 3:19 AM, Mark Lawrence mailto:breamore...@yahoo.co.uk>> wrote: On 15/07/2014 22:35, Abhiram R wrote: Umm..Guido Van Rossum said in

Re: Python 3 is killing Python

2014-07-15 Thread Kevin Walzer
"Top posting" is the practice of responding to an e-mail thread by putting your response at the top of the text you are quoting. It's standard practice in the corporate world... On 7/15/14, 6:13 PM, Abhiram R wrote: a) What is "top post"? ...but Unix/newsgroup ettiquette says that it's gau

Re: Python 3 is killing Python

2014-07-15 Thread Abhiram R
a) What is "top post"? b)I did correct myself in the next post. Or maybe you missed that. On Wed, Jul 16, 2014 at 3:19 AM, Mark Lawrence wrote: > On 15/07/2014 22:35, Abhiram R wrote: > >> Umm..Guido Van Rossum said in Pycon 2014 that Py 2.x would be supported >> only until 2015 :-| So...you kn

Re: Python 3 is killing Python

2014-07-15 Thread Mark Lawrence
On 15/07/2014 22:35, Abhiram R wrote: Umm..Guido Van Rossum said in Pycon 2014 that Py 2.x would be supported only until 2015 :-| So...you know.. you have like an year before you /do /have to migrate to 3.x . -- Abhiram.R M.Tech CSE (Sem 3) RVCE Bangalore a) please don't top post, this is alm

Re: Python 3 is killing Python

2014-07-15 Thread Abhiram R
Umm..Guido Van Rossum said in Pycon 2014 that Py 2.x would be supported only until 2015 :-| So...you know.. you have like an year before you *do *have to migrate to 3.x . On Wed, Jul 16, 2014 at 2:17 AM, Devin Jeanpierre wrote: > On Tue, Jul 15, 2014 at 1:24 PM, Mark Lawrence > wrote: > > On 1

Re: Python 3 is killing Python

2014-07-15 Thread Abhiram R
Annd I just saw that the lifetime has been pushed up to 2020 :) #SelfCorrected On Wed, Jul 16, 2014 at 3:05 AM, Abhiram R wrote: > Umm..Guido Van Rossum said in Pycon 2014 that Py 2.x would be supported > only until 2015 :-| So...you know.. you have like an year before you *do *have > to migrat

Re: Python 3 is killing Python

2014-07-15 Thread Ian Kelly
On Tue, Jul 15, 2014 at 2:20 PM, Rick Johnson wrote: > On Tuesday, July 15, 2014 1:53:27 PM UTC-5, Steven D'Aprano wrote: > >> No software developer is obliged to support their software >> forever, especially if they are giving it away for free >> [...] Nobody but nobody is supporting Python 1.1 a

Re: Python 3 is killing Python

2014-07-15 Thread Devin Jeanpierre
On Tue, Jul 15, 2014 at 1:24 PM, Mark Lawrence wrote: > On 15/07/2014 18:38, Marko Rauhamaa wrote: >> >> Chris Angelico : >> >>> Fine. Tell me how you would go about adding true Unicode support to >>> Python 2.7, while still having it able to import an unchanged program. >>> Trick question - it's

multiprocessing problem: queue.get() not finding pushed values

2014-07-15 Thread Charles Hixson
I don't think I can reduce it much beyond this. I'm trying to run Sqlite in a separate process, but I'm running into problems. *The code:* from collectionsimportnamedtuple from multiprocessing import Process, Queue, current_process from queue import Empty, Full Msg=namedtuple (

Re: Python 3 is killing Python

2014-07-15 Thread Rick Johnson
On Tuesday, July 15, 2014 1:53:27 PM UTC-5, Steven D'Aprano wrote: > No software developer is obliged to support their software > forever, especially if they are giving it away for free > [...] Nobody but nobody is supporting Python 1.1 any more, > no matter how many security holes it has. Of cou

Re: Python 3 is killing Python

2014-07-15 Thread Mark Lawrence
On 15/07/2014 18:38, Marko Rauhamaa wrote: Chris Angelico : Fine. Tell me how you would go about adding true Unicode support to Python 2.7, while still having it able to import an unchanged program. Trick question - it's fundamentally impossible, because an unchanged program will not distinguis

Re: Python 3 is killing Python

2014-07-15 Thread Marko Rauhamaa
Steven D'Aprano : > Unicode strings in Python 2 are second class entities. I don't see that. They form a type just like, say, complex. > It's not just that people will, in general, take the lazy way and > write "foo" instead of u"foo" for their strings. People live with their choices, and I don

Re: Python 3 is killing Python

2014-07-15 Thread Marko Rauhamaa
Steven D'Aprano : > On Tue, 15 Jul 2014 21:08:03 +0300, Marko Rauhamaa wrote: > >> I agree it was a grave mistake. > > On what basis do you believe it was a mistake? The supposed flaws in Python 2 weren't a good enough reason to break backward-compatibility. Marko -- https://mail.python.org/ma

Re: Python 3 is killing Python

2014-07-15 Thread Steven D'Aprano
On Tue, 15 Jul 2014 20:38:40 +0300, Marko Rauhamaa wrote: > Python 2 has always had unicode strings and [byte] strings. They were > always clearly distinguished. You really didn't have to change anything > for "true Unicode support". If that were true, then migrating from Python 2 to 3 would be m

Re: Python 3 is killing Python

2014-07-15 Thread Steven D'Aprano
On Tue, 15 Jul 2014 21:08:03 +0300, Marko Rauhamaa wrote: > I agree it was a grave mistake. On what basis do you believe it was a mistake? -- Steven -- https://mail.python.org/mailman/listinfo/python-list

Re: Python 3 is killing Python

2014-07-15 Thread Steven D'Aprano
On Tue, 15 Jul 2014 11:01:53 -0700, Rick Johnson wrote: > Are you so foolish as to believe that if code runs cleanly *immediately* > after translating via "2to3", that the code is now completely free from > translation bugs? If your code has a thorough set of unittests that continue to pass, then

Re: Python 3 is killing Python

2014-07-15 Thread Ian Kelly
On Tue, Jul 15, 2014 at 12:01 PM, Rick Johnson wrote: > On Tuesday, July 15, 2014 9:31:31 AM UTC-5, Chris Angelico wrote: >> [...] That said, though, I would advise you to give 2to3 a >> shot. You never know, it might do exactly what you need >> right out-of-the-box and give you a 3.x-compatible >

Re: Python 3 is killing Python

2014-07-15 Thread Grant Edwards
On 2014-07-15, alister wrote: > Never let the facts get in the way of a good punchline :-) Ah! That explains it! The Iraq war must have been a _joke_. It sure went over my head... -- Grant Edwards grant.b.edwardsYow! My Aunt MAUREEN was a

Re: Python 3 is killing Python

2014-07-15 Thread Marko Rauhamaa
Rick Johnson : > So in other words, "we're" know now we made a bad decision by creating > this Python3000 thing, because nobody seems to be jumping on the > bandwagon, but instead of admitting we were wrong, we'll just cling to > our new shiny *THING* and hope *EVENTUALLY*, if we brow-beat *ENOUGH

Re: Python 3 is killing Python

2014-07-15 Thread Rick Johnson
On Tuesday, July 15, 2014 9:31:31 AM UTC-5, Chris Angelico wrote: > [...] That said, though, I would advise you to give 2to3 a > shot. You never know, it might do exactly what you need > right out-of-the-box and give you a 3.x-compatible > codebase in one hit. Ha! Are you so foolish as to believ

Re: Python 3 is killing Python

2014-07-15 Thread Marko Rauhamaa
Chris Angelico : > Fine. Tell me how you would go about adding true Unicode support to > Python 2.7, while still having it able to import an unchanged program. > Trick question - it's fundamentally impossible, because an unchanged > program will not distinguish between bytes and text, but true Uni

Re: Python 3 is killing Python

2014-07-15 Thread alister
On Tue, 15 Jul 2014 15:50:46 +0100, MRAB wrote: > On 2014-07-15 13:19, alister wrote: >>> >>> Image, for a moment, a world WITHOUT the great USA! Yes, i know you >>> little commies love to curse the USA, and yes, there are many dark >>> sins committed within AND beyond her borders, but try to tell

Re: Python 3 is killing Python

2014-07-15 Thread Chris Angelico
On Wed, Jul 16, 2014 at 1:44 AM, Mark Lawrence wrote: > Or any one of > > https://pypi.python.org/pypi/six/1.7.3 > https://github.com/mitsuhiko/python-modernize > http://python-future.org/ > https://github.com/nandoflorestan/nine AIUI most of those sorts of things are designed for people maintain

Re: Python 3 is killing Python

2014-07-15 Thread Grant Edwards
On 2014-07-15, Kevin Walzer wrote: > I think it's more than a tempest in a teacup. > > The number of language revisions that result in deliberate, code-level > incompatibility out there is pretty small. People rightly expect that > code written for version 2.x of a language will continue to wor

Re: Python 3 is killing Python

2014-07-15 Thread Mark Lawrence
On 15/07/2014 15:31, Chris Angelico wrote: On Tue, Jul 15, 2014 at 11:57 PM, Kevin Walzer wrote: I've stayed with Python 2.7 because I've seen no benefit in 3.x that outweighs the hassle of going through my code line by line to make it compatible. And that's fine! The python-dev team has pro

Re: Python 3 is killing Python

2014-07-15 Thread Mark Lawrence
On 15/07/2014 13:19, alister wrote: Image, for a moment, a world WITHOUT the great USA! Yes, i know you little commies love to curse the USA, and yes, there are many dark sins committed within AND beyond her borders, but try to tell me you bass-turds, what nation in modern history has contribute

Re: NaN comparisons - Call For Anecdotes

2014-07-15 Thread Mark Lawrence
On 15/07/2014 13:32, Anders J. Munch wrote: By the way, which list is the appropriate one? The numpy and SciPy mailing lists are first and foremost about numpy and SciPy, I presume. Is there a general numerics-list somewhere also? I don't see any on https://mail.python.org/mailman/listinfo. T

Re: Python 3 is killing Python

2014-07-15 Thread MRAB
On 2014-07-15 13:19, alister wrote: Image, for a moment, a world WITHOUT the great USA! Yes, i know you little commies love to curse the USA, and yes, there are many dark sins committed within AND beyond her borders, but try to tell me you bass-turds, what nation in modern history has contribute

Re: Python 3 is killing Python

2014-07-15 Thread Anders Wegge Keller
Kevin Walzer writes: > I can only think of two widely used languages in the last decade where > there was this type of major break in binary compatibility: Perl and > Visual Basic. Lua 5.1, 5.2 and 5.3 are all incompatible to some extent. It's debatable how widely used Lua is as a stand-alone l

Re: Python 3 is killing Python

2014-07-15 Thread Chris Angelico
On Tue, Jul 15, 2014 at 11:57 PM, Kevin Walzer wrote: > The number of language revisions that result in deliberate, code-level > incompatibility out there is pretty small. People rightly expect that code > written for version 2.x of a language will continue to work with version > 3.x, even if 3.x

Re: Python 3 is killing Python

2014-07-15 Thread Kevin Walzer
On 7/15/14, 9:00 AM, Chris Angelico wrote: The problem isn't Python 2, nor Python 3, nor even the fact that there are two Pythons. The problem is that a lot of people don't understand when to choose one or the other, don't understand what the promises of support are, and (perhaps worst of all) ke

Re: xslt with python

2014-07-15 Thread varun bhatnagar
Hi Tim, Thanks a lot for the reply. I think I got the root cause of the problem. Before merging I am creating one dummy xml file on the fly and I am copying the content of first xml into that. This dummy file I am mentioning in xsl file and the URI is changing because of which it is not getting me

Re: xslt with python

2014-07-15 Thread Tim
On Tuesday, July 15, 2014 4:10:57 AM UTC-4, varun bhatnagar wrote: > I am trying to merge two xmls using xslt in python but the content of first > xml is not getting copied. The rules written in xsl file created are correct > because if I am executing it without python (directly from eclipse as I

Re: Python 3 is killing Python

2014-07-15 Thread Chris Angelico
On Tue, Jul 15, 2014 at 10:17 PM, Fabien wrote: > My two cents as a new pythonista and a scientist: isn't python2 killing > python? You're new to Python, and so you correctly want to work with Python 3. That's fine. That's excellent, in fact. You're starting out the right way, and avoiding all th

Re: Python 3 is killing Python

2014-07-15 Thread alister
On Mon, 14 Jul 2014 21:18:05 -0700, Rick Johnson wrote: > On Monday, July 14, 2014 9:11:47 PM UTC-5, Chris Angelico wrote: >> I dunno. It's not like Great Britain, Australia, or New Zealand did >> anything significant in either war, is it. > > Most of Europe occupied, London bombed into the stone

Re: NaN comparisons - Call For Anecdotes

2014-07-15 Thread Anders J. Munch
Steven D'Aprano: I'll give you the benefit of the doubt, and assume that when you first posted you hadn't realised that the audience here does not have the relevant experience, but by refusing to ask the question elsewhere, and by making snide comments that "they don't like beer", that pretty muc

Anything better than asyncio.as_completed() and asyncio.wait() to manage execution of large amount of tasks?

2014-07-15 Thread Valery Khamenya
Hi, both asyncio.as_completed() and asyncio.wait() work with lists only. No generators are accepted. Are there anything similar to those functions that pulls Tasks/Futures/coroutines one-by-one and processes them in a limited task pool? I have gazillion of Tasks, and do not want to instantiate th

Re: Python 3 is killing Python

2014-07-15 Thread alister
> > Image, for a moment, a world WITHOUT the great USA! Yes, i know you > little commies love to curse the USA, and yes, > there are many dark sins committed within AND beyond her borders, but > try to tell me you bass-turds, what nation in modern history has > contributed more technological achie

Re: Python 3 is killing Python

2014-07-15 Thread Fabien
My two cents as a new pythonista and a scientist: isn't python2 killing python? This old stuff is everywhere in the tutorials, docs, etc. and this is quite annoying. When I download a python notebook, the first thing I have to do is to translate it to py3. Which is not an easy task, given the f

networkx plot random graph Error

2014-07-15 Thread u2107
I am trying to read a file with 3 columns with col 1 and 2 as nodes/edges and column 3 as weight (value with decimal) I am trying to execute this code import networkx as nx G = nx.read_edgelist('file.txt', data=[("weight")]) G.edges(data=True) edge_labels = dict(((u, v), d["weight"]) for u,

xslt with python

2014-07-15 Thread varun bhatnagar
I am trying to merge two xmls using xslt in python but the content of first xml is not getting copied. The rules written in xsl file created are correct because if I am executing it without python (directly from eclipse as I have xslt plugin installed) it is getting merged fine. Can anybody help me

Re: Python 3 is killing Python

2014-07-15 Thread Mark Lawrence
On 15/07/2014 04:58, Michael Torrie wrote: On 06/03/2014 12:12 AM, wxjmfa...@gmail.com wrote: I was myself really suprised to fall on such a case and after thinking no, such cases may logically happen. Putting in this comment not for JMF but for poor souls who find this thread on a search and

Re: Python 3 is killing Python

2014-07-15 Thread Mark Lawrence
On 15/07/2014 05:40, Chris Angelico wrote: On Tue, Jul 15, 2014 at 2:18 PM, Rick Johnson wrote: Yeah, because nobody managed to do anything during all that time, the Royal Air Force was nowhere to be seen, and the various Resistances in occupied countries were completely ineffectual. Some mi