Menu

#53 3.3.2.0 doesn't work for me

Duplicate
nobody
None
Medium
Defect
2013-08-15
2013-06-05
Anonymous
No

Originally created by: haven...@gmail.com

What steps will reproduce the problem?
1. Launch any app under 3.3.2.0, 64-bit
2. None of them will do anything other than flash a brief console and exit (at most)
3. IPython console shows memory address error if that helps.  Can't find any other logging information.  Suggestions welcome on how to capture error log.

What is the expected output? What do you see instead?
I expected the application to launch or show some error information 

What version of the product are you using? On what operating system?
3.3.2.0 on Windows 7

Please provide any additional information below.
2.7.5.0-64bit apps all work (on the same machine) as far as I can tell.  At least I haven't encountered any problems yet with it, only 3.3.2.0

Related

Tickets: #30
Tickets: #57

Discussion

  • Anonymous

    Anonymous - 2013-06-12

    Originally posted by: btcoooo...@gmail.com

    This may be the same issue I just reported as #57. See if installing the 64-bit version of MSVCR100.DLL fixes it.

     
  • Anonymous

    Anonymous - 2013-06-14

    Originally posted by: haven...@gmail.com

    Following btcoooo...'s advice in issue #57, I attempted to install a 64-bit version of MSVCR100.DLL.  Either I was not successful (do not have admin, so copied a similar DLL from c:\windows\SysWOW64) or the problem lies elsewhere.  Every attempt to open a any python results in a 0xc000007b error. 

    Except, oddly, py.exe in python-3.3.2-amd64 folder opens another (32-bit 2.6.6) instance of python on the same machine and python.exe in same folder tries to open the winpython 3.3.2.0 instance and fails.  Is that behavior expected?  I expected all facets of winpython to be isolated from all other versions of python.

    Nothing changes for 3.3.2.1--still broken for me.

     

    Related

    Tickets: #57

  • Anonymous

    Anonymous - 2013-06-17

    Originally posted by: btcoooo...@gmail.com

    I believe the DLLs in SysWOW64 are 32-bit. Try getting the DLL from here:
    http://www.microsoft.com/en-us/download/details.aspx?id=14632

    If you already have Python 3.3 installed on your machine then the behavior you describe in your second paragraph is probably due to the new Python launcher for Windows, as described here:
    http://docs.python.org/3/whatsnew/3.3.html#pep-397-python-launcher-for-windows

     
  • Anonymous

    Anonymous - 2013-06-17

    Originally posted by: pierre.raybaut

    I confirm that, on a 64-bit Windows platform, DLLs located in SysWOW64 are 32-bit whereas DLLs located in System32 are 64-bit (odd but true...).

     
  • Anonymous

    Anonymous - 2013-08-15

    Originally posted by: pierre.raybaut

    (No comment was entered for this change.)

    Mergedinto: 57
    Status: Duplicate

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.