From: David G. <d.l...@gm...> - 2011-03-23 21:23:00
|
Hi! When I run py2exe against Python 2.6.6, I get "C:\Python26\lib\site-packages\py2exe\build_exe.py:16: DeprecationWarning: the sets module is deprecated" which implies to me that py2exe needs an update (unless, are you no longer supporting 2.6?), but when I go to the downloads page, I see that the latest version is 0.6.9 (which is what I'm running), and the modified time is 2008-11-16! Has py2exe development stalled? What's the significance of this deprecation warning I'm getting, and are there plans to update py2exe to comply w/ the change? If py2exe is no longer under active development, can someone recommend a functionally equivalent module that is? Thanks! David Goldsmith Olympia, WA -- In science it often happens that scientists say, 'You know that's a really good argument; my position is mistaken,' and then they would actually change their minds and you never hear that old view from them again. They really do it. It doesn't happen as often as it should, because scientists are human and change is sometimes painful. But it happens every day. I cannot recall the last time something like that happened in politics or religion. - Carl Sagan, 1987 CSICOP address |
From: Mark H. <mha...@sk...> - 2011-03-23 22:41:21
|
On 24/03/2011 8:22 AM, David Goldsmith wrote: > Hi! When I run py2exe against Python 2.6.6, I get > "C:\Python26\lib\site-packages\py2exe\build_exe.py:16: > DeprecationWarning: the sets module is deprecated" which implies to me > that py2exe needs an update (unless, are you no longer supporting > 2.6?), but when I go to the downloads page, I see that the latest > version is 0.6.9 (which is what I'm running), and the modified time is > 2008-11-16! > > Has py2exe development stalled? It has stalled, but isn't dead. > What's the significance of this > deprecation warning I'm getting, and are there plans to update py2exe > to comply w/ the change? At this stage the only significance should be the warning being printed - it should work fine. There are no concrete plans to fix that issue, but patches would be welcome. > If py2exe is no longer under active > development, can someone recommend a functionally equivalent module > that is? You could try cx_Freeze if it really worries you that much, but py2exe will not go away. Cheers, Mark |
From: David G. <d.l...@gm...> - 2011-03-23 23:18:35
|
Thanks for your reply. Regarding a patch, I'll look at the source of course, but if you (or anyone) know: what does py2exe use sets for and what would be the most logical replacement for that functionality. Thanks again! DG On Wed, Mar 23, 2011 at 3:40 PM, Mark Hammond <mha...@sk...> wrote: > On 24/03/2011 8:22 AM, David Goldsmith wrote: >> >> Hi! When I run py2exe against Python 2.6.6, I get >> "C:\Python26\lib\site-packages\py2exe\build_exe.py:16: >> DeprecationWarning: the sets module is deprecated" which implies to me >> that py2exe needs an update (unless, are you no longer supporting >> 2.6?), but when I go to the downloads page, I see that the latest >> version is 0.6.9 (which is what I'm running), and the modified time is >> 2008-11-16! >> >> Has py2exe development stalled? > > It has stalled, but isn't dead. > >> What's the significance of this >> deprecation warning I'm getting, and are there plans to update py2exe >> to comply w/ the change? > > At this stage the only significance should be the warning being printed - it > should work fine. There are no concrete plans to fix that issue, but > patches would be welcome. > >> If py2exe is no longer under active >> development, can someone recommend a functionally equivalent module >> that is? > > You could try cx_Freeze if it really worries you that much, but py2exe will > not go away. > > Cheers, > > Mark > -- In science it often happens that scientists say, 'You know that's a really good argument; my position is mistaken,' and then they would actually change their minds and you never hear that old view from them again. They really do it. It doesn't happen as often as it should, because scientists are human and change is sometimes painful. But it happens every day. I cannot recall the last time something like that happened in politics or religion. - Carl Sagan, 1987 CSICOP address |
From: Jimmy R. <ji...@re...> - 2011-03-24 00:23:49
|
On Wed, Mar 23, 2011 at 4:18 PM, David Goldsmith <d.l...@gm...>wrote: > Thanks for your reply. Regarding a patch, I'll look at the source of > course, but if you (or anyone) know: what does py2exe use sets for and > what would be the most logical replacement for that functionality. > Thanks again! > > I don't know off the top of my head what sets are used for, but the issue is that py2exe still supports older versions of python where sets were not in builtins, but were instead in a module. The warning you are seeing is that this module is being imported in a newer version of python. There is a common idiom for testing if the set builtin is available, and if not to import it from the old module - it would make sense to apply this idiom. Jimmy |
From: Fox, M. K <mic...@bo...> - 2011-03-23 23:36:23
|
The problem is in your code, not in py2exe. The 'sets' module is deprecated in Python 2.6 because 'set' was added as a new builtin class. See http://docs.python.org/library/stdtypes.html#set-types-set-frozenset I don't know why py2exe cares about the deprecation but you can fix the problem by removing the statement in your code that imports sets. -----Original Message----- From: David Goldsmith [mailto:d.l...@gm...] Sent: Wednesday, March 23, 2011 2:23 PM To: py2...@li... Subject: [Py2exe-users] Status of py2exe development Hi! When I run py2exe against Python 2.6.6, I get "C:\Python26\lib\site-packages\py2exe\build_exe.py:16: DeprecationWarning: the sets module is deprecated" which implies to me that py2exe needs an update (unless, are you no longer supporting 2.6?), but when I go to the downloads page, I see that the latest version is 0.6.9 (which is what I'm running), and the modified time is 2008-11-16! Has py2exe development stalled? What's the significance of this deprecation warning I'm getting, and are there plans to update py2exe to comply w/ the change? If py2exe is no longer under active development, can someone recommend a functionally equivalent module that is? Thanks! David Goldsmith Olympia, WA -- In science it often happens that scientists say, 'You know that's a really good argument; my position is mistaken,' and then they would actually change their minds and you never hear that old view from them again. They really do it. It doesn't happen as often as it should, because scientists are human and change is sometimes painful. But it happens every day. I cannot recall the last time something like that happened in politics or religion. - Carl Sagan, 1987 CSICOP address ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Py2exe-users mailing list Py2...@li... https://lists.sourceforge.net/lists/listinfo/py2exe-users |
From: Mark H. <ski...@gm...> - 2011-03-24 00:19:11
|
On 24/03/2011 10:36 AM, Fox, Michael K wrote: > The problem is in your code, not in py2exe. The 'sets' module is deprecated in Python 2.6 because 'set' was added as a new builtin class. > See http://docs.python.org/library/stdtypes.html#set-types-set-frozenset Actually, py2exe has a couple of references to: from sets import Set as set Which I assume is the problem... Cheers, Mark |
From: David G. <d.l...@gm...> - 2011-03-24 01:30:05
|
Thanks for the clarification. Is __builtin__.set equivalent in API and functionality to sets.Set? If so, shouldn't the patch be as simple as removing those references? On Wed, Mar 23, 2011 at 5:18 PM, Mark Hammond <ski...@gm...> wrote: > On 24/03/2011 10:36 AM, Fox, Michael K wrote: >> >> The problem is in your code, not in py2exe. The 'sets' module is >> deprecated in Python 2.6 because 'set' was added as a new builtin class. >> See http://docs.python.org/library/stdtypes.html#set-types-set-frozenset > > Actually, py2exe has a couple of references to: > > from sets import Set as set > > Which I assume is the problem... > > Cheers, > > Mark > -- In science it often happens that scientists say, 'You know that's a really good argument; my position is mistaken,' and then they would actually change their minds and you never hear that old view from them again. They really do it. It doesn't happen as often as it should, because scientists are human and change is sometimes painful. But it happens every day. I cannot recall the last time something like that happened in politics or religion. - Carl Sagan, 1987 CSICOP address |
From: Mark H. <ski...@gm...> - 2011-03-24 01:35:17
|
On 24/03/2011 12:29 PM, David Goldsmith wrote: > Thanks for the clarification. Is __builtin__.set equivalent in API > and functionality to sets.Set? AFAIK (and for how it is used in py2exe), yes. > If so, shouldn't the patch be as > simple as removing those references? You will need to ensure the "old" way works in earlier Python versions with no builtin set. Mark |
From: David G. <d.l...@gm...> - 2011-03-24 01:42:18
|
Ah, yes, of course. On Wed, Mar 23, 2011 at 6:33 PM, Mark Hammond <ski...@gm...> wrote: > On 24/03/2011 12:29 PM, David Goldsmith wrote: >> >> Thanks for the clarification. Is __builtin__.set equivalent in API >> and functionality to sets.Set? > > AFAIK (and for how it is used in py2exe), yes. > >> If so, shouldn't the patch be as >> simple as removing those references? > > You will need to ensure the "old" way works in earlier Python versions with > no builtin set. > > Mark > -- In science it often happens that scientists say, 'You know that's a really good argument; my position is mistaken,' and then they would actually change their minds and you never hear that old view from them again. They really do it. It doesn't happen as often as it should, because scientists are human and change is sometimes painful. But it happens every day. I cannot recall the last time something like that happened in politics or religion. - Carl Sagan, 1987 CSICOP address |
From: Werner F. B. <wer...@fr...> - 2011-03-24 07:53:02
|
On 24/03/2011 02:42, David Goldsmith wrote: > Ah, yes, of course. > > On Wed, Mar 23, 2011 at 6:33 PM, Mark Hammond<ski...@gm...> wrote: >> On 24/03/2011 12:29 PM, David Goldsmith wrote: >>> >>> Thanks for the clarification. Is __builtin__.set equivalent in API >>> and functionality to sets.Set? >> >> AFAIK (and for how it is used in py2exe), yes. >> >>> If so, shouldn't the patch be as >>> simple as removing those references? >> >> You will need to ensure the "old" way works in earlier Python versions with >> no builtin set. >> >> Mark >> > > > Making this change in py2exe.build_exe.py works for me: # Python 2.6 deprecation warning ##import sets try: set except NameError: from sets import Set as set Werner |