Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #74743 > unrolled thread

Python 3.4.1 64 bit Version

Back to article view | Back to comp.lang.python

Contents

  Python 3.4.1 64 bit Version cjwilliams43@gmail.com - 2014-07-18 06:29 -0700
    Re: Python 3.4.1 64 bit Version Chris “Kwpolska” Warrick <kwpolska@gmail.com> - 2014-07-18 15:48 +0200
    Re: Python 3.4.1 64 bit Version Zachary Ware <zachary.ware+pylist@gmail.com> - 2014-07-18 08:53 -0500
    Re: Python 3.4.1 64 bit Version Zachary Ware <zachary.ware+pylist@gmail.com> - 2014-07-18 08:54 -0500
    Re: Python 3.4.1 64 bit Version Andrew Berg <aberg010@my.hennepintech.edu> - 2014-07-18 08:59 -0500
    Re: Python 3.4.1 64 bit Version "Colin J. Williams" <cjwilliams43@gmail.com> - 2014-07-18 14:16 -0400
    Re: Python 3.4.1 64 bit Version Chris “Kwpolska” Warrick <kwpolska@gmail.com> - 2014-07-18 20:56 +0200
    Re: Python 3.4.1 64 bit Version Terry Reedy <tjreedy@udel.edu> - 2014-07-18 19:23 -0400
    Re: Python 3.4.1 64 bit Version Chris “Kwpolska” Warrick <kwpolska@gmail.com> - 2014-07-19 11:24 +0200

#74743 — Python 3.4.1 64 bit Version

The version given on Python.org is "Python 3.4.1 (v3.4.1:c0e311e010fc, May 18 2014, 10:45:13) [MSC v.1600 64 bit (AMD64)] on win32".

This question is prompted by difficulties installing PyScripter.  What does "on win32" mean in the above.  I was using PyScripter on an AMD64 processor with Python 2.7.  Now, with an attempt to move to Python 3, I have grief.

How does one install "python-3.4.1.amd64-pdb"?

I would welcome any advice.

Thanks,

Colin W.

[toc] | [next] | [standalone]

#74744

On Fri, Jul 18, 2014 at 3:29 PM,  <cjwilliams43@gmail.com> wrote:
> The version given on Python.org is "Python 3.4.1 (v3.4.1:c0e311e010fc, May 18 2014, 10:45:13) [MSC v.1600 64 bit (AMD64)] on win32".
>
> This question is prompted by difficulties installing PyScripter.  What does "on win32" mean in the above.  I was using PyScripter on an AMD64 processor with Python 2.7.  Now, with an attempt to move to Python 3, I have grief.
>
> How does one install "python-3.4.1.amd64-pdb"?
>
> I would welcome any advice.
>
> Thanks,
>
> Colin W.
> --
> https://mail.python.org/mailman/listinfo/python-list

“win32” is the name given to the Windows API as of Windows NT 3.1 and
Windows 95.  The “AMD64” part in parentheses tells the truth, that
you’re actually running the 64-bit version (which can cause problems,
though — it’s better to use the 32-bit version, IMO)

-- 
Chris “Kwpolska” Warrick <http://chriswarrick.com/>
PGP: 5EAAEA16
stop html mail | always bottom-post | only UTF-8 makes sense

[toc] | [prev] | [next] | [standalone]

#74745

On Fri, Jul 18, 2014 at 8:29 AM,  <cjwilliams43@gmail.com> wrote:
> The version given on Python.org is "Python 3.4.1 (v3.4.1:c0e311e010fc, May 18 2014, 10:45:13) [MSC v.1600 64 bit (AMD64)] on win32".
>
> This question is prompted by difficulties installing PyScripter.  What does "on win32" mean in the above.  I was using PyScripter on an AMD64 processor with Python 2.7.  Now, with an attempt to move to Python 3, I have grief.
>
> How does one install "python-3.4.1.amd64-pdb"?
>
> I would welcome any advice.

The problem there isn't "on win32", it's ".4" :).  Unless I've just
missed the announcement PyScripter has not been updated to support
Python 3.4, and I haven't figured out a way to trick it into working.
However, PyScripter works fine with Python 3.3, and there were no
syntax changes between 3.3 and 3.4.  What I have found to work fairly
well is to use PyScripter with 3.3, then test your program from a
command prompt with 3.4.

For the record, all versions of CPython on Windows (not counting
anything relating to cygwin) are "on win32" regardless of the
bittedness of the processor or the interpreter.

Hope this helps,
-- 
Zach

[toc] | [prev] | [next] | [standalone]

#74746

On Fri, Jul 18, 2014 at 8:48 AM, Chris “Kwpolska” Warrick
<kwpolska@gmail.com> wrote:
> “win32” is the name given to the Windows API as of Windows NT 3.1 and
> Windows 95.  The “AMD64” part in parentheses tells the truth, that
> you’re actually running the 64-bit version (which can cause problems,
> though — it’s better to use the 32-bit version, IMO)

What problems have you run into with the 64-bit version?  The only
issues I've had have been my own problems with installing some
versions as 32-bit and others as 64, and forgetting which was which.

-- 
Zach

[toc] | [prev] | [next] | [standalone]

#74747

On 2014.07.18 08:53, Zachary Ware wrote:
> For the record, all versions of CPython on Windows (not counting
> anything relating to cygwin) are "on win32" regardless of the
> bittedness of the processor or the interpreter.
> 
And in case you need more reassurance, there is the platform module in the stdlib.
https://docs.python.org/3/library/platform.html

[toc] | [prev] | [next] | [standalone]

#74764

[Multipart message — attachments visible in raw view] — view raw

Thanks to Chris and Zachary,

I shall retreat to Python 3.3

*pro tem*

*Colin W.*


On 18 July 2014 09:53, Zachary Ware <zachary.ware+pylist@gmail.com> wrote:

> On Fri, Jul 18, 2014 at 8:29 AM,  <cjwilliams43@gmail.com> wrote:
> > The version given on Python.org is "Python 3.4.1 (v3.4.1:c0e311e010fc,
> May 18 2014, 10:45:13) [MSC v.1600 64 bit (AMD64)] on win32".
> >
> > This question is prompted by difficulties installing PyScripter.  What
> does "on win32" mean in the above.  I was using PyScripter on an AMD64
> processor with Python 2.7.  Now, with an attempt to move to Python 3, I
> have grief.
> >
> > How does one install "python-3.4.1.amd64-pdb"?
> >
> > I would welcome any advice.
>
> The problem there isn't "on win32", it's ".4" :).  Unless I've just
> missed the announcement PyScripter has not been updated to support
> Python 3.4, and I haven't figured out a way to trick it into working.
> However, PyScripter works fine with Python 3.3, and there were no
> syntax changes between 3.3 and 3.4.  What I have found to work fairly
> well is to use PyScripter with 3.3, then test your program from a
> command prompt with 3.4.
>
> For the record, all versions of CPython on Windows (not counting
> anything relating to cygwin) are "on win32" regardless of the
> bittedness of the processor or the interpreter.
>
> Hope this helps,
> --
> Zach
>

[toc] | [prev] | [next] | [standalone]

#74767

On Fri, Jul 18, 2014 at 3:54 PM, Zachary Ware
<zachary.ware+pylist@gmail.com> wrote:
> On Fri, Jul 18, 2014 at 8:48 AM, Chris “Kwpolska” Warrick
> <kwpolska@gmail.com> wrote:
>> “win32” is the name given to the Windows API as of Windows NT 3.1 and
>> Windows 95.  The “AMD64” part in parentheses tells the truth, that
>> you’re actually running the 64-bit version (which can cause problems,
>> though — it’s better to use the 32-bit version, IMO)
>
> What problems have you run into with the 64-bit version?  The only
> issues I've had have been my own problems with installing some
> versions as 32-bit and others as 64, and forgetting which was which.

This is one of the issues: you can easily mess up 32-bit and 64-bit,
and not even notice that (AppVeyor had an issue with that lately —
they switched python to 64 but left VC++ as 32).

It’s also slightly easier to find pre-made binaries for 32-bit than
64-bit.  In general, life in 64-bits on Windows is kinda hard, for
everyone involved.


-- 
Chris “Kwpolska” Warrick <http://chriswarrick.com/>
PGP: 5EAAEA16
stop html mail | always bottom-post | only UTF-8 makes sense

[toc] | [prev] | [next] | [standalone]

#74784

On 7/18/2014 2:56 PM, Chris “Kwpolska” Warrick wrote:

> It’s also slightly easier to find pre-made binaries for 32-bit than
> 64-bit.

Searching 'python windows binaries' on Google and the first hit is 
http://www.lfd.uci.edu/~gohlke/pythonlibs/
"This page provides 32- and 64-bit Windows binaries of many scientific 
open-source extension packages for the official CPython distribution of 
the Python programming language."

He or they are currently compiling both 32 and 64 bits binaries for 2.7, 
3.3, and 3.4.

-- 
Terry Jan Reedy

[toc] | [prev] | [next] | [standalone]

#74802

On Sat, Jul 19, 2014 at 1:23 AM, Terry Reedy <tjreedy@udel.edu> wrote:
> On 7/18/2014 2:56 PM, Chris “Kwpolska” Warrick wrote:
>
>> It’s also slightly easier to find pre-made binaries for 32-bit than
>> 64-bit.
>
>
> Searching 'python windows binaries' on Google and the first hit is
> http://www.lfd.uci.edu/~gohlke/pythonlibs/
> "This page provides 32- and 64-bit Windows binaries of many scientific
> open-source extension packages for the official CPython distribution of the
> Python programming language."
>
> He or they are currently compiling both 32 and 64 bits binaries for 2.7,
> 3.3, and 3.4.

I know that site, but its binaries are not used by `pip` while wheels
published on PyPI are — and those wheels are not always available for
64-bit.

-- 
Chris “Kwpolska” Warrick <http://chriswarrick.com/>
PGP: 5EAAEA16
stop html mail | always bottom-post | only UTF-8 makes sense

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web