Re: Compiling python on windows with vs

On 6/15/23, Thomas Schweikle via Python-list wrote: > > No. This flag is not inherited. Someone has to set it for created > directories. It is easy to confirm: take a directory not under MSYS or > cygwin control (because it is mounted by MSYS or cygwin), set the flag, > then create directories. Th

Re: Compiling python on windows with vs

Am Do., 15.Juni.2023 um 16:28:21 schrieb Eryk Sun: On 6/15/23, Thomas Schweikle via Python-list wrote: In this case: not sure what is going on. Possibly you have a setting configured that affects the behavior of Git via the MinGW-w64 runtime, such that calling mkdir() ends up calling NtSet

Re: Compiling python on windows with vs

Am Do., 15.Juni.2023 um 15:44:42 schrieb Inada Naoki: Then, git doesn't enable Windows NTFS case sensitivity. You enabled NTFS case sensitivity on "C:\Users\user\K". And Windows enabled case sensitivity for all new directories under the directory. No. This flag is not inherited. Someone has t

Re: Compiling python on windows with vs

On 6/15/23, Thomas Schweikle via Python-list wrote: > > In this case: not sure what is going on. Possibly you have a setting configured that affects the behavior of Git via the MinGW-w64 runtime, such that calling mkdir() ends up calling NtSetInformationFile() to set the FileCaseSensitiveInformat

Re: Compiling python on windows with vs

Then, git doesn't enable Windows NTFS case sensitivity. You enabled NTFS case sensitivity on "C:\Users\user\K". And Windows enabled case sensitivity for all new directories under the directory. Since it is not default and minor setting, it is not a bug that current Python doesn't support building

Re: Compiling python on windows with vs

Am Mi., 14.Juni.2023 um 15:10:50 schrieb Eryk Sun: On 6/14/23, Inada Naoki via Python-list wrote: Since Git enables Windows NTFS case sensitivity while checking out sources I didn't know that. Would you give us a link to this feature? As far as I know, `git config core.ignorecase` doesn't m

Re: Compiling python on windows with vs

On 6/14/23, Inada Naoki via Python-list wrote: >> Since Git enables Windows NTFS case sensitivity while checking out sources > > I didn't know that. Would you give us a link to this feature? > As far as I know, `git config core.ignorecase` doesn't mean NTFS case > sensitive. If a repo is cloned i

Re: Compiling python on windows with vs

> Since Git enables Windows NTFS case sensitivity while checking out sources I didn't know that. Would you give us a link to this feature? As far as I know, `git config core.ignorecase` doesn't mean NTFS case sensitive. On Wed, Jun 14, 2023 at 1:57 AM Thomas Schweikle via Python-list < python-lis

Re: Compiling python on windows with vs

Am Di., 13.Juni.2023 um 20:36:17 schrieb Mats Wichmann via Python-list: On 6/13/23 12:12, Thomas Schweikle via Python-list wrote: Am Di., 13.Juni.2023 um 19:20:38 schrieb Jim Schwartz: What version of visual studio are you using? Visual Studio 2022, aka 17.6.2. What version of python?

Re: Compiling python on windows with vs

On 6/13/23, Thomas Schweikle via Python-list wrote: > > Since Git enables Windows NTFS case sensitivity while checking out > sources ... is it a bug or a "feature"? And: is there a simple AFAIK the Windows version of Git (you're not using the Linux version of Git via WSL, right?) does not automat

RE: Compiling python on windows with vs

Sent: Tuesday, June 13, 2023 1:12 PM To: Python Cc: Thomas Schweikle Subject: Re: Compiling python on windows with vs Am Di., 13.Juni.2023 um 19:20:38 schrieb Jim Schwartz: > What version of visual studio are you using? Visual Studio 2022, aka 17.6.2. > What version of python? python 3.10.1

Re: Compiling python on windows with vs

On 6/13/23 12:12, Thomas Schweikle via Python-list wrote: Am Di., 13.Juni.2023 um 19:20:38 schrieb Jim Schwartz: What version of visual studio are you using? Visual Studio 2022, aka 17.6.2. What version of python? python 3.10.11 or 3.11.4 I’ve had success with using the cython package i

Re: Compiling python on windows with vs

Am Di., 13.Juni.2023 um 19:20:38 schrieb Jim Schwartz: What version of visual studio are you using? Visual Studio 2022, aka 17.6.2. What version of python? python 3.10.11 or 3.11.4 I’ve had success with using the cython package in python and cl from visual studio, but I haven’t tried v

Re: Compiling python on windows with vs

What version of visual studio are you using? What version of python? I’ve had success with using the cython package in python and cl from visual studio, but I haven’t tried visual studio alone. Sent from my iPhone > On Jun 13, 2023, at 11:59 AM, Thomas Schweikle via Python-list > wrote: >

Re: Compiling and Linking pre-built Windows Python libraries with C++ files on Linux for Windows

Am 19.03.22 um 01:08 schrieb Ankit Agarwal: This is a very specific question. I am trying to figure out whether or not I can use pre-built python libraries and headers on Windows in a MinGW build on Linux. With the mingw cross-compiler on Linux that should be possible, however I guess it might

Re: Compiling and Linking pre-built Windows Python libraries with C++ files on Linux for Windows

On 3/18/22, Ankit Agarwal wrote: > Hi, > > This is a very specific question. I am trying to figure out whether or not > I can use pre-built python libraries and headers on Windows in a MinGW > build on Linux. Essentially I have some python and C++ code which interface > via cython and pybind. I wa

Re: Compiling and Linking pre-built Windows Python libraries with C++ files on Linux for Windows

On Fri, Mar 18, 2022 at 8:03 PM Ankit Agarwal wrote: > Hi, > > This is a very specific question. I am trying to figure out whether or not > I can use pre-built python libraries and headers on Windows in a MinGW > build on Linux. Essentially I have some python and C++ code which interface > via cy

Re: compiling 3.7.0 from source with custom libffi path

Hi, I dont have "lib64" in libffi, are you sure it is "lib64" or just "lib"? On Monday, 1 July 2019 21:32:46 UTC+9, tom...@gmail.com wrote: > On Monday, September 24, 2018 at 11:48:59 AM UTC+3, Fetchinson . wrote: > > I'm trying to compile python 3.7.0 from source with a custom libffi > > path an

Re: compiling 3.7.0 from source with custom libffi path

On Monday, September 24, 2018 at 11:48:59 AM UTC+3, Fetchinson . wrote: > I'm trying to compile python 3.7.0 from source with a custom libffi > path and the compiler/linker doesn't seem to pick up the right > version. The system libffi doesn't have the development files so I've > installed the late

Re: compiling 3.7.0 from source with custom libffi path

Exactly same issue.. ctypes wont build .. pkg-config finds libffi, headers are located in configure and still INFO: Could not locate ffi libs and/or headers python is getting really annoying to install .. not everyone has root privileges to install system-wide dependencies. On Tuesday, Septe

Re: compiling 3.7.0 from source with custom libffi path

On 9/24/18, Thomas Jollans wrote: > On 2018-09-24 16:30, Fetchinson . via Python-list wrote: >> [fetch@fetch]$ grep LIBFFI_INCLUDE Makefile >> LIBFFI_INCLUDEDIR= /opt/custom/lib/libffi-3.2.1/include >> >> So I'd say everything should work but it doesn't, I reran ./configure >> and also make o

Re: compiling 3.7.0 from source with custom libffi path

On 2018-09-24 16:30, Fetchinson . via Python-list wrote: > [fetch@fetch]$ grep LIBFFI_INCLUDE Makefile > LIBFFI_INCLUDEDIR= /opt/custom/lib/libffi-3.2.1/include > > So I'd say everything should work but it doesn't, I reran ./configure > and also make of course. I'm confused. ./configure succ

Re: compiling 3.7.0 from source with custom libffi path

On 9/24/18, Thomas Jollans wrote: > On 2018-09-24 14:14, Fetchinson . via Python-list wrote: I'm trying to compile python 3.7.0 from source with a custom libffi path and the compiler/linker doesn't seem to pick up the right version. The system libffi doesn't have the development fil

Re: compiling 3.7.0 from source with custom libffi path

On 2018-09-24 14:14, Fetchinson . via Python-list wrote: >>> I'm trying to compile python 3.7.0 from source with a custom libffi >>> path and the compiler/linker doesn't seem to pick up the right >>> version. The system libffi doesn't have the development files so I've >>> installed the latest libf

Re: compiling 3.7.0 from source with custom libffi path

>> I'm trying to compile python 3.7.0 from source with a custom libffi >> path and the compiler/linker doesn't seem to pick up the right >> version. The system libffi doesn't have the development files so I've >> installed the latest libffi (also from source) to /opt/custom but >> still I get >> >>

Re: compiling 3.7.0 from source with custom libffi path

On 2018-09-24 10:48, Fetchinson . via Python-list wrote: > I'm trying to compile python 3.7.0 from source with a custom libffi > path and the compiler/linker doesn't seem to pick up the right > version. The system libffi doesn't have the development files so I've > installed the latest libffi (also

Re: Compiling Python 3.6.1 on macOS 10.12.5

On 7/10/17, Nigel Palmer wrote: > Hi > > I am trying to compile Python 3.6.1 on macOS 10.12.5 with xcode 8.8.3 using > the instructions at > https://docs.python.org/devguide/setup.html#build-dependencies but I am > getting the error > > ./python.exe -E -S -m sysconfig --generate-posix-vars ;\ >

RE: Compiling Python 3.6.1 on macOS 10.12.5

@python.org Subject: Re: Compiling Python 3.6.1 on macOS 10.12.5 > Killed: 9 It looks like not segmentation fault. Maybe, RAM shortage? INADA Naoki On Mon, Jul 10, 2017 at 10:24 PM, Nigel Palmer wrote: > Hi > > I am trying to compile Python 3.6.1 on macOS 10.12.5 with xcode 8.8.3

Re: Compiling Python 3.6.1 on macOS 10.12.5

>Why are you trying to compile Python manually? You should use Homebrew to >install Python in 99% of cases. (The package is python3) I'm not the person you answered, but I can explain why I do things that are not "optimal" or "easy" or "best". I am interested, I want to learn something, I think

RE: Compiling Python 3.6.1 on macOS 10.12.5

From: Chris Warrick [mailto:kwpol...@gmail.com] Sent: 11 July 2017 07:48 To: Nigel Palmer Cc: python-list@python.org Subject: Re: Compiling Python 3.6.1 on macOS 10.12.5 Why are you trying to compile Python manually? You should use Homebrew to install Python in 99% of cases. (The package is

Re: Compiling Python 3.6.1 on macOS 10.12.5

>Why are you trying to compile Python manually? You should use Homebrew to >install Python in 99% of cases. (The package is python3) I'm not the person you answered, but I can explain why I do things that are not "optimal" or "easy" or "best". I am interested, I want to learn something, I think

Re: Compiling Python 3.6.1 on macOS 10.12.5

>Why are you trying to compile Python manually? You should use Homebrew to >install Python in 99% of cases. (The package is python3) I'm not the person you answered, but I can explain why I do things that are not "optimal" or "easy" or "best". I am interested, I want to learn something, I think

Re: Compiling Python 3.6.1 on macOS 10.12.5

Why are you trying to compile Python manually? You should use Homebrew to install Python in 99% of cases. (The package is python3) -- Chris Warrick -- https://mail.python.org/mailman/listinfo/python-list

Re: Compiling Python 3.6.1 on macOS 10.12.5

> Killed: 9 It looks like not segmentation fault. Maybe, RAM shortage? INADA Naoki On Mon, Jul 10, 2017 at 10:24 PM, Nigel Palmer wrote: > Hi > > I am trying to compile Python 3.6.1 on macOS 10.12.5 with xcode 8.8.3 using > the instructions at > https://docs.python.org/devguide/setup.html

Re: Compiling new Pythons on old Windows compilers

On 03/12/2017 09:26 PM, Michael Torrie wrote: > On 03/12/2017 02:45 PM, eryk sun wrote: >> On Sun, Mar 12, 2017 at 5:02 PM, Eric Frederich >> wrote: >>> Any idea why compatibility was dropped recently? There used to be a PC >>> directory with different VS directories in the source tree, now it is

Re: Compiling new Pythons on old Windows compilers

On 03/12/2017 02:45 PM, eryk sun wrote: > On Sun, Mar 12, 2017 at 5:02 PM, Eric Frederich > wrote: >> Any idea why compatibility was dropped recently? There used to be a PC >> directory with different VS directories in the source tree, now it isn't >> there any more. > > CPython 3.5+ uses the Un

Re: Compiling new Pythons on old Windows compilers

On Sun, Mar 12, 2017 at 5:02 PM, Eric Frederich wrote: > Any idea why compatibility was dropped recently? There used to be a PC > directory with different VS directories in the source tree, now it isn't > there any more. CPython 3.5+ uses the Universal CRT on Windows, which is a system component

Re: Compiling extensions on Python 2.7, Windows 10 64 bit

Hi, On Friday, 29 April 2016, Igor Korot wrote: > Andrea, > > On Fri, Apr 29, 2016 at 4:27 PM, Andrea Gavana > wrote: > > Hi, > > > > > > On Friday, 29 April 2016, Igor Korot > > wrote: > >> > >> Andrea, > >> > >> On Fri, Apr 29, 2016 at 3:45 PM, > wrote: > >> > Dear list, > >> > > >> > I

Re: Compiling extensions on Python 2.7, Windows 10 64 bit

Hi, On Friday, 29 April 2016, Igor Korot wrote: > Andrea, > > On Fri, Apr 29, 2016 at 3:45 PM, > > wrote: > > Dear list, > > > > I have been trying to compile wxPython Phoenix ( > https://github.com/wxWidgets/Phoenix) from source on Windows 10 64 bit, > Python 2.7 64 bit, using the very han

Re: Compiling extensions on Python 2.7, Windows 10 64 bit

Andrea, On Fri, Apr 29, 2016 at 4:27 PM, Andrea Gavana wrote: > Hi, > > > On Friday, 29 April 2016, Igor Korot wrote: >> >> Andrea, >> >> On Fri, Apr 29, 2016 at 3:45 PM, wrote: >> > Dear list, >> > >> > I have been trying to compile wxPython Phoenix >> > (https://github.com/wxWidgets/Phoe

Re: Compiling extensions on Python 2.7, Windows 10 64 bit

Andrea, On Fri, Apr 29, 2016 at 3:45 PM, wrote: > Dear list, > > I have been trying to compile wxPython Phoenix > (https://github.com/wxWidgets/Phoenix) from source on Windows 10 64 bit, > Python 2.7 64 bit, using the very handy Microsoft Visual C++ Compiler for > Python 2.7 (https://www.

Re: compiling matplotlib in virtual env

I ran into the same issue. Check here http://stackoverflow.com/questions/27024731/matplotlib-compilation-error-typeerror-unorderable-types-str-int It worked for me on python 3 with virtualenv in ubuntu . Libfreetype was missing. Le 2 oct. 2015 10:43, "Laura Creighton" a écrit : > Lots of egg pro

Re: compiling matplotlib in virtual env

Lots of egg problems can be fixed if you pip install this package first. https://pypi.python.org/pypi/ez_setup However, you are trying to install matplotlib. Your distro should have it already as a package (python-matplotlib perhaps? python3-matplotlib perhaps?) and you may want to get it from t

Re: compiling matplotlib in virtual env

> I been trying to compile matplotlib in a python3.4 virtual env using > pip version 1.7 on Fedora 22. I am in about 3 weeks learning python > and Django so I am not clear on the error response to: > ... > File "/usr/lib64/python3.4/distutils/version.py", line 343, in _cmp > if self

Re: Compiling multiple python scripts into an exe file

On Tue, Jan 13, 2015 at 10:53 PM, dieter wrote: > no nein writes: > >> Basically, is it possible to compile multiple unrelated python scripts into >> a single exe file, so when execute it several python programs are run at >> once. > > These are two distinct problems: > > * for doing things

Re: Compiling multiple python scripts into an exe file

no nein writes: > Basically, is it possible to compile multiple unrelated python scripts into a > single exe file, so when execute it several python programs are run at once. These are two distinct problems: * for doing things in paralell, look at "threading" or "multiprocessing" * for g

RE: Compiling Error prompt

Hi all, when ever I execute the code always on the output prompts this error "C:\Python33\lib\importlib\_bootstrap.py:1532: UserWarning: Module six was already imported from C:\Python33\lib\site-packages\six.py, but c:\python33\lib\site-packages\six-1.6.1-py3.3.egg is being added to sys.path l

Re: Compiling main script into .pyc

On 2014-01-17, Steven D'Aprano wrote: > On Thu, 16 Jan 2014 23:43:02 -0500, Dave Angel wrote: > [steve@ando ~]$ cat sample.py > print("Hello!") > > [steve@ando ~]$ ls sample.pyc > ls: sample.pyc: No such file or directory > [steve@ando ~]$ python -m compileall sample.py > Compiling sample.py ...

Re: Compiling main script into .pyc

On Thu, 16 Jan 2014 17:01:51 -0800, Sam wrote: > One thing I observe about python byte-code compiling is that the main > script does not gets compiled into .pyc. Only imported modules are > compiled into .pyc. > > May I know how can I compile the main script into .pyc? It is to > inconvenience po

Re: Compiling main script into .pyc

On Thu, 16 Jan 2014 23:43:02 -0500, Dave Angel wrote: > MRAB Wrote in message: >> On 2014-01-17 02:56, bob gailer wrote: >>> On 1/16/2014 8:01 PM, Sam wrote: One thing I observe about python byte-code compiling is that the main script does not gets compiled into .pyc. Only imported modu

Re: Compiling main script into .pyc

On 1/16/2014 10:19 PM, MRAB wrote: On 2014-01-17 02:56, bob gailer wrote: On 1/16/2014 8:01 PM, Sam wrote: One thing I observe about python byte-code compiling is that the main script does not gets compiled into .pyc. Only imported modules are compiled into .pyc. May I know how can I compile t

Re: Compiling main script into .pyc

MRAB Wrote in message: > On 2014-01-17 02:56, bob gailer wrote: >> On 1/16/2014 8:01 PM, Sam wrote: >>> One thing I observe about python byte-code compiling is that the main >>> script does not gets compiled into .pyc. Only imported modules are compiled >>> into .pyc. >>> >>> May I know how can

Re: Compiling main script into .pyc

On 2014-01-17 02:56, bob gailer wrote: On 1/16/2014 8:01 PM, Sam wrote: One thing I observe about python byte-code compiling is that the main script does not gets compiled into .pyc. Only imported modules are compiled into .pyc. May I know how can I compile the main script into .pyc? Duh? Jus

Re: Compiling main script into .pyc

On 1/16/14 8:01 PM, Sam wrote: One thing I observe about python byte-code compiling is that the main script does not gets compiled into .pyc. Only imported modules are compiled into .pyc. May I know how can I compile the main script into .pyc? It is to inconvenience potential copy-cats. The

Re: Compiling main script into .pyc

On 1/16/2014 8:01 PM, Sam wrote: One thing I observe about python byte-code compiling is that the main script does not gets compiled into .pyc. Only imported modules are compiled into .pyc. May I know how can I compile the main script into .pyc? Duh? Just import it! -- https://mail.python.org/

Re: Compiling Python3 for BeagleBone Black (Angstrom distro)

Use this http://hg.python.org/cpython/file/92022b45e60b/setup.py#l36 Add the list of modules you want to disable and redo make 2013/11/5 Travis Griggs > > On Nov 4, 2013, at 9:22 AM, Travis Griggs wrote: > > > I'm playing with a BeagleBone Black running the angstrom distro. Of > course, stock

Re: Compiling Python 3.3.2 on CentOS 6.4 - unable to find compiled OpenSSL?

Am 05.11.2013 01:23, schrieb Victor Hooi: > Hi, > > We have a machine running CentOS 6.4, and we're attempting to compile Python > 3.3.2 on it: > > # cat /etc/redhat-release > CentOS release 6.4 (Final) > > We've compiled openssl 1.0.1e 11 by hand on this box, and installed it into

Re: Compiling Python3 for BeagleBone Black (Angstrom distro)

On 11/4/2013 7:23 PM, Travis Griggs wrote: On Nov 4, 2013, at 9:22 AM, Travis Griggs wrote: I'm playing with a BeagleBone Black running the angstrom distro. Of course, stock python is 2.7, I'd rather use python3. There isn't a python3 package available for angstrom. So I downloaded the sour

RE: Compiling Python 3.3.2 on CentOS 6.4 - unable to find compiled OpenSSL?

> Any thoughts on what we're doing wrong? Building them yourself:) Try iuscommunity.org for prebuilt packages... -- https://mail.python.org/mailman/listinfo/python-list

Re: Compiling Python3 for BeagleBone Black (Angstrom distro)

On Nov 4, 2013, at 9:22 AM, Travis Griggs wrote: > I'm playing with a BeagleBone Black running the angstrom distro. Of course, > stock python is 2.7, I'd rather use python3. There isn't a python3 package > available for angstrom. So I downloaded the source and compiled. It seemed to > work pr

Re: Compiling Python3 for BeagleBone Black (Angstrom distro)

Hi Travis, I see, looking at ./configure --help | less, that I could provide > --disable-FEATURE and --without-PACKAGE directives to my ./configure > invocation. But what I don't see is how to generate a list of what > FEATURES/PACKAGES I could put there for consideration of omission. Is there > s

Re: Compiling vs interpreting [was Re: A certainl part of an if() structure never gets executed.]

On Mon, Jun 17, 2013 at 6:02 AM, Steven D'Aprano wrote: > On Sun, 16 Jun 2013 12:31:59 -0700, Mark Janssen wrote: >>> The line between compilers >>> and interpreters is quite fuzzy. >> >> It shouldn't be. > > Of course it should be, because that reflects reality. It's fuzzy AND it seldom even mat

Re: Compiling vs interpreting [was Re: A certainl part of an if() structure never gets executed.]

On Sun, 16 Jun 2013 12:31:59 -0700, Mark Janssen wrote: Whats the difference of "interpreting " to "compiling" ? >>> >>> OK, I give up! >> >> Actually, that's a more subtle question than most people think. Python, >> for example, is a compiled language. (What did you think the "c" in >> ".pyc

Re: Compiling vs interpreting [was Re: A certainl part of an if() structure never gets executed.]

>>> Whats the difference of "interpreting " to "compiling" ? >> >> OK, I give up! > > Actually, that's a more subtle question than most people think. Python, > for example, is a compiled language. (What did you think the "c" in > ".pyc" files stood for? and the compile() function>?) Careful there.

Re: Compiling native extensions with Visual Studio 2012?

On Saturday, January 12, 2013 2:45:38 AM UTC-5, Alec Taylor wrote: > There have been various threads for MSVC 2010[1][2], but the most > > recent thing I found for MSVC 2012 was [3]… from 6 months ago. > > > > Basically I want to be able to compile bcrypt—and yes I should be > > using Keccak—x

Re: Compiling native extensions with Visual Studio 2012?

Am 12.01.2013 17:06, schrieb Alec Taylor: > Would be awesome to get these built into stdlib. > > Compiling my own versions mostly for virtualenv purposes; though > sometimes I can't find the binary on: > http://www.lfd.uci.edu/~gohlke/pythonlibs/ Let's see. I've 10 months to work on the PEP + imp

Re: Compiling native extensions with Visual Studio 2012?

On Sun, Jan 13, 2013 at 1:34 AM, Christian Heimes wrote: > Am 12.01.2013 08:45, schrieb Alec Taylor: >> There have been various threads for MSVC 2010[1][2], but the most >> recent thing I found for MSVC 2012 was [3]… from 6 months ago. >> >> Basically I want to be able to compile bcrypt—and yes I

Re: Compiling native extensions with Visual Studio 2012?

Am 12.01.2013 08:45, schrieb Alec Taylor: > There have been various threads for MSVC 2010[1][2], but the most > recent thing I found for MSVC 2012 was [3]… from 6 months ago. > > Basically I want to be able to compile bcrypt—and yes I should be > using Keccak—x64 binaries on Windows x64. > > Ther

Re: Compiling native extensions with Visual Studio 2012?

Okay, got all extensions I require to compile successfully with MSVC 2012. Trick was using this fork: https://github.com/wcdolphin/py-bcrypt (See their issue log for traceback) =] On Sat, Jan 12, 2013 at 6:45 PM, Alec Taylor wrote: > There have been various threads for MSVC 2010[1][2], but the

Re: Compiling extension module (linker error)

On 2012-10-23 08:00, Paul Volkov wrote: 2012/10/22 MRAB : By the way, the recommendation is for module names to be lowercase with underscores, so "fund_rose" instead of "FundRose". Try this code: I tried as you suggested, but the linker error (unresolved external) is still there. I found a

Re: Compiling extension module (linker error)

2012/10/22 MRAB : > By the way, the recommendation is for module names to be lowercase with > underscores, so "fund_rose" instead of "FundRose". > > Try this code: > I tried as you suggested, but the linker error (unresolved external) is still there. I'm sure python33.lib is properly added because

Re: Compiling extension module (linker error)

On 2012-10-22 11:55, Paul Volkov wrote: I am trying to compile an extension module with C++ Builder 6 for Python 3.3. I converted python33.lib using coff2omf.exe and added this library into my project. I wonder why I get this error message while building: [Linker Error] Unresolved external '_PyM

Re: Compiling debug Python 2.7 on Windows

On 23/05/2012 2:42 AM, Иван Громов wrote: Hi, I'm trying to compile a debug version of Python 2.7 on Windows, but I've encountered some problems while creating a distribution.\ When I run PCbuild\python.exe setup.py bdist_wininst I get an error error: pyconfig.h: No such file or directory As far

Re: Compiling Python (modules) on 64bit Windows - which compiler suite?

> > See "Compiling 64-bit extension modules on Windows" at > . It applies to > non-Cython extensions as well. > > MinGW-w64 also works, but you'll have to generate and use libpythonXX.a and > libmsvcr90.a link libraries. > > Christoph Th

Re: Compiling Python (modules) on 64bit Windows - which compiler suite?

Thomas Bach, 21.03.2012 20:03: > Ralph Heinkel writes: >> when processing our mass spectrometry data we are running against the >> 2GB memory limit on our 32 bit machines. So we are planning to move to >> 64bit. Downloading and installing the 64bit version of Python for >> Windows is trivial, but h

Re: Compiling Python (modules) on 64bit Windows - which compiler suite?

On Wednesday, March 21, 2012 8:06:47 AM UTC-7, Ralph Heinkel wrote: > Hi, > > when processing our mass spectrometry data we are running against the > 2GB memory limit on our 32 bit machines. So we are planning to move to > 64bit. Downloading and installing the 64bit version of Python for > Windows

Re: Compiling Python (modules) on 64bit Windows - which compiler suite?

Hi, Ralph Heinkel writes: > Hi, > > when processing our mass spectrometry data we are running against the > 2GB memory limit on our 32 bit machines. So we are planning to move to > 64bit. Downloading and installing the 64bit version of Python for > Windows is trivial, but how do we compile our o

Re: Compiling Python (modules) on 64bit Windows - which compiler suite?

On 3/21/2012 11:06 AM, Ralph Heinkel wrote: when processing our mass spectrometry data we are running against the 2GB memory limit on our 32 bit machines. So we are planning to move to 64bit. Downloading and installing the 64bit version of Python for Windows is trivial, but how do we compile our

Re: compiling qt app extensions with distutils

On 22/07/11 21:37, strattonbrazil wrote: >> Okay, your terminology was confused: you want to extend Python, not your >> application. > > Sorry, after I sent that e-mail, I realized I had already mixed up the > terms, where I should have written "embedding". > >> First of all, you don't technicall

Re: compiling qt app extensions with distutils

> > I have a simple Qt app that renders a scene in OpenGL does some very > > basic geometry routines.  I originally was planning extending my app > > just by including Python.h and the corresponding lib possibly using > > pythonqt, but every time I brought it up on the python mailing list, > > many

Re: compiling qt app extensions with distutils

On 22/07/11 18:22, strattonbrazil wrote: > I have a simple Qt app that renders a scene in OpenGL does some very > basic geometry routines. I originally was planning extending my app > just by including Python.h and the corresponding lib possibly using > pythonqt, but every time I brought it up on

Re: compiling qt app extensions with distutils

I have a simple Qt app that renders a scene in OpenGL does some very basic geometry routines. I originally was planning extending my app just by including Python.h and the corresponding lib possibly using pythonqt, but every time I brought it up on the python mailing list, many would say I should

Re: compiling qt app extensions with distutils

On 22/07/11 15:43, strattonbrazil wrote: > I'd like to extend my C++ Qt applicaition using distutils. Looking > over the tutorial docs (http://docs.python.org/extending/ > building.html#building), it seems fairly intuitive for simple > examples, but I'm already using a rather complex qmake/Makefil

Re: Compiling Python 3.2 on Cygwin fails

On Mon, Jul 4, 2011 at 3:49 PM, Aly Tawfik wrote: > On Jun 20, 12:44 pm, sewpafly wrote: >> I was able to a little further by changing 2 lines in Makefile.pre.in. >> >> On line 170, changed: >>     DLLLIBRARY= @DLLLIBRARY@ >> to: >>     DLLLIBRARY= libpython$(VERSION).dll >> >> On line 509 it had

Re: Compiling Python 3.2 on Cygwin fails

On Jun 20, 12:44 pm, sewpafly wrote: > I was able to a little further by changing 2 lines in Makefile.pre.in. > > On line 170, changed: >     DLLLIBRARY= @DLLLIBRARY@ > to: >     DLLLIBRARY= libpython$(VERSION).dll > > On line 509 it had: >     $(DLLLIBRARY) libpython$(VERSION).dll.a: $(LIBRARY_OB

Re: Compiling Python 3.2 on Cygwin fails

On Jun 20, 12:44 pm, sewpafly wrote: > I was able to a little further by changing 2 lines in Makefile.pre.in. > > On line 170, changed: >     DLLLIBRARY= @DLLLIBRARY@ > to: >     DLLLIBRARY= libpython$(VERSION).dll > > On line 509 it had: >     $(DLLLIBRARY) libpython$(VERSION).dll.a: $(LIBRARY_OB

Re: Compiling Python 3.2 on Cygwin fails

I was able to a little further by changing 2 lines in Makefile.pre.in. On line 170, changed: DLLLIBRARY= @DLLLIBRARY@ to: DLLLIBRARY= libpython$(VERSION).dll On line 509 it had: $(DLLLIBRARY) libpython$(VERSION).dll.a: $(LIBRARY_OBJS) which I changed to: $(DLLLIBRARY) libpython$(

Re: Compiling python without ssl?

On 4/1/2011 7:36 AM, Austin Bingham wrote: Is there any way to compile python (3.1.3, in case it matters) without ssl support? OpenSSL is on my system, and configure finds it, Can you temporarily disguise (rename) it? -- Terry Jan Reedy -- http://mail.python.org/mailman/listinfo/python-list

Re: Compiling python without ssl?

[Austin Bingham] Is there any way to compile python (3.1.3, in case it matters) without ssl support? OpenSSL is on my system, and configure finds it, but I can't find a way to tell configure to explicitly ignore it. I need a version of python without ssl for trade compliance reasons (I don't ma

Re: compiling Python 2.7.1 with readline module fails on Debian (Virtualbox)

On 24/12/2010 2:16, Benedict Verheyen wrote: > On 23/12/2010 20:55, Stefan Sonnenberg-Carstens wrote: >>> I finally succeeded. I built ncurses and installed it to $HOME/usr/local ./configure --with-shared --enable-termcap --prefix=$HOME/usr/local make make install Then i built readline ./configu

Re: compiling Python 2.7.1 with readline module fails on Debian (Virtualbox)

On 23/12/2010 20:55, Stefan Sonnenberg-Carstens wrote: >> >> > OK, I compiled it successfully under Debian 5.07 i386. > ncurses and libreadline are compiled from hand, both --prefix=$HOME/usr/local. > For python the only extra needed was export > LD_LIBRARY_PATH=$HOME/usr/local/lib:$LD_LIBRARY_PA

Re: compiling Python 2.7.1 with readline module fails on Debian (Virtualbox)

Am 23.12.2010 15:37, schrieb Benedict Verheyen: On 23/12/2010 14:09, Benedict Verheyen wrote: I started from scratch. I tried to build readline 6 and 5, and installing the packages system wide as opposed to $HOME/local, but everytime Python fails to find it. On stable, apt-get build-dep python

Re: compiling Python 2.7.1 with readline module fails on Debian (Virtualbox)

Am 23.12.2010 15:37, schrieb Benedict Verheyen: On 23/12/2010 14:09, Benedict Verheyen wrote: I started from scratch. I tried to build readline 6 and 5, and installing the packages system wide as opposed to $HOME/local, but everytime Python fails to find it. On stable, apt-get build-dep python

Re: compiling Python 2.7.1 with readline module fails on Debian (Virtualbox)

On 23/12/2010 14:09, Benedict Verheyen wrote: > > I started from scratch. > I tried to build readline 6 and 5, and installing the packages system wide > as opposed to $HOME/local, but everytime Python fails to find it. > > On stable, apt-get build-dep python 2.6 doesn't work, but > apt-get build

Re: compiling Python 2.7.1 with readline module fails on Debian (Virtualbox)

On 23/12/2010 11:00, Stefan Sonnenberg-Carstens wrote: > apt-get build-dep python 2.6 > should do, the dependencies haven't changed (IMHO). > Then wipe away $HOME/usr/local (if you can, btw), > reset all env vars to default (perhaps reboot). > Then untar python from scratch, cd into that dir, and

Re: compiling Python 2.7.1 with readline module fails on Debian (Virtualbox)

Am 23.12.2010 10:04, schrieb Benedict Verheyen: On 22/12/2010 18:47, Stefan Sonnenberg-Carstens wrote: Am 22.12.2010 09:33, schrieb Benedict Verheyen: Did you try apt-get install build-essential apt-get build-dep python2.7 before trying to compile ? Anyway, the config.log file is always of

Re: compiling Python 2.7.1 with readline module fails on Debian (Virtualbox)

On 22/12/2010 18:47, Stefan Sonnenberg-Carstens wrote: > Am 22.12.2010 09:33, schrieb Benedict Verheyen: >> > Did you try > > apt-get install build-essential > apt-get build-dep python2.7 > > before trying to compile ? > > Anyway, the config.log file is always of special interest. > Btw, which

Re: compiling Python 2.7.1 with readline module fails on Debian (Virtualbox)

On 22/12/2010 18:57, Jim Pharis wrote: > are you running make clean for good measure? Yes, i am. I am gong to try and uninstall Python2.7 from $HOME/local and see if that makes a difference. Maybe it interferes with the build process? Regards, Benedict -- http://mail.python.org/mailman/listinf

Re: compiling Python 2.7.1 with readline module fails on Debian (Virtualbox)

are you running make clean for good measure? On Wed, Dec 22, 2010 at 3:33 AM, Benedict Verheyen < benedict.verhe...@gmail.com> wrote: > Hi, > > > i'm trying to compile Python 2.7.1 on Debian (Virtual Box). > Compiling end successfully but readline and curses fail to build. > > I'm working with vi

Re: compiling Python 2.7.1 with readline module fails on Debian (Virtualbox)

Am 22.12.2010 09:33, schrieb Benedict Verheyen: Hi, i'm trying to compile Python 2.7.1 on Debian (Virtual Box). Compiling end successfully but readline and curses fail to build. I'm working with virtualenv and I install all my packages in $HOME/local. I've downloaded readline, compiled and ins

  1   2   3   4   >