Issue444129
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2001-07-24 15:12 by anonymous, last changed 2022-04-10 16:04 by admin. This issue is now closed.
Messages (20) | |||
---|---|---|---|
msg5568 - (view) | Author: Nobody/Anonymous (nobody) | Date: 2001-07-24 15:12 | |
after upgrading from 2.0 to 2.1 then to 2.1.1 getting error that cant find python20.dll. I completely removed all traces of python and did a fresh install even modified the registry and removed all instances of python and pywin. It is important to note that I also removed an re-installed win32all and it failed to completely install because this error. Another note though python will still run after the error is given the win32 extensions fail to load. I am running on japaneese version of win2000 but had the same problem on the english version(the steps mentioned fixed the problem on english version). |
|||
msg5569 - (view) | Author: Tim Peters (tim.peters) * ![]() |
Date: 2001-07-24 16:34 | |
Logged In: YES user_id=31435 It sounds like you're trying to use Python 2.1.1 with a version of win32all built for 2.0. If so, you can't do that -- Python 2.1.x supplies python21.dll, not python20.dll. Go to ActiveState's site and either install ActivePython from them (which comes with a matched set of components), or get build 140 of win32all.exe from them (which was built to work with Python 2.1 -- but won't work with Python 2.0). Feel free to reopen this bug report if that doesn't solve it. |
|||
msg5570 - (view) | Author: Nobody/Anonymous (nobody) | Date: 2001-07-24 16:54 | |
Logged In: NO I am in fact not using the wrong version of win32all, the problem occurs prior to the install of the extensions. And it is correct that the 2.0 dll's are not installed and python2.1.1 (or 2.1) is complaining about it. I originaly thought the same thing so I removed win32all and python2.1.1 unloaded the dll's and re-installed 2.1.1 prior to re-installing win32all I got the same errors. |
|||
msg5571 - (view) | Author: Guido van Rossum (gvanrossum) * ![]() |
Date: 2001-07-24 17:00 | |
Logged In: YES user_id=6380 Sorry to butt in... Are you perhaps trying to use a third party extension like PIL or Numeric Python? Or your own? Extensions built for one Python version won't work with another. Can you tell us exactly what you did that gave the error message? Preferably with the path to the executable that you are trying to run that gives the exception. |
|||
msg5572 - (view) | Author: Tim Peters (tim.peters) * ![]() |
Date: 2001-07-24 17:07 | |
Logged In: YES user_id=31435 Then we need more specific information from you. I've never heard of this and find it difficult to believe that anything in the std Python 2.1 distribution requires python20.dll. I just removed all traces of all Pythons from my Win2K box, installed a fresh 2.1.1, and ran the std test suite to completion without any problems. Exactly what do you do that triggers a msg about python20.dll? If I can't reproduce it (and so far I can't), all we can do is guess. Do you perhaps have your own customizations in a PYTHONSTARTUP file that may be trying to access obsolete stuff? Have you tried running Python with -v to get a trace of what it's trying to import? |
|||
msg5573 - (view) | Author: Nobody/Anonymous (nobody) | Date: 2001-07-24 17:35 | |
Logged In: NO As of my last attempt I was running nothing but BeOpen pyhton 2.1.1 (no third party libraries)on a clean system. The error occurs when I run python from the command line or IDLE. I rolled back to 2.0 then installed 2.1.1 on top of it just now and it seemed to fix python. I then installed win32all 140 and the install script throws a similar error saying "module use of python20.dll conflicts with this version of python". |
|||
msg5574 - (view) | Author: Nobody/Anonymous (nobody) | Date: 2001-07-24 18:14 | |
Logged In: NO Okay lets get more specific after installing 2.1.1 on top of 2.0 it worked I then uninstalled 2.0 and the error is back "python20.dll not found". I ran with -v option and the last lib to load before the error is UserDict. If I install 2.0 then 2.1.1 I seem to be ok with python then but if I try to install win32all it complains and fails stating incompatible dll message. Starting over I have uninstalled everything and re- installed 2.1.1 and have the same problem. the command I am running is... c:\python21\python.exe -v |
|||
msg5575 - (view) | Author: Tim Peters (tim.peters) * ![]() |
Date: 2001-07-24 19:12 | |
Logged In: YES user_id=31435 I can't reproduce this on my system -- I see no problems at all. Can you capture the full output from running python - v and attach it to this report? I know exactly what's on my box, but can only guess about what's on yours. There are lots of clues in -v output that would help me. *Somehow* you're picking up an obsolete component, but there are no such components in the PythonLabs distribution. Note that "I then uninstalled 2.0" will cause registry entries to get restored to what they were at the time you first installed 2.0; that will wipe out the registry entries you created if you installed 2.1.1 before uninstalling 2.0. Anything relying on the registry *may* get screwed by that. Our (PythonLabs) distribution doesn't use the registry for much, but win32all may. |
|||
msg5576 - (view) | Author: Nobody/Anonymous (nobody) | Date: 2001-07-25 16:49 | |
Logged In: NO Here is the exact output displayed upon executing "python - v" E:\Python21>python -v # E:\Python21\lib\site.pyc matches E:\Python21\lib\site.py import site # precompiled from E:\Python21\lib\site.pyc # E:\Python21\lib\os.pyc matches E:\Python21\lib\os.py import os # precompiled from E:\Python21\lib\os.pyc import nt # builtin # E:\Python21\lib\ntpath.pyc matches E:\Python21 \lib\ntpath.py import ntpath # precompiled from E:\Python21\lib\ntpath.pyc # E:\Python21\lib\stat.pyc matches E:\Python21\lib\stat.py import stat # precompiled from E:\Python21\lib\stat.pyc # E:\Python21\lib\UserDict.pyc matches E:\Python21 \lib\UserDict.py import UserDict # precompiled from E:\Python21 \lib\UserDict.pyc Python 2.1.1 (#20, Jul 20 2001, 01:19:29) [MSC 32 bit (Intel)] on win32 Type "copyright", "credits" or "license" for more information. >>> Here is the additional error that appears displayed in a Windows dialog box. I have not typed it in "exactly" as it appears. The dots (...........) below represent a bunch of lines with directory paths: Dialog Box Title: Dynamic Library python20.dll path not found ============================================================ Dynamic Library python20.dll path not found. e:\su5j\security\test\bin................................... ............................................................ .......... ............................................................ ............................................................ ............................... e:\Program Files\Microsoft Visual Studio\Common\msdev98 \BIN\;T:\tools\bin; c:\ATF ============================================================ |
|||
msg5577 - (view) | Author: Tim Peters (tim.peters) * ![]() |
Date: 2001-07-25 17:41 | |
Logged In: YES user_id=31435 Assigned to Mark: can you make sense of this? I have to figure it has *something* to do with win32all, because this is the only report of its kind, and the -v output below shows that the base distribution is acting normally in all respects, including getting to the interactive prompt without trouble. Anonymous, do you use a PYTHONSTARTUP file? I asked before, but didn't hear back. That's the only way I know of in the std distribution to execute some Python code at startup that doesn't get mentioned in the -v outpout. |
|||
msg5578 - (view) | Author: Nobody/Anonymous (nobody) | Date: 2001-07-26 14:52 | |
Logged In: NO No we do not use a PYTHONSTARTUP file. Furthermore, I figured I would quit tryint to use 2.1 and go with 2.0. Well, guess what, when I try to use 2.0, it says it cannot find python21.dll. But when I try to use 2.1 (the reason to write to you guys), it says it cannot find the python20.dll ??????????????????????????????????? Note that I have manually deleted everythinng, checked the registers, etc, etc, etc. But obviously, something is hidden somewhere or there is something else going on. I, too, think that it may have to do with the win32 extension, but the whole thing is a huge mystery. |
|||
msg5579 - (view) | Author: Guido van Rossum (gvanrossum) * ![]() |
Date: 2001-07-26 14:57 | |
Logged In: YES user_id=6380 It sounds like you have screwed something over by your manual interventions. I suggest that we close this bug report and you reinstall Windows. |
|||
msg5580 - (view) | Author: Nobody/Anonymous (nobody) | Date: 2001-07-26 15:07 | |
Logged In: NO True, we may have screwed something up, but this is not what caused the problem in the first place. In other words, there is a bug somewhere that should be fixed. The fact that we may have screwed something up in trying to resolve it is not only irrelevant but it also does not mean the bug is gone. Others in my company have had the same problem but were able to get around the bug. Sure, close the bug report; we will start from scratch and, well, hopefully the mysterious bug will not come up again......... Nevertheless, a big THANK YOU for your gracious intervention and attempts at solving this. |
|||
msg5581 - (view) | Author: Guido van Rossum (gvanrossum) * ![]() |
Date: 2001-07-26 15:13 | |
Logged In: YES user_id=6380 Bugs of this nature almost *always* end up being caused by some local bizarrity of the Windows configuration, not by something the Python installer could have prevented. The fact that others in your company have the same problem (but no-one outside your company has reported this) suggests that it could be some kind of network management problem. Good luck! |
|||
msg5582 - (view) | Author: Tim Peters (tim.peters) * ![]() |
Date: 2001-07-26 15:32 | |
Logged In: YES user_id=31435 I'm reopening this, at least until MarkH has a chance to look at it. While some Windows Mysteries never get solved, you can't tell which those are in advance <wink>. Anonymous, I also would like to know what's going on, but you have a unique problem (never reported before), and one I can't reproduce. But my experience w/ win32all is trivial. That's why I want MarkH (win32all's author) to see this. |
|||
msg5583 - (view) | Author: Nobody/Anonymous (nobody) | Date: 2001-07-26 19:20 | |
Logged In: NO That sounds good to me. I will re-install Windows and try to install python 2.1 anew..........will let you know what happens. It should be interesting. |
|||
msg5584 - (view) | Author: Nobody/Anonymous (nobody) | Date: 2001-07-28 00:34 | |
Logged In: NO Well, I guess this is the end of this saga as far as I am concerned. I re-installed Windows 2000, and everything worked fine. We could conclude that it was Windows 2000, but could it be something in the win32all or a combination of the operating system AND win32all???? Anyway, thanks to all of you again for your help. If you look into this any further and find out anything new, I would love to be told what it was. Thanks again! |
|||
msg5585 - (view) | Author: Guido van Rossum (gvanrossum) * ![]() |
Date: 2001-07-28 01:33 | |
Logged In: YES user_id=6380 I wouldn't be surprised if it had something to do with this kind of leapfrog installation sequence: 1. install Python 2.0 2. install win32all for Python 2.0 3. install Python 2.1 4. uninstall Python 2.0 But there are so many variations... Mark, are you reading this? |
|||
msg5586 - (view) | Author: Mark Hammond (mhammond) * ![]() |
Date: 2001-07-29 17:02 | |
Logged In: YES user_id=14198 I am reading this, but still travelling. I have no idea off the top of my head, but suspect that Tim's latest "leap- frog" idea could explain it. I will check this out when I return. |
|||
msg5587 - (view) | Author: Mark Hammond (mhammond) * ![]() |
Date: 2002-03-28 01:44 | |
Logged In: YES user_id=14198 This is stale, and never since reported. I suspect a problem with the specific win32all build used. |
History | |||
---|---|---|---|
Date | User | Action | Args |
2022-04-10 16:04:14 | admin | set | github: 34823 |
2001-07-24 15:12:21 | anonymous | create |