On Fri, Jan 27, 2017 at 3:28 PM, Ethan Furman wrote:
> On 01/27/2017 01:07 PM, Brent Brinkley wrote:
>
>> Suggested structure:
>>
>> print() <| some_func() <| another_func("Hello")
>>
>
> My first question is what does this look like when print() and some_func()
> have other parameters? In oth
On Jan 27, 2017 4:51 PM, "Random832" wrote:
On Fri, Jan 27, 2017, at 12:54, C Anthony Risinger wrote:
> I know the scientific community is a big and important part of the
> Python ecosystem, but I honestly believe other parts of Python are
> suffering from any dragging of feet at this point. Pyth
On Fri, Jan 27, 2017, at 12:54, C Anthony Risinger wrote:
> I know the scientific community is a big and important part of the
> Python ecosystem, but I honestly believe other parts of Python are
> suffering from any dragging of feet at this point. Python 3 has been
> out nearly a decade, and I thi
On 01/27/2017 01:07 PM, Brent Brinkley wrote:
I’m relatively new to the world of python
Welcome!
but in my short time here I’ve
fallen in love with how readable this language is. One issue that I’ve
seen in a lot of languages struggle with is nested function calls.
Parenthesis when neste
Hi,
This would break apart as soon as one of left functions takes more than one
parameter.
Best regards,
João Santos
On Fri, 27 Jan 2017, 22:08 Brent Brinkley, wrote:
> HI Everyone,
>
> I’m relatively new to the world of python but in my short time here I’ve
> fallen in love with how readable
HI Everyone,
I’m relatively new to the world of python but in my short time here I’ve fallen
in love with how readable this language is. One issue that I’ve seen in a lot
of languages struggle with is nested function calls. Parenthesis when nested
inherently create readability issues. I stumble
So I realize this is subjective and just a personal experience, but over
the last 3-5 years I've really watched Python usage and popularity decline
in the "hearts and minds" of my peers, across a few different companies I
work with. At my current gig we don't even use Python anymore for tools
that
On 1/27/2017 4:38 AM, Nathaniel Smith wrote:
On Fri, Jan 27, 2017 at 1:32 AM, Stephan Houben
wrote:
Hi all,
FWIW, I got the following statement from here:
https://github.com/numpy/numpy/wiki/Numerical-software-on-Windows
"Standard numpy and scipy binary releases on Windows use pre-compiled
On Fri, Jan 27, 2017 at 1:32 AM, Stephan Houben wrote:
> Hi all,
>
> FWIW, I got the following statement from here:
>
> https://github.com/numpy/numpy/wiki/Numerical-software-on-Windows
>
> "Standard numpy and scipy binary releases on Windows use pre-compiled ATLAS
> libraries and are 32-bit only
Hi all,
FWIW, I got the following statement from here:
https://github.com/numpy/numpy/wiki/Numerical-software-on-Windows
"Standard numpy and scipy binary releases on Windows use pre-compiled ATLAS
libraries and are 32-bit only because of the difficulty of compiling ATLAS
on 64-bit Windows. "
Mi
On 27.01.2017 06:13, Terry Reedy wrote:
> On 1/26/2017 5:32 PM, M.-A. Lemburg wrote:
>
>> Many applications on Windows are still 32-bit applications and
>> unless you process large amounts of data, a 32-bit Python
>> system is well worth using. In some cases, it's even needed,
>> e.g. if you have
Resending because Google Groups handling of mailing lists is broken
:-( Sorry to anyone who gets double posts.
On 27 January 2017 at 08:39, Paul Moore wrote:
> On 27 January 2017 at 06:22, Denis Akhiyarov
> wrote:
>> The problem is not in Python packages, but when gluing Python with other
>> W
12 matches
Mail list logo
