Re: [IronPython] Which modules collection to use?
Re: IRONPYTHONPATH It looks like the magic is already in place in dev.bat to set [IRON]PYTHONPATH to the right path. However, the setting is conditional on If DEFINED THISISSNAP I am not a stupid fella, but i had to resort to bugging you and asking about the modules set up. I am sure there are / were / will be other stumped ones. I wonder if this would be a big deal to change the dev.bat to set the right paths without relying on THISISSNAP being set. Since this would only affect those who run within dev.bat's magic land, the extra bit of default magic should not be a surprise, no? I'd propose a patch, but don't undersand what half of dev.bat does, and would prefer people familiar with the matter to make the change, if it is agreed upon. Daniel. On Fri, Jan 21, 2011 at 17:24, Dino Viehland di...@microsoft.com wrote: Daniel wrote: Pulled src from github. The devel set up instructions (http://ironpython.codeplex.com/wikipage?title=Respository%20Instructions) and all the script magic already in place is just great as things compile and run. Very cool. However, need help figuring some things out, please: 1. Neither the release, nor the debug deployment copies the standard module files into Lib. Is there magic in place for that already, like a project file that has the deployment paths spelled out? We have a copy of the std lib in External.LCA_RESTRICTED\Languages\IronPython\27\Lib. I generally just set IRONPYTHONPATH at that directory which is much better than copying it on every build. For releases the MSI builder will pick it up out External.LCA_RESTRICTED\Languages\CPython\27\Lib. The difference between those two directories is the tests - the IronPython dir has various changes to disable failing tests, occasionally adds some extra tests, etc... The 2 dirs are also useful for doing 3 way merges when updating the standard library. That way you know what the last version we pulled was. 2. There are two copies of modules sets. One in cPython/Lib, there other is in IronPython/27/Lib. The answer is probably obvious, but which set of modules do I need to copy? [conveniently answered above] 3. Before I found the bundled module collections, I tried modules from 2.7.1 (r271:86832, Nov 27 2010, 18:30:46) [MSC v.1500 32 bit (Intel)] and saw code in modules blowing up left and right. It's obvious that the modules collection in IronLanguages is stale, but i wonder how stale it is... Are they from 2.5/2.6 time? If the next IPY release is 2.7 do we need to go and update the modules bundled with 2.7? These are all from the 2.7 timeframe and should be from 2.7.0 at the very earliest. If you windiff the CPython lib dir w/ your 2.7.1 install Lib dir you should be able to see the differences. I'm surprised that things are blowing up - maybe there's some site packages breaking things in your install? ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Re: [IronPython] Which modules collection to use?
Daniel wrote: Re: IRONPYTHONPATH It looks like the magic is already in place in dev.bat to set [IRON]PYTHONPATH to the right path. However, the setting is conditional on If DEFINED THISISSNAP I am not a stupid fella, but i had to resort to bugging you and asking about the modules set up. I am sure there are / were / will be other stumped ones. I wonder if this would be a big deal to change the dev.bat to set the right paths without relying on THISISSNAP being set. Since this would only affect those who run within dev.bat's magic land, the extra bit of default magic should not be a surprise, no? I'd propose a patch, but don't undersand what half of dev.bat does, and would prefer people familiar with the matter to make the change, if it is agreed upon. This sounds fine - anything related to SNAP can be disregarded at this point, SNAP is an internal Microsoft gated checkin system which we used for submitting checkins and running all of the tests. I don't see why we wouldn't want to always set IRONPYTHONPATH. We did at one point run our own tests both w/ and w/o the std lib but we stopped doing that some time ago. ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
[IronPython] Which modules collection to use?
Hi Pulled src from github. The devel set up instructions (http://ironpython.codeplex.com/wikipage?title=Respository%20Instructions) and all the script magic already in place is just great as things compile and run. Very cool. However, need help figuring some things out, please: 1. Neither the release, nor the debug deployment copies the standard module files into Lib. Is there magic in place for that already, like a project file that has the deployment paths spelled out? 2. There are two copies of modules sets. One in cPython/Lib, there other is in IronPython/27/Lib. The answer is probably obvious, but which set of modules do I need to copy? 3. Before I found the bundled module collections, I tried modules from 2.7.1 (r271:86832, Nov 27 2010, 18:30:46) [MSC v.1500 32 bit (Intel)] and saw code in modules blowing up left and right. It's obvious that the modules collection in IronLanguages is stale, but i wonder how stale it is... Are they from 2.5/2.6 time? If the next IPY release is 2.7 do we need to go and update the modules bundled with 2.7? Daniel. ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Re: [IronPython] Which modules collection to use?
Daniel wrote: Pulled src from github. The devel set up instructions (http://ironpython.codeplex.com/wikipage?title=Respository%20Instructions) and all the script magic already in place is just great as things compile and run. Very cool. However, need help figuring some things out, please: 1. Neither the release, nor the debug deployment copies the standard module files into Lib. Is there magic in place for that already, like a project file that has the deployment paths spelled out? We have a copy of the std lib in External.LCA_RESTRICTED\Languages\IronPython\27\Lib. I generally just set IRONPYTHONPATH at that directory which is much better than copying it on every build. For releases the MSI builder will pick it up out External.LCA_RESTRICTED\Languages\CPython\27\Lib. The difference between those two directories is the tests - the IronPython dir has various changes to disable failing tests, occasionally adds some extra tests, etc... The 2 dirs are also useful for doing 3 way merges when updating the standard library. That way you know what the last version we pulled was. 2. There are two copies of modules sets. One in cPython/Lib, there other is in IronPython/27/Lib. The answer is probably obvious, but which set of modules do I need to copy? [conveniently answered above] 3. Before I found the bundled module collections, I tried modules from 2.7.1 (r271:86832, Nov 27 2010, 18:30:46) [MSC v.1500 32 bit (Intel)] and saw code in modules blowing up left and right. It's obvious that the modules collection in IronLanguages is stale, but i wonder how stale it is... Are they from 2.5/2.6 time? If the next IPY release is 2.7 do we need to go and update the modules bundled with 2.7? These are all from the 2.7 timeframe and should be from 2.7.0 at the very earliest. If you windiff the CPython lib dir w/ your 2.7.1 install Lib dir you should be able to see the differences. I'm surprised that things are blowing up - maybe there's some site packages breaking things in your install? ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Re: [IronPython] Which modules collection to use?
Thx on the IRONPYTHONPATH hint. Regarding what blows up: copy'n'paste Lib folder from cPython 2.7.1 into /Debug/.., followed by bdc 6 Warning(s) 0 Error(s) Time Elapsed 00:00:37.34 C:\workipy IronPython 2.7 Beta 1 DEBUG (2.7.0.10) on .NET 4.0.30319.1 Type help, copyright, credits or license for more information. import os Traceback (most recent call last): File stdin, line 1, in module File C:\work\ironlang\Bin\Debug\Lib\os.py, line 398, in module File C:\work\ironlang\Bin\Debug\Lib\UserDict.py, line 84, in module File C:\work\ironlang\Bin\Debug\Lib\abc.py, line 109, in register File C:\work\ironlang\Bin\Debug\Lib\abc.py, line 151, in __subclasscheck__ File C:\work\ironlang\Bin\Debug\Lib\_weakrefset.py, line 69, in __contains__ TypeError: cannot create weak reference to 'classobj' object Daniel. On Fri, Jan 21, 2011 at 17:24, Dino Viehland di...@microsoft.com wrote: Daniel wrote: Pulled src from github. The devel set up instructions (http://ironpython.codeplex.com/wikipage?title=Respository%20Instructions) and all the script magic already in place is just great as things compile and run. Very cool. However, need help figuring some things out, please: 1. Neither the release, nor the debug deployment copies the standard module files into Lib. Is there magic in place for that already, like a project file that has the deployment paths spelled out? We have a copy of the std lib in External.LCA_RESTRICTED\Languages\IronPython\27\Lib. I generally just set IRONPYTHONPATH at that directory which is much better than copying it on every build. For releases the MSI builder will pick it up out External.LCA_RESTRICTED\Languages\CPython\27\Lib. The difference between those two directories is the tests - the IronPython dir has various changes to disable failing tests, occasionally adds some extra tests, etc... The 2 dirs are also useful for doing 3 way merges when updating the standard library. That way you know what the last version we pulled was. 2. There are two copies of modules sets. One in cPython/Lib, there other is in IronPython/27/Lib. The answer is probably obvious, but which set of modules do I need to copy? [conveniently answered above] 3. Before I found the bundled module collections, I tried modules from 2.7.1 (r271:86832, Nov 27 2010, 18:30:46) [MSC v.1500 32 bit (Intel)] and saw code in modules blowing up left and right. It's obvious that the modules collection in IronLanguages is stale, but i wonder how stale it is... Are they from 2.5/2.6 time? If the next IPY release is 2.7 do we need to go and update the modules bundled with 2.7? These are all from the 2.7 timeframe and should be from 2.7.0 at the very earliest. If you windiff the CPython lib dir w/ your 2.7.1 install Lib dir you should be able to see the differences. I'm surprised that things are blowing up - maybe there's some site packages breaking things in your install? ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Re: [IronPython] Which modules collection to use?
Daniel wrote: Thx on the IRONPYTHONPATH hint. Regarding what blows up: copy'n'paste Lib folder from cPython 2.7.1 into /Debug/.., followed by bdc 6 Warning(s) 0 Error(s) Time Elapsed 00:00:37.34 C:\workipy IronPython 2.7 Beta 1 DEBUG (2.7.0.10) on .NET 4.0.30319.1 Type help, copyright, credits or license for more information. import os Traceback (most recent call last): File stdin, line 1, in module File C:\work\ironlang\Bin\Debug\Lib\os.py, line 398, in module File C:\work\ironlang\Bin\Debug\Lib\UserDict.py, line 84, in module File C:\work\ironlang\Bin\Debug\Lib\abc.py, line 109, in register File C:\work\ironlang\Bin\Debug\Lib\abc.py, line 151, in __subclasscheck__ File C:\work\ironlang\Bin\Debug\Lib\_weakrefset.py, line 69, in __contains__ TypeError: cannot create weak reference to 'classobj' object This is a bug in IronPython, here's the simple repro: class C: pass import weakref weakref.ref(C) OldClass just needs to have an IWeakReferencable implementation added to it. Looks like this is new in 2.7.0 and I'm guessing something in 2.7.1 now depends upon it. Maybe there just wasn't a test case for it or we have it disabled in the IronPython dir. ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
