Quantlib 1.14 and Quantlib1.14-SWIG: versions of Visual C++ prior to VC++10 (2010) are no longer supported
0
I downloaded tarbals for both quantlib 1.14 and quantlib 1.14-swig. The quantlib folder under SWIG does contain the quantlib_wrap.cpp. But the setup complains the the MSC version. Here is the new error. This post is associated with another post on missing quantlib_wrap.cpp error message.
C:UsersPublic3rdPartyLibrariesQuantLib-1.14ql/config.msvc.hpp(29) : fatal error C1189: #error : "versions of Visual C++ prior to VC++10 (2010) are no longer supported"
error: command 'C:\Users\U435169\AppData\Local\Programs\Common\Microsoft\Visual C++ for Python\9.0\VC\Bin\cl.exe' failed with exit status 2.
Use 1.13. VC9 is no longer supported. – Luigi Ballabio
I will try 1.13 also. But actually, I do have VC++ 14.0 installed. I am using VS2015 to compile the quantlib. Not sure the true reason.
I did try the 1.13 and run into linking error. I think it might be from the inconsistency between the compile of quantlib-swig (VC9.0) and quantlib(VC14). If that is the case, how do we control the compiling version of quantlib-swig? Is there an option to control that?
C:UsersU435169AppDataLocalProgramsCommonMicrosoftVisual C++ for Python9.0VCBincl.exe /c /nologo /Ox /MD /W3 /GS- /DNDEBUG -D__WIN32__ -DWIN32 -DNDEBUG -D_WINDOWS -DNOMINMAX -ID:packagesPython27include -ID:packagesPython27PC -IC:UsersPublic3rdPartyLibrariesQuantLib-1.13 -IC:UsersPublicMSYS2mingw32include /TpQuantLib/quantlib_wrap.cpp /Fobuildtemp.win32-2.7ReleaseQuantLib/quantlib_wrap.obj /GR /FD /Zm250 /EHsc /bigobj /MD
quantlib_wrap.cpp
C:UsersU435169AppDataLocalProgramsCommonMicrosoftVisual C++ for Python9.0VCBinlink.exe /DLL /nologo /INCREMENTAL:NO /LIBPATH:D:packagesPython27libs /LIBPATH:D:packagesPython27PCbuild /LIBPATH:D:packagesPython27PCVS9.0 /LIBPATH:C:UsersPublic3rdPartyLibrariesQuantLib-1.13lib /EXPORT:init_QuantLib buildtemp.win32-2.7ReleaseQuantLib/quantlib_wrap.obj /OUT:buildlib.win32-2.7QuantLib_QuantLib.pyd /IMPLIB:buildtemp.win32-2.7ReleaseQuantLib_QuantLib.lib /MANIFESTFILE:buildtemp.win32-2.7ReleaseQuantLib_QuantLib.pyd.manifest /subsystem:windows /machine:x86
LINK : fatal error LNK1104: cannot open file 'QuantLib-vc90-mt.lib'
error: command 'C:\Users\U435169\AppData\Local\Programs\Common\Microsoft\Visual C++ for Python\9.0\VC\Bin\link.exe' failed with exit status 1104
python c++ quantlib quantlib-swig
asked Nov 20 at 20:21
MagicFatto
12
add a comment |
0
I downloaded tarbals for both quantlib 1.14 and quantlib 1.14-swig. The quantlib folder under SWIG does contain the quantlib_wrap.cpp. But the setup complains the the MSC version. Here is the new error. This post is associated with another post on missing quantlib_wrap.cpp error message.
C:UsersPublic3rdPartyLibrariesQuantLib-1.14ql/config.msvc.hpp(29) : fatal error C1189: #error : "versions of Visual C++ prior to VC++10 (2010) are no longer supported"
error: command 'C:\Users\U435169\AppData\Local\Programs\Common\Microsoft\Visual C++ for Python\9.0\VC\Bin\cl.exe' failed with exit status 2.
Use 1.13. VC9 is no longer supported. – Luigi Ballabio
I will try 1.13 also. But actually, I do have VC++ 14.0 installed. I am using VS2015 to compile the quantlib. Not sure the true reason.
I did try the 1.13 and run into linking error. I think it might be from the inconsistency between the compile of quantlib-swig (VC9.0) and quantlib(VC14). If that is the case, how do we control the compiling version of quantlib-swig? Is there an option to control that?
C:UsersU435169AppDataLocalProgramsCommonMicrosoftVisual C++ for Python9.0VCBincl.exe /c /nologo /Ox /MD /W3 /GS- /DNDEBUG -D__WIN32__ -DWIN32 -DNDEBUG -D_WINDOWS -DNOMINMAX -ID:packagesPython27include -ID:packagesPython27PC -IC:UsersPublic3rdPartyLibrariesQuantLib-1.13 -IC:UsersPublicMSYS2mingw32include /TpQuantLib/quantlib_wrap.cpp /Fobuildtemp.win32-2.7ReleaseQuantLib/quantlib_wrap.obj /GR /FD /Zm250 /EHsc /bigobj /MD
quantlib_wrap.cpp
C:UsersU435169AppDataLocalProgramsCommonMicrosoftVisual C++ for Python9.0VCBinlink.exe /DLL /nologo /INCREMENTAL:NO /LIBPATH:D:packagesPython27libs /LIBPATH:D:packagesPython27PCbuild /LIBPATH:D:packagesPython27PCVS9.0 /LIBPATH:C:UsersPublic3rdPartyLibrariesQuantLib-1.13lib /EXPORT:init_QuantLib buildtemp.win32-2.7ReleaseQuantLib/quantlib_wrap.obj /OUT:buildlib.win32-2.7QuantLib_QuantLib.pyd /IMPLIB:buildtemp.win32-2.7ReleaseQuantLib_QuantLib.lib /MANIFESTFILE:buildtemp.win32-2.7ReleaseQuantLib_QuantLib.pyd.manifest /subsystem:windows /machine:x86
LINK : fatal error LNK1104: cannot open file 'QuantLib-vc90-mt.lib'
error: command 'C:\Users\U435169\AppData\Local\Programs\Common\Microsoft\Visual C++ for Python\9.0\VC\Bin\link.exe' failed with exit status 1104
python c++ quantlib quantlib-swig
asked Nov 20 at 20:21
MagicFatto
12
What is the question? What version of MSVC are your using?
– NathanOliver
Nov 20 at 20:26
Welcome to Stack Overflow! Please take the tour and in particular read How to Ask. It's very unclear what your question is or what you expect from a solution. After all, the error message is pretty clear.
– Ulrich Eckhardt
Nov 20 at 20:33
Wasn't finishing the question and browser was terminated unexpected. Re-edit it for clarity.
– MagicFatto
Nov 20 at 20:46
add a comment |
0
0
0
0
I downloaded tarbals for both quantlib 1.14 and quantlib 1.14-swig. The quantlib folder under SWIG does contain the quantlib_wrap.cpp. But the setup complains the the MSC version. Here is the new error. This post is associated with another post on missing quantlib_wrap.cpp error message.
C:UsersPublic3rdPartyLibrariesQuantLib-1.14ql/config.msvc.hpp(29) : fatal error C1189: #error : "versions of Visual C++ prior to VC++10 (2010) are no longer supported"
error: command 'C:\Users\U435169\AppData\Local\Programs\Common\Microsoft\Visual C++ for Python\9.0\VC\Bin\cl.exe' failed with exit status 2.
Use 1.13. VC9 is no longer supported. – Luigi Ballabio
I will try 1.13 also. But actually, I do have VC++ 14.0 installed. I am using VS2015 to compile the quantlib. Not sure the true reason.
I did try the 1.13 and run into linking error. I think it might be from the inconsistency between the compile of quantlib-swig (VC9.0) and quantlib(VC14). If that is the case, how do we control the compiling version of quantlib-swig? Is there an option to control that?
C:UsersU435169AppDataLocalProgramsCommonMicrosoftVisual C++ for Python9.0VCBincl.exe /c /nologo /Ox /MD /W3 /GS- /DNDEBUG -D__WIN32__ -DWIN32 -DNDEBUG -D_WINDOWS -DNOMINMAX -ID:packagesPython27include -ID:packagesPython27PC -IC:UsersPublic3rdPartyLibrariesQuantLib-1.13 -IC:UsersPublicMSYS2mingw32include /TpQuantLib/quantlib_wrap.cpp /Fobuildtemp.win32-2.7ReleaseQuantLib/quantlib_wrap.obj /GR /FD /Zm250 /EHsc /bigobj /MD
quantlib_wrap.cpp
C:UsersU435169AppDataLocalProgramsCommonMicrosoftVisual C++ for Python9.0VCBinlink.exe /DLL /nologo /INCREMENTAL:NO /LIBPATH:D:packagesPython27libs /LIBPATH:D:packagesPython27PCbuild /LIBPATH:D:packagesPython27PCVS9.0 /LIBPATH:C:UsersPublic3rdPartyLibrariesQuantLib-1.13lib /EXPORT:init_QuantLib buildtemp.win32-2.7ReleaseQuantLib/quantlib_wrap.obj /OUT:buildlib.win32-2.7QuantLib_QuantLib.pyd /IMPLIB:buildtemp.win32-2.7ReleaseQuantLib_QuantLib.lib /MANIFESTFILE:buildtemp.win32-2.7ReleaseQuantLib_QuantLib.pyd.manifest /subsystem:windows /machine:x86
LINK : fatal error LNK1104: cannot open file 'QuantLib-vc90-mt.lib'
error: command 'C:\Users\U435169\AppData\Local\Programs\Common\Microsoft\Visual C++ for Python\9.0\VC\Bin\link.exe' failed with exit status 1104
python c++ quantlib quantlib-swig
asked Nov 20 at 20:21
MagicFatto
12
I downloaded tarbals for both quantlib 1.14 and quantlib 1.14-swig. The quantlib folder under SWIG does contain the quantlib_wrap.cpp. But the setup complains the the MSC version. Here is the new error. This post is associated with another post on missing quantlib_wrap.cpp error message.
C:UsersPublic3rdPartyLibrariesQuantLib-1.14ql/config.msvc.hpp(29) : fatal error C1189: #error : "versions of Visual C++ prior to VC++10 (2010) are no longer supported"
error: command 'C:\Users\U435169\AppData\Local\Programs\Common\Microsoft\Visual C++ for Python\9.0\VC\Bin\cl.exe' failed with exit status 2.
Use 1.13. VC9 is no longer supported. – Luigi Ballabio
I will try 1.13 also. But actually, I do have VC++ 14.0 installed. I am using VS2015 to compile the quantlib. Not sure the true reason.
I did try the 1.13 and run into linking error. I think it might be from the inconsistency between the compile of quantlib-swig (VC9.0) and quantlib(VC14). If that is the case, how do we control the compiling version of quantlib-swig? Is there an option to control that?
C:UsersU435169AppDataLocalProgramsCommonMicrosoftVisual C++ for Python9.0VCBincl.exe /c /nologo /Ox /MD /W3 /GS- /DNDEBUG -D__WIN32__ -DWIN32 -DNDEBUG -D_WINDOWS -DNOMINMAX -ID:packagesPython27include -ID:packagesPython27PC -IC:UsersPublic3rdPartyLibrariesQuantLib-1.13 -IC:UsersPublicMSYS2mingw32include /TpQuantLib/quantlib_wrap.cpp /Fobuildtemp.win32-2.7ReleaseQuantLib/quantlib_wrap.obj /GR /FD /Zm250 /EHsc /bigobj /MD
quantlib_wrap.cpp
C:UsersU435169AppDataLocalProgramsCommonMicrosoftVisual C++ for Python9.0VCBinlink.exe /DLL /nologo /INCREMENTAL:NO /LIBPATH:D:packagesPython27libs /LIBPATH:D:packagesPython27PCbuild /LIBPATH:D:packagesPython27PCVS9.0 /LIBPATH:C:UsersPublic3rdPartyLibrariesQuantLib-1.13lib /EXPORT:init_QuantLib buildtemp.win32-2.7ReleaseQuantLib/quantlib_wrap.obj /OUT:buildlib.win32-2.7QuantLib_QuantLib.pyd /IMPLIB:buildtemp.win32-2.7ReleaseQuantLib_QuantLib.lib /MANIFESTFILE:buildtemp.win32-2.7ReleaseQuantLib_QuantLib.pyd.manifest /subsystem:windows /machine:x86
LINK : fatal error LNK1104: cannot open file 'QuantLib-vc90-mt.lib'
error: command 'C:\Users\U435169\AppData\Local\Programs\Common\Microsoft\Visual C++ for Python\9.0\VC\Bin\link.exe' failed with exit status 1104
python c++ quantlib quantlib-swig
python c++ quantlib quantlib-swig
asked Nov 20 at 20:21
MagicFatto
12
asked Nov 20 at 20:21
MagicFatto
12
edited Nov 20 at 22:34
asked Nov 20 at 20:21
MagicFatto
12
asked Nov 20 at 20:21
MagicFatto
12
asked Nov 20 at 20:21
MagicFatto
12
12
What is the question? What version of MSVC are your using?
– NathanOliver
Nov 20 at 20:26
Welcome to Stack Overflow! Please take the tour and in particular read How to Ask. It's very unclear what your question is or what you expect from a solution. After all, the error message is pretty clear.
– Ulrich Eckhardt
Nov 20 at 20:33
Wasn't finishing the question and browser was terminated unexpected. Re-edit it for clarity.
– MagicFatto
Nov 20 at 20:46
add a comment |
What is the question? What version of MSVC are your using?
– NathanOliver
Nov 20 at 20:26
Welcome to Stack Overflow! Please take the tour and in particular read How to Ask. It's very unclear what your question is or what you expect from a solution. After all, the error message is pretty clear.
– Ulrich Eckhardt
Nov 20 at 20:33
Wasn't finishing the question and browser was terminated unexpected. Re-edit it for clarity.
– MagicFatto
Nov 20 at 20:46
What is the question? What version of MSVC are your using?
– NathanOliver
Nov 20 at 20:26
What is the question? What version of MSVC are your using?
– NathanOliver
Nov 20 at 20:26
Welcome to Stack Overflow! Please take the tour and in particular read How to Ask. It's very unclear what your question is or what you expect from a solution. After all, the error message is pretty clear.
– Ulrich Eckhardt
Nov 20 at 20:33
Welcome to Stack Overflow! Please take the tour and in particular read How to Ask. It's very unclear what your question is or what you expect from a solution. After all, the error message is pretty clear.
– Ulrich Eckhardt
Nov 20 at 20:33
Wasn't finishing the question and browser was terminated unexpected. Re-edit it for clarity.
– MagicFatto
Nov 20 at 20:46
Wasn't finishing the question and browser was terminated unexpected. Re-edit it for clarity.
– MagicFatto
Nov 20 at 20:46
add a comment |
1 Answer
1
active
oldest
votes
0
I'm guessing you're compiling the module for Python 2.7?
Python 2.7 for Windows is compiled with VC++ 2008 and uses it for compiling external modules as well. If you can switch to Python 3.5 or later instead, it will use your VC++ 2015 installation.
answered Nov 20 at 22:42
Luigi Ballabio
2,7331323
You are right! When try 3.6.1, ran into indentation error. I saw similar problems posted 10 month ago and you suggested him writing email to the related developers. Not sure how his problem was resolved. (C:ProgramDataAnaconda3) C:UsersPublic3rdPartyLibrariesQuantLib-SWIG-1.14Python>python setup.py build File "setup.py", line 2 Copyright (C) 2000, 2001, 2002, 2003 RiskMap srl ^ IndentationError: unexpected indent
– MagicFatto
Nov 21 at 1:24
By the way, Python 2.7.3 doesn't have this issue and I have never modified thesetup.py. The first three lines are:# -*- coding: iso-8859-1 -*- """ Copyright (C) 2000, 2001, 2002, 2003 RiskMap srl
– MagicFatto
Nov 21 at 1:40
It seems that Python doesn't recognize the second line (it reports line 3 as line 2). Please try adding a blank line between line 1 and 2.
– Luigi Ballabio
Nov 21 at 13:41
And anyway: did you try runningpip install QuantLib-Pythonas I suggested in your other question, instead of compiling?
– Luigi Ballabio
Nov 21 at 13:43
Thanks Luigi for staying with me all this time!!! I did trypip install QuantLib-Pythonand it didn't work out. If that worked, it would make life easier :). Once I inserted one blank line between the original first line and second line in thesetup.py, the problem went away. The build went well and finished generating code!!! Didn't expect this to be this hard but lucky to have your guidance.
– MagicFatto
Nov 21 at 14:17
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53400935%2fquantlib-1-14-and-quantlib1-14-swig-versions-of-visual-c-prior-to-vc10-201%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
0
I'm guessing you're compiling the module for Python 2.7?
Python 2.7 for Windows is compiled with VC++ 2008 and uses it for compiling external modules as well. If you can switch to Python 3.5 or later instead, it will use your VC++ 2015 installation.
answered Nov 20 at 22:42
Luigi Ballabio
2,7331323
You are right! When try 3.6.1, ran into indentation error. I saw similar problems posted 10 month ago and you suggested him writing email to the related developers. Not sure how his problem was resolved. (C:ProgramDataAnaconda3) C:UsersPublic3rdPartyLibrariesQuantLib-SWIG-1.14Python>python setup.py build File "setup.py", line 2 Copyright (C) 2000, 2001, 2002, 2003 RiskMap srl ^ IndentationError: unexpected indent
– MagicFatto
Nov 21 at 1:24
By the way, Python 2.7.3 doesn't have this issue and I have never modified thesetup.py. The first three lines are:# -*- coding: iso-8859-1 -*- """ Copyright (C) 2000, 2001, 2002, 2003 RiskMap srl
– MagicFatto
Nov 21 at 1:40
It seems that Python doesn't recognize the second line (it reports line 3 as line 2). Please try adding a blank line between line 1 and 2.
– Luigi Ballabio
Nov 21 at 13:41
And anyway: did you try runningpip install QuantLib-Pythonas I suggested in your other question, instead of compiling?
– Luigi Ballabio
Nov 21 at 13:43
Thanks Luigi for staying with me all this time!!! I did trypip install QuantLib-Pythonand it didn't work out. If that worked, it would make life easier :). Once I inserted one blank line between the original first line and second line in thesetup.py, the problem went away. The build went well and finished generating code!!! Didn't expect this to be this hard but lucky to have your guidance.
– MagicFatto
Nov 21 at 14:17
add a comment |
0
I'm guessing you're compiling the module for Python 2.7?
Python 2.7 for Windows is compiled with VC++ 2008 and uses it for compiling external modules as well. If you can switch to Python 3.5 or later instead, it will use your VC++ 2015 installation.
answered Nov 20 at 22:42
Luigi Ballabio
2,7331323
You are right! When try 3.6.1, ran into indentation error. I saw similar problems posted 10 month ago and you suggested him writing email to the related developers. Not sure how his problem was resolved. (C:ProgramDataAnaconda3) C:UsersPublic3rdPartyLibrariesQuantLib-SWIG-1.14Python>python setup.py build File "setup.py", line 2 Copyright (C) 2000, 2001, 2002, 2003 RiskMap srl ^ IndentationError: unexpected indent
– MagicFatto
Nov 21 at 1:24
By the way, Python 2.7.3 doesn't have this issue and I have never modified thesetup.py. The first three lines are:# -*- coding: iso-8859-1 -*- """ Copyright (C) 2000, 2001, 2002, 2003 RiskMap srl
– MagicFatto
Nov 21 at 1:40
It seems that Python doesn't recognize the second line (it reports line 3 as line 2). Please try adding a blank line between line 1 and 2.
– Luigi Ballabio
Nov 21 at 13:41
And anyway: did you try runningpip install QuantLib-Pythonas I suggested in your other question, instead of compiling?
– Luigi Ballabio
Nov 21 at 13:43
Thanks Luigi for staying with me all this time!!! I did trypip install QuantLib-Pythonand it didn't work out. If that worked, it would make life easier :). Once I inserted one blank line between the original first line and second line in thesetup.py, the problem went away. The build went well and finished generating code!!! Didn't expect this to be this hard but lucky to have your guidance.
– MagicFatto
Nov 21 at 14:17
add a comment |
0
0
0
I'm guessing you're compiling the module for Python 2.7?
Python 2.7 for Windows is compiled with VC++ 2008 and uses it for compiling external modules as well. If you can switch to Python 3.5 or later instead, it will use your VC++ 2015 installation.
answered Nov 20 at 22:42
Luigi Ballabio
2,7331323
I'm guessing you're compiling the module for Python 2.7?
Python 2.7 for Windows is compiled with VC++ 2008 and uses it for compiling external modules as well. If you can switch to Python 3.5 or later instead, it will use your VC++ 2015 installation.
answered Nov 20 at 22:42
Luigi Ballabio
2,7331323
answered Nov 20 at 22:42
Luigi Ballabio
2,7331323
answered Nov 20 at 22:42
Luigi Ballabio
2,7331323
answered Nov 20 at 22:42
Luigi Ballabio
2,7331323
2,7331323
You are right! When try 3.6.1, ran into indentation error. I saw similar problems posted 10 month ago and you suggested him writing email to the related developers. Not sure how his problem was resolved. (C:ProgramDataAnaconda3) C:UsersPublic3rdPartyLibrariesQuantLib-SWIG-1.14Python>python setup.py build File "setup.py", line 2 Copyright (C) 2000, 2001, 2002, 2003 RiskMap srl ^ IndentationError: unexpected indent
– MagicFatto
Nov 21 at 1:24
By the way, Python 2.7.3 doesn't have this issue and I have never modified thesetup.py. The first three lines are:# -*- coding: iso-8859-1 -*- """ Copyright (C) 2000, 2001, 2002, 2003 RiskMap srl
– MagicFatto
Nov 21 at 1:40
It seems that Python doesn't recognize the second line (it reports line 3 as line 2). Please try adding a blank line between line 1 and 2.
– Luigi Ballabio
Nov 21 at 13:41
And anyway: did you try runningpip install QuantLib-Pythonas I suggested in your other question, instead of compiling?
– Luigi Ballabio
Nov 21 at 13:43
Thanks Luigi for staying with me all this time!!! I did trypip install QuantLib-Pythonand it didn't work out. If that worked, it would make life easier :). Once I inserted one blank line between the original first line and second line in thesetup.py, the problem went away. The build went well and finished generating code!!! Didn't expect this to be this hard but lucky to have your guidance.
– MagicFatto
Nov 21 at 14:17
add a comment |
You are right! When try 3.6.1, ran into indentation error. I saw similar problems posted 10 month ago and you suggested him writing email to the related developers. Not sure how his problem was resolved. (C:ProgramDataAnaconda3) C:UsersPublic3rdPartyLibrariesQuantLib-SWIG-1.14Python>python setup.py build File "setup.py", line 2 Copyright (C) 2000, 2001, 2002, 2003 RiskMap srl ^ IndentationError: unexpected indent
– MagicFatto
Nov 21 at 1:24
By the way, Python 2.7.3 doesn't have this issue and I have never modified thesetup.py. The first three lines are:# -*- coding: iso-8859-1 -*- """ Copyright (C) 2000, 2001, 2002, 2003 RiskMap srl
– MagicFatto
Nov 21 at 1:40
It seems that Python doesn't recognize the second line (it reports line 3 as line 2). Please try adding a blank line between line 1 and 2.
– Luigi Ballabio
Nov 21 at 13:41
And anyway: did you try runningpip install QuantLib-Pythonas I suggested in your other question, instead of compiling?
– Luigi Ballabio
Nov 21 at 13:43
Thanks Luigi for staying with me all this time!!! I did trypip install QuantLib-Pythonand it didn't work out. If that worked, it would make life easier :). Once I inserted one blank line between the original first line and second line in thesetup.py, the problem went away. The build went well and finished generating code!!! Didn't expect this to be this hard but lucky to have your guidance.
– MagicFatto
Nov 21 at 14:17
You are right! When try 3.6.1, ran into indentation error. I saw similar problems posted 10 month ago and you suggested him writing email to the related developers. Not sure how his problem was resolved. (C:ProgramDataAnaconda3) C:UsersPublic3rdPartyLibrariesQuantLib-SWIG-1.14Python>python setup.py build File "setup.py", line 2 Copyright (C) 2000, 2001, 2002, 2003 RiskMap srl ^ IndentationError: unexpected indent
– MagicFatto
Nov 21 at 1:24
You are right! When try 3.6.1, ran into indentation error. I saw similar problems posted 10 month ago and you suggested him writing email to the related developers. Not sure how his problem was resolved. (C:ProgramDataAnaconda3) C:UsersPublic3rdPartyLibrariesQuantLib-SWIG-1.14Python>python setup.py build File "setup.py", line 2 Copyright (C) 2000, 2001, 2002, 2003 RiskMap srl ^ IndentationError: unexpected indent
– MagicFatto
Nov 21 at 1:24
By the way, Python 2.7.3 doesn't have this issue and I have never modified the
setup.py. The first three lines are: # -*- coding: iso-8859-1 -*- """ Copyright (C) 2000, 2001, 2002, 2003 RiskMap srl– MagicFatto
Nov 21 at 1:40
By the way, Python 2.7.3 doesn't have this issue and I have never modified the
setup.py. The first three lines are: # -*- coding: iso-8859-1 -*- """ Copyright (C) 2000, 2001, 2002, 2003 RiskMap srl– MagicFatto
Nov 21 at 1:40
It seems that Python doesn't recognize the second line (it reports line 3 as line 2). Please try adding a blank line between line 1 and 2.
– Luigi Ballabio
Nov 21 at 13:41
It seems that Python doesn't recognize the second line (it reports line 3 as line 2). Please try adding a blank line between line 1 and 2.
– Luigi Ballabio
Nov 21 at 13:41
And anyway: did you try running
pip install QuantLib-Python as I suggested in your other question, instead of compiling?– Luigi Ballabio
Nov 21 at 13:43
And anyway: did you try running
pip install QuantLib-Python as I suggested in your other question, instead of compiling?– Luigi Ballabio
Nov 21 at 13:43
Thanks Luigi for staying with me all this time!!! I did try
pip install QuantLib-Python and it didn't work out. If that worked, it would make life easier :). Once I inserted one blank line between the original first line and second line in the setup.py, the problem went away. The build went well and finished generating code!!! Didn't expect this to be this hard but lucky to have your guidance.– MagicFatto
Nov 21 at 14:17
Thanks Luigi for staying with me all this time!!! I did try
pip install QuantLib-Python and it didn't work out. If that worked, it would make life easier :). Once I inserted one blank line between the original first line and second line in the setup.py, the problem went away. The build went well and finished generating code!!! Didn't expect this to be this hard but lucky to have your guidance.– MagicFatto
Nov 21 at 14:17
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53400935%2fquantlib-1-14-and-quantlib1-14-swig-versions-of-visual-c-prior-to-vc10-201%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What is the question? What version of MSVC are your using?
– NathanOliver
Nov 20 at 20:26
Welcome to Stack Overflow! Please take the tour and in particular read How to Ask. It's very unclear what your question is or what you expect from a solution. After all, the error message is pretty clear.
– Ulrich Eckhardt
Nov 20 at 20:33
Wasn't finishing the question and browser was terminated unexpected. Re-edit it for clarity.
– MagicFatto
Nov 20 at 20:46