On 07/14/2013 01:02 AM, Jim Mooney wrote:
On 13 July 2013 21:41, eryksun wrote:
A lot of new packages support versions 2.6+, which have the "with"
statement enabled.
So, since I'm using 2.7 I don't need generators or with?
Then all I'm using to be 3.3ish, would be:
from __future__ import
On 07/14/2013 12:37 AM, Jim Mooney wrote:
On 13 July 2013 20:03, Steven D'Aprano wrote:
I don't understand that last sentence.
Ah, I can be marvelously unclear. I keep forgetting telepathy only works
on my home planet ;')
You still have done nothing to explain the "last sentence." You
On 13 July 2013 21:41, eryksun wrote:
>
> A lot of new packages support versions 2.6+, which have the "with"
> statement enabled.
>
> So, since I'm using 2.7 I don't need generators or with?
Then all I'm using to be 3.3ish, would be:
from __future__ import division, print_function
import sys
if
On 13 July 2013 20:03, Steven D'Aprano wrote:
>
> I don't understand that last sentence.
Ah, I can be marvelously unclear. I keep forgetting telepathy only works
on my home planet ;')
I wiped everything out to start fresh with Py27, so this is just a very
simple example of what worked in sendi
On 14/07/13 09:29, Jim Mooney wrote:
Which brings up a question. I finally settled on Python 2.7 for various
reasons, but find some 3.3 things useful. Generators are one-off and input
is one-off, so they match well for testing, for instance.
I don't understand that last sentence.
I checke
On 07/13/2013 07:45 PM, Dave Angel wrote:
On 07/13/2013 07:29 PM, Jim Mooney wrote:
Dave Angel
Where I got confused is I'm importing a module with a manual input, then
renaming the input function to a generator function in my program , so I
can bypass manual input and feed the module to
On 07/13/2013 07:29 PM, Jim Mooney wrote:
Dave Angel
You still don't understand. If you write a module and I import it, then
other imports BY ME don't affect your module. Whether it's a __future__ one
or not. My import affects my global namespace, not yours. My compile-time
switches affect
Dave Angel
You still don't understand. If you write a module and I import it, then
> other imports BY ME don't affect your module. Whether it's a __future__ one
> or not. My import affects my global namespace, not yours. My compile-time
> switches affect my divide, not yours. Same thing.
>
A
On 07/13/2013 02:29 PM, Jim Mooney wrote:
Steven D'Aprano
No, actually, it's the opposite of a gotcha. If a module expects to use
truncated division, and *fails* to "from __future__ import division",
that's what it needs to get. If your import would change what the other
module sees, then you c
On 07/13/2013 01:48 PM, Alan Gauld wrote:
On 13/07/13 16:08, Brett Wunderlich wrote:
commanded by a Button. Once the button is pressed the values in the
fields should result in a calculation - the values should all be numeric
You'll need to convert between strings and numbers, the GUI display
Steven D'Aprano
No, actually, it's the opposite of a gotcha. If a module expects to use
truncated division, and *fails* to "from __future__ import division",
that's what it needs to get. If your import would change what the other
module sees, then you could change the behaviour of the other modul
On 13/07/13 16:08, Brett Wunderlich wrote:
commanded by a Button. Once the button is pressed the values in the
fields should result in a calculation - the values should all be numeric
You'll need to convert between strings and numbers, the GUI displays
strings (with one exception, see below)
Greetings pythonistas,
I have been exploring the use of Tkinter trying to write a fairly simple
program which will accept data from a GUI with 3 Entry fields that is commanded
by a Button. Once the button is pressed the values in the fields should result
in a calculation - the values should all
t-packages/pypi_classifiers-0.1-py2.7.egg/EGG-INFO/top_level.txt'
>>>>> quit()
>> antonia@antonia-HP-2133/usr/local/lib/python2.7/dist-packages/pypi_classifiers-0.1-py2.7.egg/EGG-INFO
>> $ ls -l
>> total 24
>> -rw
Hi,
On 13 July 2013 15:14, Albert-Jan Roskam wrote:
> IOError: [Errno 13] Permission denied:
> '/usr/local/lib/python2.7/dist-packages/pypi_classifiers-0.1-py2.7.egg/EGG-INFO/top_level.txt'
> >>> quit()
> antonia@antonia-HP-2133/usr/local/lib/python2.7/dist-packages/pypi_classifiers-0.1-py2.7.e
On 13/07/13 05:05, Jack Little wrote:
Is there a way in python to do matrix multiplication and its inverse? No
external modules is preferred, but it is ok.
If you have numpy, you should use that.
If you want a pure Python version, here's a quick and dirty matrix multiplier
that works only f
On 13/07/13 18:39, Jim Mooney wrote:
On 13 July 2013 00:54, eryksun wrote:
A __future__ import modifies compilation of the current module.
Hmm, so if I import a module that uses truncated division, that's what I
get, even though I imported __future__ division. OTOH, a non-future import
wil
On 13 July 2013 00:54, eryksun wrote:
> A __future__ import modifies compilation of the current module.
>
Hmm, so if I import a module that uses truncated division, that's what I
get, even though I imported __future__ division. OTOH, a non-future import
will be used by a module imported after i
18 matches
Mail list logo
