Re: Repair Install of 64 bit python

[Terry Reedy]

On 4/16/2021 10:15 AM, Cameron Simpson wrote:

On 16Apr2021 13:13, Dan Ciprus (dciprus)  wrote:

Isn't the recommended python3 way of pip-ing stuff:

python3 -m pip install ...

.. just curious.


If there's only one Python 3 installed then "pip3 install ..." _ought_
to be equivalent. However, in the face of virtualenvs etc there may
often be several pip3s.

Using "python3 -m pip install ..." ensures that you are using the pip
which is associated with "python3" (which you can adjust to be whichever
python3 you intend). This is why the "-m pip" form is recommended: it
definitely installs in the Python you'd be running.


It requires that pip itself be installed for pythonx, which can be 
ensured with "pythonx -m ensurepip".



--
Terry Jan Reedy

--
https://mail.python.org/mailman/listinfo/python-list

Re: Repair Install of 64 bit python

[Cameron Simpson]

On 16Apr2021 13:13, Dan Ciprus (dciprus)  wrote:
>Isn't the recommended python3 way of pip-ing stuff:
>
>python3 -m pip install ...
>
>.. just curious.

If there's only one Python 3 installed then "pip3 install ..." _ought_ 
to be equivalent. However, in the face of virtualenvs etc there may 
often be several pip3s.

Using "python3 -m pip install ..." ensures that you are using the pip 
which is associated with "python3" (which you can adjust to be whichever 
python3 you intend). This is why the "-m pip" form is recommended: it 
definitely installs in the Python you'd be running.

Cheers,
Cameron Simpson 
-- 
https://mail.python.org/mailman/listinfo/python-list

Re: Repair Install of 64 bit python

[Dan Ciprus (dciprus) via Python-list]

Isn't the recommended python3 way of pip-ing stuff:

python3 -m pip install ...

.. just curious.

On Thu, Apr 15, 2021 at 08:36:56PM -0500, o1bigtenor wrote:

On Thu, Apr 15, 2021 at 8:03 PM Dodson, Matthew
 wrote:


Hi,

Having an issue after installing 64 bit python. Can't pip install any packages. Get the 
error "No module named pip".



No expert here but to me that reads like you need to install 'pip'.

On linux I need to make sure its pip3 - - - for python 3.
Then after that's done you sounds be able to go $ pip3 install x .

HTH
--
https://mail.python.org/mailman/listinfo/python-list


--
Daniel Ciprus  .:|:.:|:.
CONSULTING ENGINEER.CUSTOMER DELIVERY   Cisco Systems Inc.
dcip...@cisco.com
tel: +1-703-484-0205
mob: +1-540-223-7098



signature.asc
Description: PGP signature
-- 
https://mail.python.org/mailman/listinfo/python-list

Re: Repair Install of 64 bit python

[o1bigtenor]

On Thu, Apr 15, 2021 at 8:03 PM Dodson, Matthew
 wrote:
>
> Hi,
>
> Having an issue after installing 64 bit python. Can't pip install any 
> packages. Get the error "No module named pip".
>

No expert here but to me that reads like you need to install 'pip'.

On linux I need to make sure its pip3 - - - for python 3.
Then after that's done you sounds be able to go $ pip3 install x .

HTH
-- 
https://mail.python.org/mailman/listinfo/python-list

Repair Install of 64 bit python

[Dodson, Matthew]

Hi,

Having an issue after installing 64 bit python. Can't pip install any packages. 
Get the error "No module named pip".

Thanks,
Matt


Matthew Dodson 
2020 Data Analytics/Video Intern
New York Football Giants
Quest Diagnostics Training Center
1925 Giants Drive
East Rutherford, NJ 07073
o: 201-806-1749
matthew.dod...@giants.nfl.net

This e-mail is intended only for the use of the individual or entity named 
above and contains confidential and privileged information.  If the reader of 
this message is not the intended recipient, or the employee or agent 
responsible to deliver it to the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender of the e-mail and destroy the original message.  
UNLESS CLEARLY STATED,  NOTHING IN THIS E-MAIL, IN ANY E-MAIL THREAD OF WHICH 
IT MAY BE A PART, OR IN ANY ATTACHMENTS THERETO, SHALL CONSTITUTE A BINDING 
CONTRACT, OR ANY CONTRACTUAL OBLIGATION, OR ANY INTENT TO ENTER INTO ANY 
BINDING OBLIGATIONS.
-- 
https://mail.python.org/mailman/listinfo/python-list

[issue38989] pip install selects 32 bit wheels for 64 bit python if vcvarsall.bat amd64_x86 in environment

[Vinay Sajip]

Vinay Sajip  added the comment:

FYI I'm in the process of updating distlib to add the get_platform() / 
get_host_platform() distinction. The next release should have it.

--
keywords: +3.5regression

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue38989] pip install selects 32 bit wheels for 64 bit python if vcvarsall.bat amd64_x86 in environment

[Steve Dower]

Steve Dower  added the comment:

I'm closing this as external, as the canonical source for platform tags is now 
the packaging library.

Either pip and/or distlib should switch to using that library or the logic 
included (which I'll note is considerably more complex - but also more well 
defined and tested - than what is in distutils).

--
resolution:  -> third party
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue38989] pip install selects 32 bit wheels for 64 bit python if vcvarsall.bat amd64_x86 in environment

[Kyle Altendorf]

Change by Kyle Altendorf :


--
nosy: +altendky

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26992] 64-bit Python 2.7.11 hangs in 64-bit Windows 10 - CMD and Git Bash

[Zachary Ware]

Zachary Ware  added the comment:

As this appears to be a 2.7-only issue, I'm going to go ahead and close it.

--
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue38989] pip install selects 32 bit wheels for 64 bit python if vcvarsall.bat amd64_x86 in environment

[Steve Dower]

Steve Dower  added the comment:

> maybe you have some relevant context

Nothing you haven't figured out yourself. As you say, they're both private 
functions, and as we investigated adding a "get_target_platform" function, it 
turned out that nearly all users were expecting the target platform, so rather 
than updating everything we added one for the less-common case.

get_host_platform was not defined before, so I'd say use it if it's there and 
use get_platform if it's not.

I doubt we're going to add any new public/supported APIs to distutils ever 
again, to be honest.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue38989] pip install selects 32 bit wheels for 64 bit python if vcvarsall.bat amd64_x86 in environment

[Kevin Puetz]

Change by Kevin Puetz :


--
nosy: +vinay.sajip

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue38989] pip install selects 32 bit wheels for 64 bit python if vcvarsall.bat amd64_x86 in environment

[Kevin Puetz]

Kevin Puetz  added the comment:

Just to link the various pieces together: I think 

https://bitbucket.org/pypa/distlib/src/2d145da7cb42590039fbd56a9ab764d5d4716a98/distlib/wheel.py#lines-53

is the place in distlib that's being breaking pip due to redefining 
distutils.util.get_platform() as the cross-compile target architecture  rather 
than the build architecture.

https://docs.python.org/3/distutils/apiref.html doesn't show it as a documented 
public function, but the commit Ryan linked did introduce a new 
get_host_plaform() that matches the old behavior; if that became public and 
distlib used itinstead (conditional on the python version?) that would also be 
a way to fix the symptom Ryan noted (pip now choosing the wrong wheel to 
install).

I don't know how the pieces here fit together well enough to now which side 
should change.

@zooba: adding you to the Cc since it was your comments at 
https://github.com/python/cpython/pull/11774#discussion_r254461961 that seem to 
have led to the decision to re-define get_platform, maybe you have some 
relevant context?

--
nosy: +steve.dower

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue38989] pip install selects 32 bit wheels for 64 bit python if vcvarsall.bat amd64_x86 in environment

[Kevin Puetz]

Kevin Puetz  added the comment:

Besides the fact the MSVC's target platform isn't really related to the 
architecture for dependencies being installed, I'm not sure VSCMD_ARG_TGT_ARCH 
is an appropriate variable to look at in the first place. It doesn't seem to be 
at all documented, and (from looking at the implemenation) it seems to be meant 
as how parse_cmd.bat communicates with vcvars.bat, dotnet.bat, winsdk.bat, etc 
(these are all sub-programms that make up vcvarsall.bat)

I think %PLATFORM% (which generally ends up set equal to %VSCMD_ARG_TGT_ARCH% 
once vsdevcmd\ext\vcvars.bat has done its thing) is might be a better variable 
that cross-compiling should actually look at when it wants to know what 
architecture MSVC will compile to.

--
nosy: +puetzk

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue38989] pip install selects 32 bit wheels for 64 bit python if vcvarsall.bat amd64_x86 in environment

[Ryan Thornton]

New submission from Ryan Thornton :

## Expected Behavior

pip install should download dependencies matching the architecture of the 
python executable being used.

## Actual Behavior

When calling pip install from a Visual Studio command prompt configured to 
cross compile from x64 to x86, pip installs wheels matching the architecture of 
Visual Studio's cross compile target (i.e. `VSCMD_ARG_TGT_ARCH=x86`) and not 
the architecture of python itself (x64).

This results in a broken installation of core libraries.

## Steps to Reproduce

System Details:
Windows 10 x64
Python 3.8 x64
Visual Studio 2017 15.9.14

Environment Details:
vcvarsall.bat amd64_x86

1. "C:\Program Files\Python38\python.exe" -mvenv "test"
2. cd test\Scripts
3. pip install cffi==1.13.2

Results in the following:

> Collecting cffi
>  Using cached 
> https://files.pythonhosted.org/packages/f8/26/5da5cafef77586e4f7a136b8a24bc81fd2cf1ecb71b6ec3998ffe78ea2cf/cffi-1.13.2-cp38-cp38-win32.whl

## Context

I think the regression was introduced here:
62dfd7d6fe11bfa0cd1d7376382c8e7b1275e38c

https://github.com/python/cpython/commit/62dfd7d6fe11bfa0cd1d7376382c8e7b1275e38c

--
components: Distutils
messages: 357936
nosy: Ryan Thornton, dstufft, eric.araujo
priority: normal
severity: normal
status: open
title: pip install selects 32 bit wheels for 64 bit python if vcvarsall.bat 
amd64_x86 in environment
type: behavior
versions: Python 3.8

___
Python tracker 
<https://bugs.python.org/issue38989>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26992] 64-bit Python 2.7.11 hangs in 64-bit Windows 10 - CMD and Git Bash

[Steve Dower]

Steve Dower added the comment:

I wonder if it's related to issue26882? Seems unlikely as they are very 
different versions, but it's possible.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26992] 64-bit Python 2.7.11 hangs in 64-bit Windows 10 - CMD and Git Bash

[R. David Murray]

R. David Murray added the comment:

Is there any way you can attach a debugger to the process and see what it is 
doing or where it is stuck?  Otherwise, unless someone else can reproduce this, 
I don't think there is much we can do with this bug report.

--
nosy: +r.david.murray

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26992] 64-bit Python 2.7.11 hangs in 64-bit Windows 10 - CMD and Git Bash

[Sam Taylor]

New submission from Sam Taylor:

We have seen an issue where the 64-bit 2.7.11 Python Interpreter hangs whilst 
trying to run it in either Command Prompt or Git Bash on 64-bit Windows 10.

The issue is intermittent, the interpreter will run sometimes but will often 
hang immediately after typing 'python + ENTER' in either of the terminals.  
There seems to be no pattern when it won't work.

We haven't seen this issue in 64-bit Windows 8.1.

The workaround was to install the 32-bit version of python 2.7.11 on 64-bit 
Windows 10 PC's - the interpreter is completely reliable in this case and 
running 32-bit has no effect on our work.

I haven't found the exact same issue elsewhere on the python bugs forum but 
similar issues point to Windows 10 dropping some functionality which Windows 
8.1 and earlier versions had.

Setting up pseudo terminals does help but is a messy workaround.  Adding and 
removing PYTHONPATH etc from the environment variables doesn't have any effect.

Everything is working fine so this isn't really an issue.  I'm just interested 
if anyone else has experienced this and if they can shed any light onto what 
causes it.

--
components: Interpreter Core, Windows
messages: 265246
nosy: paul.moore, sam.taylor.bs, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: 64-bit Python 2.7.11 hangs in 64-bit Windows 10 - CMD and Git Bash
type: crash
versions: Python 2.7

___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26992>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Re: 64 bit python 3.5

[Mark Lawrence]

On 25/09/2015 17:55, Bill Strum wrote:

Is there a 64 bit version of 3.5 and if so where can I get it.

Thanks.

--
Bill Strum



https://www.python.org/downloads/release/python-350/

--
My fellow Pythonistas, ask not what our language can do for you, ask
what you can do for our language.

Mark Lawrence

--
https://mail.python.org/mailman/listinfo/python-list

64 bit python 3.5

[Bill Strum]

Is there a 64 bit version of 3.5 and if so where can I get it.

Thanks.

-- 
Bill Strum
-- 
https://mail.python.org/mailman/listinfo/python-list

Re: What is the difference between 32 and 64 bit Python on Windows 7 64 bit?

[Sturla Molden]

On 11/05/14 08:56, Ross Gayler wrote:


It looks to me as though 32 and 64 bit versions of Python on 64 bit
Windows are both really 32 bit Python, differing only in how they
interact with Windows.


No! Pointers are 64 bit, Python integers (on Python 2.x) are 32 bit. 
Microsoft decided to use a 32 bit long in MSVC for backwards 
compatiblity, but also because the AMD64 (x86-64) architecture was 
designed to use a 64 address with a 32 bit offset. (A 64 bit long was 
originally slightly less efficient.) You can see the value of 64 bit 
Python e.g. if you allocate a lot of objects or if you try to mmap a 
huge file. With 32 bit Python you are limited to only 2 GB of virtual 
memory. In 64 bit Python you can in practice mmap as much as you want.


The element size of what you try to index also matters. While a C long 
and a Python int is 32 bit on Windows, 64-bit Python will use a 64-bit 
offset internally (Py_ssize_t and Py_intptr_t) even on Windows. The 32 
bit Python int just limits how many objects you can index from Python 
space before Python roll over to using long instead of int. It does not 
limit the amount of memory a Python int can index. In is only when you 
index an array of bytes you will see the roll-over from Python int to 
Python long at the 2 GB limit. Typically, object will be much larger 
than one byte.


Here are two examples:

- A one-dimensional NumPy array with dtype np.float64 can keep 16 GB of 
data before a 32 bit index is too small and Python starts to use long. 
A two-dimensional NumPy array with dtype np.float64 can keep 256 GB of 
data before a 32 bit index is too small.


- A Python list stores internally an array of pointers, each of which is 
64 bit. So just indexing those goes up to 16 GB of pointer data before 
the int rolls over. Then each of these pointers point to a Python 
object. A Python float on my computer (not Windows) is 24 bytes, which I 
got from sys.getsizeof(1.) So 2**32 of those are another 383 GB. So if I 
indexed a list of Python floats on this computer, Python could handle an 
almost 400 GB data structure with a 32 bit int as indexer without 
rolling over to long.


This is obviously way beyond anything the 2 GB limit on 32 bit Python 
allows.





Sturla





--
https://mail.python.org/mailman/listinfo/python-list

Re: What is the difference between 32 and 64 bit Python on Windows 7 64 bit?

[Sturla Molden]

On 12/05/14 15:42, Sturla Molden wrote:


- A one-dimensional NumPy array with dtype np.float64 can keep 16 GB of
data before a 32 bit index is too small and Python starts to use long. A
two-dimensional NumPy array with dtype np.float64 can keep 256 GB of
data before a 32 bit index is too small.



Oops, the latter should be 34359738336 GB (that is, 32767 pentabytes) :)

Sturla





--
https://mail.python.org/mailman/listinfo/python-list

Re: What is the difference between 32 and 64 bit Python on Windows 7 64 bit?

[Sturla Molden]

On 11/05/14 08:56, Ross Gayler wrote:


Is that true?I have spent a couple of hours searching for a definitive
description of the difference between the 32 and 64 bit versions of
Python for Windows and haven't found anything.


Why do you care if a Python int object uses 32 or 64 bits internally? 
Python 2.x will automatically switch to long when needed. The size of 
the Python integer is an internal implementation detail you will not 
notice. Python knows when to use a long instead of an int. Python 3.x 
does not even have a fixed-size integer.


64 bit Python is 64 bit Python, even on Windows. The difference between 
32 bit and 64 bit Python is what you would expect: The size of a C 
pointer is 64 bits, and the virtual address space is much larger (in 
general not 2**63-1 bytes, but some OS dependent value).


Sturla



--
https://mail.python.org/mailman/listinfo/python-list

Re: What is the difference between 32 and 64 bit Python on Windows 7 64 bit?

[MRAB]

On 2014-05-13 00:41, Sturla Molden wrote:

On 12/05/14 15:42, Sturla Molden wrote:


- A one-dimensional NumPy array with dtype np.float64 can keep 16 GB of
data before a 32 bit index is too small and Python starts to use long. A
two-dimensional NumPy array with dtype np.float64 can keep 256 GB of
data before a 32 bit index is too small.



Oops, the latter should be 34359738336 GB (that is, 32767 pentabytes) :)


Double oops, Sturla, it's petabyte (well, pebibyte actually). :-)
--
https://mail.python.org/mailman/listinfo/python-list

Re: What is the difference between 32 and 64 bit Python on Windows 7 64 bit?

[Chris Angelico]

On Tue, May 13, 2014 at 10:05 AM, Sturla Molden sturla.mol...@gmail.com wrote:
 On 11/05/14 08:56, Ross Gayler wrote:

 Is that true?I have spent a couple of hours searching for a definitive
 description of the difference between the 32 and 64 bit versions of
 Python for Windows and haven't found anything.


 Why do you care if a Python int object uses 32 or 64 bits internally? Python
 2.x will automatically switch to long when needed. The size of the Python
 integer is an internal implementation detail you will not notice. Python
 knows when to use a long instead of an int. Python 3.x does not even have a
 fixed-size integer.

Sometimes you just want to confirm. :) Or maybe you want your program
to be able to detect which it's on. There are ways of doing both, but
sys.maxint isn't one of them, as it's specific to the int-long
promotion of Py2.

ChrisA
-- 
https://mail.python.org/mailman/listinfo/python-list

Re: What is the difference between 32 and 64 bit Python on Windows 7 64 bit?

[Sturla Molden]

On 13/05/14 02:09, Chris Angelico wrote:


Sometimes you just want to confirm. :) Or maybe you want your program
to be able to detect which it's on. There are ways of doing both, but
sys.maxint isn't one of them, as it's specific to the int-long
promotion of Py2.


The OPs main mistake, I guess, was to assume that sys.maxint is the 
biggest integer value Python 2.x can use.


Sturla


--
https://mail.python.org/mailman/listinfo/python-list

What is the difference between 32 and 64 bit Python on Windows 7 64 bit?

[Ross Gayler]

Hi,

I want to install Python on a PC with 16GB of RAM and the 64 bit version of
Windows 7.
I want Python to be able to use as much as possible of the RAM.

When I install the 64 bit version of Python I find that sys.maxint ==
2**31  - 1
Whereas the Pythpon installed on my 64 bit linux system returns sys.maxint
== 2**63 - 1.


It looks to me as though 32 and 64 bit versions of Python on 64 bit Windows
are both really 32 bit Python, differing only in how they interact with
Windows. So I wouldn't expect 64 bit Python running on 64 bit Windows to
allow the large data struictures I could have with 64 bit Python running on
64 bit linux.

Is that true?I have spent a couple of hours searching for a definitive
description of the difference between the 32 and 64 bit versions of Python
for Windows and haven't found anything.

Thanks

Ross
-- 
https://mail.python.org/mailman/listinfo/python-list

Re: What is the difference between 32 and 64 bit Python on Windows 7 64 bit?

[Terry Reedy]

On 5/11/2014 2:56 AM, Ross Gayler wrote:

Hi,

I want to install Python on a PC with 16GB of RAM and the 64 bit version
of Windows 7.
I want Python to be able to use as much as possible of the RAM.

When I install the 64 bit version of Python I find that sys.maxint ==
2**31  - 1


Since sys.maxint is gone in 3.x, you must be using some version of 2.x. 
Do yourself a favor and install 3.4 unless you absolutely need 2.x.


With 3.4:
 a = [None]*10
 sys.getsizeof(a)
800064
That is 10 8-byte pointers, as I expected.

--
Terry Jan Reedy

--
https://mail.python.org/mailman/listinfo/python-list

Re: What is the difference between 32 and 64 bit Python on Windows 7 64 bit?

[Benjamin Kaplan]

On Sat, May 10, 2014 at 11:56 PM, Ross Gayler r.gay...@gmail.com wrote:

 Hi,

 I want to install Python on a PC with 16GB of RAM and the 64 bit version of 
 Windows 7.
 I want Python to be able to use as much as possible of the RAM.

 When I install the 64 bit version of Python I find that sys.maxint == 2**31  
 - 1
 Whereas the Pythpon installed on my 64 bit linux system returns sys.maxint == 
 2**63 - 1.


That comes from the underlying C implementation. 64-bit MSVC still has
long int as 32-bit. You need to specify long long int to get a 64-bit
number even on a 64-bit compiler. Microsoft is a little nuts on the
backwards compatiblity.


 It looks to me as though 32 and 64 bit versions of Python on 64 bit Windows 
 are both really 32 bit Python, differing only in how they interact with 
 Windows. So I wouldn't expect 64 bit Python running on 64 bit Windows to 
 allow the large data struictures I could have with 64 bit Python running on 
 64 bit linux.

 Is that true?I have spent a couple of hours searching for a definitive 
 description of the difference between the 32 and 64 bit versions of Python 
 for Windows and haven't found anything.


long int (the size of an integer) != size_t (the size of an object).
64-bit Python still uses 64-bit pointers so it can still address more
than 4GB of memory. It just rolls over into longs after 32-bit int max
instead of after 64-bit int max.
-- 
https://mail.python.org/mailman/listinfo/python-list

Re: 64-bit Python for Solaris

[Matchek]

Crickets

2013/5/21 Maciej (Matchek) Bliziński mac...@opencsw.org:
 the ${prefix}/lib/pythonX.Y/_sysconfigdata.py file contains
 system-specific information

...and is installed in an architecture-independent directory by the
Python installer. This looks broken to me.
-- 
http://mail.python.org/mailman/listinfo/python-list

64-bit Python for Solaris

[Matchek]

Hello python-list,

I'm looking into creating a 32/64-bit Python (2.x and/or 3.x) package
for Solaris. The specificity of that package is that I need to include
both 32-bit and 64-bit binaries in it. The exact way in which the
32/64 support is done is described at [1].

There currently is a Python package that I maintain, which is 32-bit only[2].

I have made an attempt to build a 64-bit package, and my findings are
that the ${prefix}/lib/pythonX.Y/_sysconfigdata.py file contains
system-specific information. Note that it's not ${libdir}/pythonX.Y -
that would have worked, because I'm specifying different ${libdir}
directories when running the 32-bit and 64-bit builds. The Python
installer specifically uses ${prefix}/lib/pythonX.Y. For the most part
is fine, because most of files in there are not architecture-specific,
and it would be quite good to share them among the 32-bit and 64-bit
binaries at runtime. The problem is that some files differ. I've
described it some more at [3].

Ideally, I'd make _sysconfigdata.py return/set different values
depending on the Python runtime that reads it. Something like:

if we're 64-bit:
  set values for the 64-bit platform
else:
  set values for the 32-bit platform

It's a similar approach to how we currently handle C header files. See
the 'Development packages' section in [1] for more information.

The problem is that it would involve somewhat intrusive patching of
the Python source code, and in long term that means maintainability
issues.

Has this issue been seen before? Is there a better solution? Is there
something that can be done upstream to accommodate this kind of
packaging?

Maciej

[1] http://www.opencsw.org/manual/for-maintainers/32-bit-and-64-bit.html
[2] http://www.opencsw.org/packages/python/
[3] http://lists.opencsw.org/pipermail/maintainers/2013-January/017583.html
-- 
http://mail.python.org/mailman/listinfo/python-list

[issue15772] Unresolved symbols in Windows 64-bit python

[Martin v . Löwis]

Martin v. Löwis added the comment:

Closing as works-for-me then.

--
resolution:  - works for me
status: open - closed

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15772
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue15772] Unresolved symbols in Windows 64-bit python

[Silverback Networks]

Silverback Networks added the comment:

Boy, do I feel like an idiot now. An update to VC 2010 Express SP1 had 
clobbered by x64 build capabilities completely, and even reinstalling the SDK 
did nothing. It turns out that there's a specific hotfix you have to install to 
get x64 builds working again: http://support.microsoft.com/kb/2519277

When I did that and fixed up the build environment variables, Python extensions 
all built again, despite the apparently random decorating.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15772
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue15772] Unresolved symbols in Windows 64-bit python

[Silverback Networks]

Silverback Networks added the comment:

Same errors in 3.3. Some names are decorated, some aren't, seemingly at random.

For instance, python32.lib contains:

35B20 _PyObject_Dump
35B20 __imp__PyObject_Dump

and just below that,

2924A PyObject_Free
2924A __imp_PyObject_Free

But the Visual Studio 2010 compiler always looks for the underscored names for 
x64, resulting in, for instance:

  error LNK2019: unresolved external symbol __imp__PyObject_Free referenced in 
function _WRdealloc

I understand that the x64 isn't supposed to use underscore prefixes as all, but 
it is and Python partially is. I have no idea why.

The preprocessed output of including python.h, btw, is:

__declspec(dllimport) void PyObject_Free(void *);

--
nosy: +silverbacknet

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15772
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue15772] Unresolved symbols in Windows 64-bit python

[Silverback Networks]

Changes by Silverback Networks silverback...@gmail.com:


--
versions: +Python 3.3

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15772
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue15772] Unresolved symbols in Windows 64-bit python

[Saul Spatz]

New submission from Saul Spatz:

In trying to build a SWING module on Windows with 64-bit python, I get the 
linker errors listed at the bottom of this message.

I have this problem with both python 2.7 and 3.2.  I have built the project 
without problems on Windows with 32-bit python, and a correspondent informs me 
that it cam be built on linux with 64-bit python.

I have listed the exports from python32.lib with dumpbin, and in every case, 
the symbol after the __imp__ appears in the library without a leading 
underscore. For example, for the first unresolved symbol, 
__imp__PyBytes_AsStringAndSize, I find that PyBytes_AsStringAndSize appears in 
the library.  Of 1074 exports in the library, 891 do not have leading 
underscores, and the remainder do.  In the 32-bit library, every export starts 
with an underscore.   

This is obviously related to issues 15165 and 14286, but I hope this additional 
information will help locate the trouble.  I am running windows 7 professional, 
and I installed python by downloading and running the installer with all the 
defaults.

1example_wrap.obj : error LNK2019: unresolved external symbol 
__imp__PyBytes_AsStringAndSize referenced in function _SWIG_Python_str_AsChar
1example_wrap.obj : error LNK2019: unresolved external symbol 
__imp__PyUnicodeUCS2_AsUTF8String referenced in function _SWIG_Python_str_AsChar
1example_wrap.obj : error LNK2019: unresolved external symbol 
__imp__PyUnicodeUCS2_FromString referenced in function _SWIG_Python_str_FromChar
1example_wrap.obj : error LNK2001: unresolved external symbol 
__imp__PyExc_RuntimeError
1example_wrap.obj : error LNK2001: unresolved external symbol 
__imp__PyExc_AttributeError
1example_wrap.obj : error LNK2001: unresolved external symbol 
__imp__PyExc_SystemError
1example_wrap.obj : error LNK2001: unresolved external symbol 
__imp__PyExc_ValueError
1example_wrap.obj : error LNK2001: unresolved external symbol 
__imp__PyExc_SyntaxError
1example_wrap.obj : error LNK2001: unresolved external symbol 
__imp__PyExc_OverflowError
1example_wrap.obj : error LNK2001: unresolved external symbol 
__imp__PyExc_ZeroDivisionError
1example_wrap.obj : error LNK2001: unresolved external symbol 
__imp__PyExc_TypeError
1example_wrap.obj : error LNK2001: unresolved external symbol 
__imp__PyExc_IndexError
1example_wrap.obj : error LNK2001: unresolved external symbol 
__imp__PyExc_IOError
1example_wrap.obj : error LNK2001: unresolved external symbol 
__imp__PyExc_MemoryError
1example_wrap.obj : error LNK2019: unresolved external symbol 
__imp__PyInstanceMethod_New referenced in function _SWIG_PyInstanceMethod_New
1example_wrap.obj : error LNK2019: unresolved external symbol 
__imp__PyErr_SetString referenced in function _SWIG_Python_SetErrorMsg
1example_wrap.obj : error LNK2019: unresolved external symbol 
__imp__Py_BuildValue referenced in function __SWIG_Py_None
1example_wrap.obj : error LNK2019: unresolved external symbol 
__imp__PyLong_FromVoidPtr referenced in function _SwigPyObject_long
1example_wrap.obj : error LNK2019: unresolved external symbol __imp__Py_DecRef 
referenced in function _SwigPyObject_repr
1example_wrap.obj : error LNK2019: unresolved external symbol 
__imp__PyUnicodeUCS2_Concat referenced in function _SwigPyObject_repr
1example_wrap.obj : error LNK2019: unresolved external symbol 
__imp__PyUnicodeUCS2_FromFormat referenced in function _SwigPyObject_repr
1example_wrap.obj : error LNK2019: unresolved external symbol 
__imp__PyBool_FromLong referenced in function _SwigPyObject_richcompare
1example_wrap.obj : error LNK2001: unresolved external symbol 
__imp___Py_NotImplementedStruct
1example_wrap.obj : error LNK2019: unresolved external symbol 
__imp__PyObject_Free referenced in function _SwigPyObject_dealloc
1example_wrap.obj : error LNK2019: unresolved external symbol 
__imp__PyObject_CallFunctionObjArgs referenced in function _SwigPyObject_dealloc
1example_wrap.obj : error LNK2019: unresolved external symbol 
__imp__PyObject_IsTrue referenced in function _SwigPyObject_own
1example_wrap.obj : error LNK2019: unresolved external symbol 
__imp__PyArg_UnpackTuple referenced in function _SwigPyObject_own
1example_wrap.obj : error LNK2019: unresolved external symbol 
__imp__PyType_Ready referenced in function _SwigPyObject_TypeOnce
1example_wrap.obj : error LNK2019: unresolved external symbol 
__imp__PyObject_GenericGetAttr referenced in function _SwigPyObject_TypeOnce
1example_wrap.obj : error LNK2001: unresolved external symbol 
__imp__PyBaseObject_Type
1example_wrap.obj : error LNK2019: unresolved external symbol 
__imp__PyObject_SetAttr referenced in function _SWIG_Python_NewShadowInstance
1example_wrap.obj : error LNK2019: unresolved external symbol 
__imp__PyObject_Call referenced in function _SWIG_Python_NewShadowInstance
1example_wrap.obj : error LNK2019: unresolved external symbol 
__imp__PyErr_Clear referenced in function _SWIG_Python_GetModule
1example_wrap.obj : error LNK2019: unresolved external symbol

[issue15772] Unresolved symbols in Windows 64-bit python

[Brian Curtin]

Changes by Brian Curtin br...@python.org:


--
components: +Build
nosy: +brian.curtin, loewis

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15772
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Re: How to build 64-bit Python on Solaris with GCC?

[Skip Montanaro]

Karim kliateni at gmail.com writes:

 ./configure
 make
 make install

Thanks.  I have several different versions in my local sandbox.  None
are 64-bit ELFs.  Just to make sure I hadn't missed some new development
in this area, I cloned the hg repository and build the trunk version
from scratch.  I get a 32-bit executable on Solaris:

   % file ./python
   ./python: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
   dynamically linked (uses shared libs), not stripped

Skip


-- 
http://mail.python.org/mailman/listinfo/python-list

Re: How to build 64-bit Python on Solaris with GCC?

[Stefan Krah]

Skip Montanaro s...@pobox.com wrote:
 Thanks.  I have several different versions in my local sandbox.  None
 are 64-bit ELFs.  Just to make sure I hadn't missed some new development
 in this area, I cloned the hg repository and build the trunk version
 from scratch.  I get a 32-bit executable on Solaris:
 
% file ./python
./python: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
dynamically linked (uses shared libs), not stripped

./configure CFLAGS=-m64 LDFLAGS=-m64 should work with a reasonably
recent revision.


Stefan Krah


-- 
http://mail.python.org/mailman/listinfo/python-list

Re: How to build 64-bit Python on Solaris with GCC?

[Skip Montanaro]

 ./configure CFLAGS=-m64 LDFLAGS=-m64 should work with a reasonably
 recent revision.

Thanks, that did, indeed work with CPython trunk.  I eventually switched from
gcc to Sun's compiler though because I was getting link warnings.

Skip


-- 
http://mail.python.org/mailman/listinfo/python-list

Re: How to build 64-bit Python on Solaris with GCC?

[Skip Montanaro]

 Does anyone have a recipe for the subject build?

I know Solaris is a minority platform these days, but surely someone has 
tackled 
this problem, haven't they?

Thx,

Skip




-- 
http://mail.python.org/mailman/listinfo/python-list

Re: How to build 64-bit Python on Solaris with GCC?

[Karim]

Le 07/12/2011 12:30, Skip Montanaro a écrit :

Does anyone have a recipe for the subject build?

I know Solaris is a minority platform these days, but surely someone has tackled
this problem, haven't they?

Thx,

Skip





./configure
make
make install

Karim
--
http://mail.python.org/mailman/listinfo/python-list

How to build 64-bit Python on Solaris with GCC?

[Skip Montanaro]

I'd like to build a 64-bit version of Python on Solaris using gcc.  I did a
bit of Googling, but everything I came up with seemed old, inconclusive or
assumes the use of the Sun Studio compiler, with which i have no
experience.  Does anyone have a recipe for the subject build?

Thanks,

-- 
Skip Montanaro - s...@pobox.com - http://www.smontanaro.net/
-- 
http://mail.python.org/mailman/listinfo/python-list

[issue9181] Solaris extension building does not work with 64 bit python

[Charles Solar]

Charles Solar charlesso...@gmail.com added the comment:

Hello again, I got a copy of the latest python from the 2.7 branch, recompiled 
with CFLAGS=-m64 -O3 and LDFLAGS=-m64 and my extension compiled just fine.
So I can verify this bug fixed

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9181
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9181] Solaris extension building does not work with 64 bit python

[Antoine Pitrou]

Antoine Pitrou pit...@free.fr added the comment:

Thanks for checking. Closing as fixed.

--
resolution:  - fixed
status: open - closed

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9181
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9181] Solaris extension building does not work with 64 bit python

[Éric Araujo]

Éric Araujo mer...@netwok.org added the comment:

Charles, can you still reproduce your bug now that #9437 has been fixed?

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9181
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Can 32-bit and 64-bit Python coexist in the same computer?

[Andy]

Hi guys!

I got a new laptop computer which came with the 64-bit version of
Windows 7.  I installed the 64-bit versions of Python and a few other
libraries and wrote a few Python programs right there.  If I copy the
Python scripts to a 32-bit computer, it runs flawlessly.  But in the
future I may still need to distribute my compiled programs to people
who use 32-bit Windows and it seems that neither PyInstaller nor
py2exe can cross compile a 32-bit application from this 64-bit
computer.

So ugly as it sounds, I'm considering installing in parallel the 32-
bit version of Python on this same computer.  Is there anything I need
to know or a better way to achieve this instead of having a double
Python installation?

By the way, I use Python 2.6, so it would be [Python 2.6.x 32-bit] and
[Python 2.6.x 64-bit] on the same computer.

Thanks!
Andy
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Can 32-bit and 64-bit Python coexist in the same computer?

[J.O. Aho]

Andy wrote:
 Hi guys!
 
 I got a new laptop computer which came with the 64-bit version of
 Windows 7.  I installed the 64-bit versions of Python and a few other
 libraries and wrote a few Python programs right there.  If I copy the
 Python scripts to a 32-bit computer, it runs flawlessly.  But in the
 future I may still need to distribute my compiled programs to people
 who use 32-bit Windows and it seems that neither PyInstaller nor
 py2exe can cross compile a 32-bit application from this 64-bit
 computer.

A better way may be to have everything as a source package which auto
compiles during installation, then you can use an universal package.


 So ugly as it sounds, I'm considering installing in parallel the 32-
 bit version of Python on this same computer.  Is there anything I need
 to know or a better way to achieve this instead of having a double
 Python installation?

This will work, you just need to have two different paths to the installations
and of course you will need to install packages for both of them. It works
kind in the same way as you would have 2.6 and 3 installed on the same time.



-- 

  //Aho
-- 
http://mail.python.org/mailman/listinfo/python-list

[issue9181] Solaris extension building does not work with 64 bit python

[Éric Araujo]

Changes by Éric Araujo mer...@netwok.org:


--
versions: +3rd party

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9181
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9181] Solaris extension building does not work with 64 bit python

[Antoine Pitrou]

Antoine Pitrou pit...@free.fr added the comment:

Can you try using CC=cc -m64 OPT=-O3 instead?
(replace cc with the proper compiler name, of course)

--
nosy: +pitrou

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9181
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9181] Solaris extension building does not work with 64 bit python

[Charles Solar]

Charles Solar charlesso...@gmail.com added the comment:

I just recompiled using your suggested flags and it is now properly linking my 
extensions.  I guess using CFLAGS and LDFLAGS was causing the problem.
Is specifying CC the recommended way to build 64 bit python?  If so when I 
guess this issue is not really an issue at all.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9181
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9181] Solaris extension building does not work with 64 bit python

[Antoine Pitrou]

Antoine Pitrou pit...@free.fr added the comment:

 Is specifying CC the recommended way to build 64 bit python?

Currently, yes. LDFLAGS is supposed to work, but it doesn't (open bug: #9437).

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9181
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9181] Solaris extension building does not work with 64 bit python

[Éric Araujo]

Éric Araujo mer...@netwok.org added the comment:

Thank you for the report.  Do you want to work on a patch?  The usual process 
is that someone makes a patch for the active version (branch named py3k, the 
future 3.2), then the committer backports to stable versions (3.1 and 2.7) and 
forward-ports to distutils2.  See also guidelines at 
http://www.python.org/dev/patches/

--
nosy: +eric.araujo
versions: +Python 3.1, Python 3.2

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9181
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9181] Solaris extension building does not work with 64 bit python

[Charles Solar]

New submission from Charles Solar charlesso...@gmail.com:

On solaris, if you build a 64 bit python and use it to build an extension, it 
will not properly link the module.

Apparently solaris requires the -m64 flag in the linker as well as the compile 
steps.  Python distutils successfully compiles all the object files using -m64, 
but it fails to link with -m64 causing the entire build to fail if the 
extension needs a 64 bit library dependency ( will get 'incompatible library' 
errors from the linker ).

To reproduce:
build python with CFLAGS=-m64 -O3 LDFLAGS=-m64
build a C extension that depends on a 64 bit library (python setup.py install)

I assume that it would work if the C extension does not need a specific 64 bit 
library as the linker will not go and look for the wrong version of file.  So 
its a very uncommon but annoying bug.

 ld --version
GNU ld (GNU Binutils) 2.20.1.20100303
Copyright 2009 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) a later version.
This program has absolutely no warranty.

--
assignee: tarek
components: Distutils, Distutils2, Extension Modules
messages: 109396
nosy: redcomet, tarek
priority: normal
severity: normal
status: open
title: Solaris extension building does not work with 64 bit python
type: compile error
versions: Python 2.7

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9181
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7206] 64 bit python fails on Windows 7

[Rich Healey]

Rich Healey ri...@psych0tik.net added the comment:

I looked into it a bit further.

With some trial and error I narrowed the source of the problem to be the 
'KernelModeDriverInstall' option under compatibility. I believe this 
isn't a problem, because python shouldn't be trying to install drivers, 
and even if it needed to presumably that would be nested in something 
loaded dynamically, rather than the original image so it could catch the 
issue and deal with it.

I will try to reproduce this on another machine to double check my 
logic. Thanks again for all your help Martin.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7206
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7206] 64 bit python fails on Windows 7

[Rich Healey]

Rich Healey ri...@psych0tik.net added the comment:

I've done some more fiddling with the debugger, once I discovered the 
Windows symbol servers, and a tool called application verifier some 
things started to fall into place.

LuaPriv takes care of user privelidges, the program runs fine when I run 
it as administrator. I believe that disabling UAC has caused the issue.

I will attempt 2 things
a) Create a new user account on this machine to see if the issue is 
ongoing.
b) Try to fiddle more with the debugger to find the last python call in 
the stack.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7206
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7206] 64 bit python fails on Windows 7

[Rich Healey]

Rich Healey ri...@psych0tik.net added the comment:

I have an apology to make for wasting your time.

Further investigation demonstrates that it was evidently fiddling with 
the Application Verifier that broke everything (although I installed it 
during my debugging attempts- I'm guessing that something else in VS has 
the same capabilities).

By disabling all tests the application runs, by reenabling them it stops 
again.

I now have a few questions

1) How can the verifier add the flags to the loading mechanism to add 
the breaks? In that when I installed different versions/clean reinstall 
of the same version it was still broken. Clearly it doesn't patch the 
binary, but leaves a flag somewhere (???) about the binary?

2) OK by the looks of it I only had one question ;)

thanks for all your help!

--
status: open - closed

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7206
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7206] 64 bit python fails on Windows 7

[Martin v . Löwis]

Martin v. Löwis mar...@v.loewis.de added the comment:

See the section How Does AppVerifier Work? in

http://msdn.microsoft.com/en-us/library/aa480483.aspx

This doesn't answer your question fully, as it fails to explain how
precisely they hook into the app.

ISTM that they use the HKLM\Software\Microsoft\Windows
NT\CurrentVersion\Image File Execution Options registry hook. For each
executable (such as python.exe), you can specify an alternative binary
that gets launched whenever somebody is asking to launch python.exe
(IIUC, by setting the Debugger value on the registry key). In case of
appverifier, they probably then load the original binary, do their entry
point rewriting, and start the binary.

There actually *is* a second question: what is it that AppVerifier
complains about? It may be useful to run Python in AppVerifier to detect
bugs - but any outcome of this is out of scope of this report, it seems.
If you are curious to look into this further, that would be much
appreciated.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7206
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7206] 64 bit python fails on Windows 7

[Carey]

Carey carey.metca...@gmail.com added the comment:

yes, please do

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7206
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7206] 64 bit python fails on Windows 7

[Rich Healey]

Rich Healey ri...@psych0tik.net added the comment:

Download the debugging suite from
http://www.microsoft.com/whdc/devtools/debugging/install64bit.mspx#

Open windbg
Press Ctrl + E to load an executable
Select your python binary
Step through by typing g in the text box at the bottom of the Command
window.

The application will fail to crash completely as windbg will catch the
exception, however you should notice that it's spitting out duplicate
errors after a few breaks.

Paste up your log :)

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7206
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7206] 64 bit python fails on Windows 7

[Rich Healey]

Rich Healey ri...@psych0tik.net added the comment:

Carey I can send you the steps I used to create the dump if you like so we 
can check if it's the same issue?

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7206
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7206] 64 bit python fails on Windows 7

[Carey]

Carey carey.metca...@gmail.com added the comment:

I am having the exact same problem with both the AMD64 and 32 bit
installs. The python shell just will not open. For now I am running it
in the virtual XP machine but it is extremely slow and a fix would be
very helpful. I have tried uninstalling and reinstalling with no effect.
I too am willing to set up a remote desktop connection if it would help.

Windows 7 Pro RTM, Intel Core 2 Duo

--
nosy: +Carey

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7206
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7206] 64 bit python fails on Windows 7

[Martin v . Löwis]

Martin v. Löwis mar...@v.loewis.de added the comment:

By exactly the same problem, do you mean that your installation also
runs into a break instruction in ntdll!CsrSetPriorityClass+0x40? Can you
please also attach the debugger log (unless it's byte-for-byte identical
with the one from richo)?

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7206
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7206] 64 bit python fails on Windows 7

[Carey]

Carey carey.metca...@gmail.com added the comment:

i don't know how to do that. Is there an integrated debugger within
Windows 7? My program just doesn't open, it doesn't display any error
messages at all.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7206
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7206] 64 bit python fails on Windows 7

[Martin v . Löwis]

Martin v. Löwis mar...@v.loewis.de added the comment:

 i don't know how to do that. Is there an integrated debugger within
 Windows 7? My program just doesn't open, it doesn't display any error
 messages at all.

Ok. So I'm skeptical that this is the same bug (having roughly the same
symptom is not convincing). If you want it studied, please report it
separately.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7206
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7206] 64 bit python fails on Windows 7

[Martin v . Löwis]

Martin v. Löwis mar...@v.loewis.de added the comment:

 No action- the interpreter fails to start.

How precisely do you start the interpreter (and what interpreter precisely)?

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7206
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7206] 64 bit python fails on Windows 7

[Rich Healey]

Rich Healey ri...@psych0tik.net added the comment:

By running the python.exe (either by double clicking it, typing it's
path into a cmd shell or by opening it in a debugger).

I tried to create a 64 bit build of the source tree which DID start, but
the hoops I had to jump through to build it with VC++ Express Edition
were so convoluted that I'm not convinced it's meaning.

I've tried this with 2.6.3 and 3.1.1 from the amd64 .msi's at
http://www.python.org/download/

(2.6.3 was the current release when I tried. I will install 2.6.4 and
let you know- although I'm not convinced it will help).

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7206
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7206] 64 bit python fails on Windows 7

[Rich Healey]

Rich Healey ri...@psych0tik.net added the comment:

Nope- 2.6.4 fails in the same way.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7206
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7206] 64 bit python fails on Windows 7

[Martin v . Löwis]

Martin v. Löwis mar...@v.loewis.de added the comment:

FWIW, these all run fine on my copy of Windows 7.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7206
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7206] 64 bit python fails on Windows 7

[Rich Healey]

Rich Healey ri...@psych0tik.net added the comment:

They did at first for me, and then something changed.

They now don't start. I don't have the skills to properly diagnose why,
all I can get out of my debuggers is that something is happening in
ntdll.dll

Not necessarily pointing fault at Python per se, but as it's the only
application I can find this bug in, and it's present in every amd64
version of Dolphin I try this is my first port of call.

What other info can I provide to help? I can set up a remote desktop to
this machine for a developer if they would like.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7206
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7206] 64 bit python fails on Windows 7

[Rich Healey]

New submission from Rich Healey ri...@psych0tik.net:

64 bit pythons fail on 64 bit Windows 7.

The crash happens with python 2.6 and 3.1 in 64 bit mode. 3.1 was a
clean install after the issue presented itself.

I'm not 100% sure how best to help with the problem, I've attached the
dump from windows debugger, please let me know if there's anything else
I can do to help.

It used to work but I'm not sure what changed, as near as I can tell
nothing system wide did, except perhaps the installation of new
compilers, my thought is that it could alter some dll search path?

Thanks in advance

richo

--
components: Interpreter Core
files: failedPython.log
messages: 94467
nosy: richo
severity: normal
status: open
title: 64 bit python fails on Windows 7
type: crash
versions: Python 2.6, Python 3.1
Added file: http://bugs.python.org/file15197/failedPython.log

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7206
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7206] 64 bit python fails on Windows 7

[Antoine Pitrou]

Antoine Pitrou pit...@free.fr added the comment:

What is LuaPriv in that log? Something you installed?
(sorry, not a Windows specialist)

--
nosy: +pitrou

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7206
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7206] 64 bit python fails on Windows 7

[Antoine Pitrou]

Changes by Antoine Pitrou pit...@free.fr:


--
components: +Build, Windows
priority:  - critical

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7206
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7206] 64 bit python fails on Windows 7

[Rich Healey]

Rich Healey ri...@psych0tik.net added the comment:

I'm not 100% sure.

I have a x64 machine running Windows 2008. I will check if it's in the
log now.

I will also check if it's in the debug trace for x86 python (which works).

RESULTS:

I get the LuaPriv initialised line on x86 python on my win7 machine
(which works).
I don't get that line on any python builds on x64 windows server 2008.

I did some googling on what it is- it's a mechanism for restricting
access. It seems that it could be causing the crash because it thinks
the application is overflowing the stack (ie, it's a DEP related issue?).
http://msdn.microsoft.com/en-us/library/dd371695(VS.85).aspx
That is a M$ link about it.

I'm fully willing to help but don't know how, I am quite novice.

Thanks


richo

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7206
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7206] 64 bit python fails on Windows 7

[Rich Healey]

Rich Healey ri...@psych0tik.net added the comment:

I think that dump may be incorrect because it does not have all the
symbols. I will checkout source for latest 3.x trunk and attempt to
build 64 bit binaries.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7206
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7206] 64 bit python fails on Windows 7

[Martin v . Löwis]

Martin v. Löwis mar...@v.loewis.de added the comment:

What kind of action has triggered that crash?

--
nosy: +loewis

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7206
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7206] 64 bit python fails on Windows 7

[Rich Healey]

Rich Healey ri...@psych0tik.net added the comment:

No action- the interpreter fails to start.

Or do you mean what changed to make it break? I'm not sure. It used to
work but I don't believe I changed anything on my system.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7206
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

How to install 64-bit python on Ubuntu

[Curious]

Hello All,

Ubuntu comes pre-installed with Python2.6 but this python installation
is a 32 bit installation. I need to use 64-bit Python on Ubuntu - how
do I update the current installation to 64-bit installation? Is there
any separate package that I need to apt-get?

I do the following to know if the current python installation is 32-
bit or 64-bit:

Python 2.6.2 (release26-maint, Apr 19 2009, 01:56:41)
[GCC 4.3.3] on linux2
Type help, copyright, credits or license for more information.
 from struct import *
 calcsize(P) * 8
32


I expect to see the pointer size as 64 there..
If any of you could provide me any info on this matter, it would be a
great help
Thanks in advance!
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: How to install 64-bit python on Ubuntu

[Roger Binns]

Curious wrote:
 Ubuntu comes pre-installed with Python2.6 but this python installation
 is a 32 bit installation. 

For 64 bit Ubuntu you are mistaken:

$ file /usr/bin/python2.6
/usr/bin/python2.6: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked (uses shared libs), for GNU/Linux 2.6.15, stripped

 I do the following to know if the current python installation is 32-
 bit or 64-bit:

This is what I do:

 import ctypes
 ctypes.sizeof(ctypes.c_void_p)
8

Roger

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: How to install 64-bit python on Ubuntu

[Curious]

On Oct 7, 4:07 pm, Roger Binns rog...@rogerbinns.com wrote:
 Curious wrote:
  Ubuntu comes pre-installed with Python2.6 but this python installation
  is a 32 bit installation.

 For 64 bit Ubuntu you are mistaken:

 $ file /usr/bin/python2.6
 /usr/bin/python2.6: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
 dynamically linked (uses shared libs), for GNU/Linux 2.6.15, stripped

  I do the following to know if the current python installation is 32-
  bit or 64-bit:

 This is what I do:

  import ctypes
  ctypes.sizeof(ctypes.c_void_p)

 8

 Roger

Thanks very much for you response, Roger!

I am sorry but I am not able to follow what you are saying. I am quite
new to linux installation world and it's possible that I am missing
pretty straightforward info.

Did you mean to say that Ubuntu does come pre-installed with 64-bit
Python? When I used the same command as you did, I see a 32-bit
version there. I am not sure how to get to 64-bit.

$ file /usr/bin/python2.6
/usr/bin/python2.6: ELF 32-bit LSB executable, Intel 80386, version 1
(SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15,
stripped

Python 2.6.2 (release26-maint, Apr 19 2009, 01:56:41)
[GCC 4.3.3] on linux2
Type help, copyright, credits or license for more information.
 import ctypes
 ctypes.sizeof(ctypes.c_void_p)
4



I also tried building Python on this machine by setting following
configuration option:
/configure --enable-universalsdk --with-universal-archs=64-bit

But no luck. I am definitely missing something here. Could you please
explain how did you get a 64-bit version there? I am using ubuntu
9.0.4.

Thanks!

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: How to install 64-bit python on Ubuntu

[Christian Heimes]

Curious schrieb:
 On Oct 7, 4:07 pm, Roger Binns rog...@rogerbinns.com wrote:
 Curious wrote:
 Ubuntu comes pre-installed with Python2.6 but this python installation
 is a 32 bit installation.
 For 64 bit Ubuntu you are mistaken:

 $ file /usr/bin/python2.6
 /usr/bin/python2.6: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
 dynamically linked (uses shared libs), for GNU/Linux 2.6.15, stripped

 I do the following to know if the current python installation is 32-
 bit or 64-bit:
 This is what I do:

 import ctypes
 ctypes.sizeof(ctypes.c_void_p)
 8

 Roger
 
 Thanks very much for you response, Roger!
 
 I am sorry but I am not able to follow what you are saying. I am quite
 new to linux installation world and it's possible that I am missing
 pretty straightforward info.
 
 Did you mean to say that Ubuntu does come pre-installed with 64-bit
 Python? When I used the same command as you did, I see a 32-bit
 version there. I am not sure how to get to 64-bit.

I bet your Ubuntu installation is 32bit, too. You need a 64bit
installation of Ubuntu in order to run a 64bit version of Python. By
default Python is compiled in the same flavor as the OS. What does
uname -m show? It should print x86_64 for a 64bit version of Linux.

--enable-universalsdk and  --with-universal-archs have no function on
Linux. They are Mac OS X only options.

Christian

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: How to install 64-bit python on Ubuntu

[Roger Binns]

Curious wrote:
 Did you mean to say that Ubuntu does come pre-installed with 64-bit
 Python? 

I am saying that 64 bit Ubuntu comes with 64 bit Python.  (32 bit Ubuntu
comes with 32 bit Python.)

 When I used the same command as you did, I see a 32-bit
 version there.

It is most likely that you are running 32 bit Ubuntu (unless you bypassed
Ubuntu's packaging and similar stunts).  Run 'uname -a' and look near the
end.  For 64 bit you should see something like this:

$ uname -m
x86_64

If you see i686 instead of x86_64 you are on 32 bit.

 $ file /usr/bin/python2.6
 /usr/bin/python2.6: ELF 32-bit LSB executable, Intel 80386, version 1
 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15,
 stripped

That is definitely a 32 bit binary.  Try some others like /bin/ls and
/sbin/init.  (A 64 bit kernel can run 32 bit binaries but these core system
files should all match the kernel.)

 I also tried building Python on this machine by setting following
 configuration option:
 /configure --enable-universalsdk --with-universal-archs=64-bit

That is a road you don't want to go down unless you really know what you are
doing and want to bypass the packaging system.  As far as I am aware those
options only apply to Macs anyway!

 Could you please explain how did you get a 64-bit version there?

When I download Ubuntu I got the 64 bit version.  Look at the bottom of the
page:

  http://www.ubuntu.com/getubuntu/download

You may find various guides on how to convert a 32 bit installation into a
64 bit one.  Do not do any of those (if you do then mention it when asking
for help at which point people will tell you not to have done that!)  Make a
backup and do a *fresh* install.

Roger

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: How to install 64-bit python on Ubuntu

[Curious]

On Oct 7, 4:55 pm, Christian Heimes li...@cheimes.de wrote:
 Curious schrieb:



  On Oct 7, 4:07 pm, Roger Binns rog...@rogerbinns.com wrote:
  Curious wrote:
  Ubuntu comes pre-installed with Python2.6 but this python installation
  is a 32 bit installation.
  For 64 bit Ubuntu you are mistaken:

  $ file /usr/bin/python2.6
  /usr/bin/python2.6: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
  dynamically linked (uses shared libs), for GNU/Linux 2.6.15, stripped

  I do the following to know if the current python installation is 32-
  bit or 64-bit:
  This is what I do:

  import ctypes
  ctypes.sizeof(ctypes.c_void_p)
  8

  Roger

  Thanks very much for you response, Roger!

  I am sorry but I am not able to follow what you are saying. I am quite
  new to linux installation world and it's possible that I am missing
  pretty straightforward info.

  Did you mean to say that Ubuntu does come pre-installed with 64-bit
  Python? When I used the same command as you did, I see a 32-bit
  version there. I am not sure how to get to 64-bit.

 I bet your Ubuntu installation is 32bit, too. You need a 64bit
 installation of Ubuntu in order to run a 64bit version of Python. By
 default Python is compiled in the same flavor as the OS. What does
 uname -m show? It should print x86_64 for a 64bit version of Linux.

 --enable-universalsdk and  --with-universal-archs have no function on
 Linux. They are Mac OS X only options.

 Christian

Thanks for your response Christian! You are right, I have got a wrong
Ubuntu installation, installed it by mistake instead of 64-bit. After
the re-installation, I will post what Python version I find.
Thanks all!
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: How to install 64-bit python on Ubuntu

[Curious]

On Oct 7, 5:11 pm, Roger Binns rog...@rogerbinns.com wrote:
 Curious wrote:
  Did you mean to say that Ubuntu does come pre-installed with 64-bit
  Python?

 I am saying that 64 bit Ubuntu comes with 64 bit Python.  (32 bit Ubuntu
 comes with 32 bit Python.)

  When I used the same command as you did, I see a 32-bit
  version there.

 It is most likely that you are running 32 bit Ubuntu (unless you bypassed
 Ubuntu's packaging and similar stunts).  Run 'uname -a' and look near the
 end.  For 64 bit you should see something like this:

 $ uname -m
 x86_64

 If you see i686 instead of x86_64 you are on 32 bit.

  $ file /usr/bin/python2.6
  /usr/bin/python2.6: ELF 32-bit LSB executable, Intel 80386, version 1
  (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15,
  stripped

 That is definitely a 32 bit binary.  Try some others like /bin/ls and
 /sbin/init.  (A 64 bit kernel can run 32 bit binaries but these core system
 files should all match the kernel.)

  I also tried building Python on this machine by setting following
  configuration option:
  /configure --enable-universalsdk --with-universal-archs=64-bit

 That is a road you don't want to go down unless you really know what you are
 doing and want to bypass the packaging system.  As far as I am aware those
 options only apply to Macs anyway!

  Could you please explain how did you get a 64-bit version there?

 When I download Ubuntu I got the 64 bit version.  Look at the bottom of the
 page:

  http://www.ubuntu.com/getubuntu/download

 You may find various guides on how to convert a 32 bit installation into a
 64 bit one.  Do not do any of those (if you do then mention it when asking
 for help at which point people will tell you not to have done that!)  Make a
 backup and do a *fresh* install.

 Roger

Thanks Roger. Actually we have one machine at our disposal to try
different things out. We installed Linux on it just yesterday and
wanted to get Python working so there's nothing important that we fear
to loose. We'll probably do the fresh install. Will post on the forum
about how it goes and if I get 64-bit Python version.
-- 
http://mail.python.org/mailman/listinfo/python-list

Compiling 64 bit python on a mac - cannot compute sizeof (int)

[Keflavich]

I'm trying to compile a 64 bit version of python 2.6.2 on my mac (OS X
10.5.7), and am running into a problem during the configure stage.

I configure with:
./configure --enable-framework=/Library/Frameworks --enable-
universalsdk MACOSX_DEPLOYMENT_TARGET=10.5 --with-universal-archs=all -
with-readline-dir=/usr/local

because I want 64 and 32 bit, and I needed to install a 64 bit
readline as a prerequisite.

configure fails at:
checking size of int... configure: error: cannot compute sizeof (int)

I'm not reporting this as a bug because I know it's a problem with my
path somewhere (a friend with an identical computer but slightly
different setup was able to compile without a problem), but I don't
know what paths to change.  Any tips?

Thanks,
Adam
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Compiling 64 bit python on a mac - cannot compute sizeof (int)

[Mark Dickinson]

On Jul 3, 5:30 pm, Keflavich keflav...@gmail.com wrote:
 I'm trying to compile a 64 bit version of python 2.6.2 on my mac (OS X
 10.5.7), and am running into a problem during the configure stage.

 I configure with:
 ./configure --enable-framework=/Library/Frameworks --enable-
 universalsdk MACOSX_DEPLOYMENT_TARGET=10.5 --with-universal-archs=all -
 with-readline-dir=/usr/local

 because I want 64 and 32 bit, and I needed to install a 64 bit
 readline as a prerequisite.

 configure fails at:
 checking size of int... configure: error: cannot compute sizeof (int)

I confess that I don't fully understand the intricacies of the various
OS X autoconf options, but I think the problem is that the --enable-
universalsdk option takes a directory.  If that directory isn't
given, it appears to default to /Developer/SDKs/MacOSX10.4u.sdk (at
least on my OS X 10.5.7 machine), which would likely conflict with
your MACOSX_DEPLOYMENT_TARGET=10.5 setting.

Try either changing MACOSX_DEPLOYMENT_TARGET to 10.4, or using --
enable-universalsdk=/Developer/SDKs/MacOSX10.5.sdk  (or whatever the
appropriate directory is on your system).  For some reason, I think
using --enable-universalsdk=/ also works on my system.  If none of
that helps, you might try asking this question over on the pythonmac-
sig mailing list. (http://mail.python.org/mailman/listinfo/pythonmac-
sig)

Mark
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Compiling 64 bit python on a mac - cannot compute sizeof (int)

[Adam]

On Jul 3, 2:18 pm, Mark Dickinson dicki...@gmail.com wrote:
 On Jul 3, 5:30 pm, Keflavich keflav...@gmail.com wrote:

  I'm trying to compile a 64 bit version of python 2.6.2 on my mac (OS X
  10.5.7), and am running into a problem during the configure stage.

  I configure with:
  ./configure --enable-framework=/Library/Frameworks --enable-
  universalsdk MACOSX_DEPLOYMENT_TARGET=10.5 --with-universal-archs=all -
  with-readline-dir=/usr/local

  because I want 64 and 32 bit, and I needed to install a 64 bit
  readline as a prerequisite.

  configure fails at:
  checking size of int... configure: error: cannot compute sizeof (int)

 I confess that I don't fully understand the intricacies of the various
 OS X autoconf options, but I think the problem is that the --enable-
 universalsdk option takes a directory.  If that directory isn't
 given, it appears to default to /Developer/SDKs/MacOSX10.4u.sdk (at
 least on my OS X 10.5.7 machine), which would likely conflict with
 your MACOSX_DEPLOYMENT_TARGET=10.5 setting.

 Try either changing MACOSX_DEPLOYMENT_TARGET to 10.4, or using --
 enable-universalsdk=/Developer/SDKs/MacOSX10.5.sdk  (or whatever the
 appropriate directory is on your system).  For some reason, I think
 using --enable-universalsdk=/ also works on my system.  If none of
 that helps, you might try asking this question over on the pythonmac-
 sig mailing list. (http://mail.python.org/mailman/listinfo/pythonmac-
 sig)

 Mark

Thanks.  I also determined after the fact that universalsdk was the
problem, but I didn't know how to fix it.  Unfortunately, it turns out
what you identified was a transcription error on my part - I had been
using --enable-universalsdk instead of --enable-universalsdk=/.
Thanks for the help, I appreciate it!

Adam
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Problem building 64-bit python 2.6.2 on Solaris 10

[Martin v. Löwis]

 I was able to compile ctypes with gcc4sparc without many changes to
 the CFLAGS, etc.  I had another weird error, but upgrading to the
 latest gcc4sparc fixed it.  One thing I'm not clear about is how
 extensions are built.  I noticed that my CFLAGS are not being passed
 to gcc when building the extensions, so some of them are failing to
 find the correct includes  libraries.  How does one pass these flags?

The most reliable strategy is to edit Modules/Setup, and uncomment
the modules where you want to pass flags. These will then not be built
through setup.py (but become builtin by default).

Regards,
Martin
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Problem building 64-bit python 2.6.2 on Solaris 10

[John Center]

Hi Martin,

I was able to compile ctypes with gcc4sparc without many changes to
the CFLAGS, etc.  I had another weird error, but upgrading to the
latest gcc4sparc fixed it.  One thing I'm not clear about is how
extensions are built.  I noticed that my CFLAGS are not being passed
to gcc when building the extensions, so some of them are failing to
find the correct includes  libraries.  How does one pass these flags?

Thanks.

-John


-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Problem building 64-bit python 2.6.2 on Solaris 10

[John Center]

On May 29, 7:13 pm, Martin v. Löwis mar...@v.loewis.de wrote:

 Ah, too much text - I was confused by you reporting two issues in a
 single email message. That has exhausted my capacity for quick message
 scanning.

Sorry about that.  I have a tendency to over document...

 So this is a ctypes problem. You'll have to ignore it - there is
 absolutely no way that you could possibly build the ctypes module
 with Sun CC (short of rewriting ctypes to support it, of course).
 Use gcc if you need the ctypes module, or accept not having the ctypes
 module available.

I was afraid that would be the case.  I have gcc4sparc, but I usually
build with Sun Studio.  I believe gcc4sparc uses the Sun Studio
backend.  I'll try this, but do you know if I would need to do
anything different to get the ctypes code to compile?

 Unfortunately, no. It is definitely *not* Python who is searching for
 these libraries. That you had been passing them to ld during linkage
 doesn't help at all. Linking succeeds just fine; Python then tries
 to load the the _ssl module, which in turn causes the *dynamic* linker
 (ld.so.1) to search for the shared library; it doesn't find it and
 therefore gives up loading _ssl.so.

Ok, so it looks like the only option here is to use LD_LIBRARY_PATH.

Thanks, Martin.

-John
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Problem building 64-bit python 2.6.2 on Solaris 10

[Martin v. Löwis]

 Ok, so it looks like the only option here is to use LD_LIBRARY_PATH.

Not really: there is also crle, and LD_RUN_PATH.

Regards,
Martin
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Problem building 64-bit python 2.6.2 on Solaris 10

[John Center]

On May 28, 6:03 pm, Martin v. Löwis mar...@v.loewis.de wrote:
  I think the problem is it should be built with v9.S for 64-bit, not
  v8.S.  Is that correct?  If so, how do I get it to use the right one?

 The Solaris dynamic loader can't find it. Set LD_LIBRARY_PATH or
 LD_RUN_PATH appropriately, or use crle(8).

 Regards,
 Martin

Hi Martin,

I'm not sure I understand.  It appears that cc is compiling the wrong
module, v8.S.  It should be compiling v9.S.  The errors are being
reported by fbe, the Sun Studio assembler, not ld.  I think there must
be a place to specify which I want to use, but I don't understand the
python build environment well enough to know where to do it.

You may be right about the first error.  It's being reported by ld,
but -L/opt/openssl/lib/sparcv9  -R/opt/openssl/lib/sparcv9 are being
passed to cc.  It is able to find -lssl  -lcrypto, but I think python
itself doesn't use the openssl libraries.  Since I see the chain
ld.so.1: python: fatal: libssl.so.0.9.8: open failed: No such file or
directory, which I think means python itself doesn't know where they
are at.  I checked python  libpython.so with ldd  neither uses
libssl.so.  It seems to me there should be another way to tell python
where to find it to build the module.  Does this make sense?

Thanks for your help.

-John
-- 
http://mail.python.org/mailman/listinfo/python-list

Problem building 64-bit python 2.6.2 on Solaris 10

[John Center]

Hi,

I'm trying to build python 2.6.2 on Solaris 10 (SPARC 64), using Sun
Studio 12, but I'm having a few problems getting a clean build.  The
python configure options are:

with_gcc=no
with_universal_archs=64-bit
with_cxx_main=CC -m64

The first problem I'm having is _ssl.so not building:

cc -m64 -xcode=pic32 -DNDEBUG -g -xs -xtarget=ultraT1 -xarch=sparcvis2
-m64 -mt
-xcode=pic32 -xmemalign=8s -xpagesize=default -I. -I/opt/ws/dists/
Python-2.6.2/.
/Include -I. -IInclude -I./Include -I/opt/db/include -I/opt/tcl8/
include -I/opt/
openssl/include -I/opt/gnu/include -I/opt/local/include -I/usr/sfw/
include -I/usr/include -I/usr/local/include -I/opt/ws/dists/
Python-2.6.2/Include -I/opt/ws/dists/Python-2.6.2 -c /opt/ws/dists/
Python-2.6.2/Modules/_ssl.c -o build/temp.solaris-2.10-sun4v-2.6/opt/
ws/dists/Python-2.6.2/Modules/_ssl.o
/opt/ws/dists/Python-2.6.2/Modules/_ssl.c, line 1119: warning:
statement not reached
cc -m64 -G build/temp.solaris-2.10-sun4v-2.6/opt/ws/dists/Python-2.6.2/
Modules/_ssl.o -L/opt/openssl/lib/sparcv9 -L/opt/db/lib/sparcv9 -L/opt/
gnu/lib/sparcv9 -L
/opt/local/lib/sparcv9 -L/usr/sfw/lib/sparcv9 -L/usr/lib/sparcv9 -L/
usr/local/lib -L. -R/opt/db/lib/sparcv9 -R/opt/gnu/lib/sparcv9 -R/opt/
local/lib/sparcv9 -R/usr/sfw/lib/sparcv9 -R/usr/lib/sparcv9 -lssl -
lcrypto -lpython2.6 -o build/lib.so
laris-2.10-sun4v-2.6/_ssl.so

*** WARNING: renaming _ssl since importing it failed: ld.so.1:
python: fatal: libssl.so.0.9.8: open failed: No such file or directory

I have the openssl include  64-bit libraries in the paths shown
above, so why this doesn't work?  What am I missing?


My next problem is building the ctypes module:

cc -m64 -xcode=pic32 -DNDEBUG -g -xs -xtarget=ultraT1 -xarch=sparcvis2
-m64 -mt
-xcode=pic32 -xmemalign=8s -xpagesize=default -I. -I/opt/ws/dists/
Python-2.6.2/.
/Include -Ibuild/temp.solaris-2.10-sun4v-2.6/libffi/include -Ibuild/
temp.solaris
-2.10-sun4v-2.6/libffi -I/opt/ws/dists/Python-2.6.2/Modules/_ctypes/
libffi/src -
I. -IInclude -I./Include -I/opt/db/include -I/opt/tcl8/include -I/opt/
openssl/include -I/opt/gnu/include -I/opt/local/include -I/usr/sfw/
include -I/usr/include
-I/usr/local/include -I/opt/ws/dists/Python-2.6.2/Include -I/opt/ws/
dists/Python
-2.6.2 -c /opt/ws/dists/Python-2.6.2/Modules/_ctypes/libffi/src/sparc/
v8.S -o build/temp.solaris-2.10-sun4v-2.6/opt/ws/dists/Python-2.6.2/
Modules/_ctypes/libffi
/src/sparc/v8.o

/opt/ws/tools/SUNWspro/prod/bin/fbe: /opt/ws/tmp/dists/cpp0AAA.
19506.DfaqgM, l
ine 438: error: detect global register use not covered .register
pseudo-op
/opt/ws/tools/SUNWspro/prod/bin/fbe: /opt/ws/tmp/dists/cpp0AAA.
19506.DfaqgM, l
ine 456: error: detect global register use not covered .register
pseudo-op
cc: assembler failed for /opt/ws/dists/Python-2.6.2/Modules/_ctypes/
libffi/src/s
parc/v8.S

I think the problem is it should be built with v9.S for 64-bit, not
v8.S.  Is that correct?  If so, how do I get it to use the right one?

Any help would be greatly appreciated.

-John
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Problem building 64-bit python 2.6.2 on Solaris 10

[Martin v. Löwis]

 I think the problem is it should be built with v9.S for 64-bit, not
 v8.S.  Is that correct?  If so, how do I get it to use the right one?

The Solaris dynamic loader can't find it. Set LD_LIBRARY_PATH or
LD_RUN_PATH appropriately, or use crle(8).

Regards,
Martin
-- 
http://mail.python.org/mailman/listinfo/python-list

Determining 32 bit vs 64 bit Python and numpy

[mmanns]

Hi

I am looking for a robust, cross-platform way to determine if I am on a
32 bit or a 64 bit Python and if the numpy installation is also 32 bit
or 64 bit.

I have googled a bit and found some platform specific solutions but
nothing general.

The solution should work with different versions of Python (= 2.4).

Thanks in advance

Martin
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Determining 32 bit vs 64 bit Python and numpy

[Martin v. Löwis]

 I am looking for a robust, cross-platform way to determine if I am on a
 32 bit or a 64 bit Python and if the numpy installation is also 32 bit
 or 64 bit.

You can find out the size of a pointer with struct.calcsize(P) * 8.
Numpy will have the same configuration if you can import it.

Regards,
Martin
-- 
http://mail.python.org/mailman/listinfo/python-list

Re: Determining 32 bit vs 64 bit Python and numpy

[mmanns]

On Mon, 25 May 2009 23:54:45 +0200
Martin v. Löwis mar...@v.loewis.de wrote:

  I am looking for a robust, cross-platform way to determine if I am
  on a 32 bit or a 64 bit Python and if the numpy installation is
  also 32 bit or 64 bit.
 
 You can find out the size of a pointer with struct.calcsize(P) * 8.
 Numpy will have the same configuration if you can import it.


That works great. Thank you.

Best Regards

Martin

-- 
http://mail.python.org/mailman/listinfo/python-list

[issue2652] 64 bit python memory leak usage

[Antoine Pitrou]

Antoine Pitrou pit...@free.fr added the comment:

Closing since no further information was given about the workload.

--
nosy: +pitrou
resolution:  - invalid
status: open - closed

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2652
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Is there any way for a program to choose between 32 bit or 64-bit python dynamically?

[srinivasan srinivas]

Hi,
Is thera any way for a program to choose between 32-bit or 64-bit dynamically?

Thanks,
Srini


  Add more friends to your messenger and enjoy! Go to 
http://messenger.yahoo.com/invite/
--
http://mail.python.org/mailman/listinfo/python-list

Re: Is there any way for a program to choose between 32 bit or 64-bit python dynamically?

[Chris Rebert]

On Fri, Mar 20, 2009 at 6:28 AM, srinivasan srinivas
sri_anna...@yahoo.co.in wrote:

 Hi,
 Is thera any way for a program to choose between 32-bit or 64-bit dynamically?

Doubt it, since it's set in stone from when your CPython interpreter
got compiled.
There may be some workaround to use 32bit libs from a 64-bit program
though, but I'm not at all sure.

Cheers,
Chris

-- 
I have a blog:
http://blog.rebertia.com
--
http://mail.python.org/mailman/listinfo/python-list

what does 64-bit python mean?

[srinivasan srinivas]

Hi,
Could someone help me in understanding what 64-bit python means?

tahnks,
Srini


  Add more friends to your messenger and enjoy! Go to 
http://messenger.yahoo.com/invite/
--
http://mail.python.org/mailman/listinfo/python-list