I'm no longer using cx_Freeze, so my opinion isn't that important, but I
think this is a reasonable approach - things do seem to be slowly moving
towards Python 3, and as you say, cx_Freeze 5.x will still be available for
people who want to use it for Python 2.
I'm planning a similar move for Pynsist 2.0 to reduce the number of
different cases it needs to handle.
Thomas
On 30 April 2017 at 04:56, Anthony Tuininga <anthony.tuini...@gmail.com>
wrote:
> All,
>
> I am hoping to get your opinion on whether it makes sense to release
> cx_Freeze 6 as Python 3.5+ only. Python 2.7 is nearing the end of life and
> more and more people are using Python 3.5+ so it seems a reasonable time to
> consider this. cx_Freeze 5 would continue to exist for as long as Python
> 2.7 remains viable.
>
> One problem in particular that I have been working on solving is the
> removal of the dependency on the built-in definition of sys.path. This
> doesn't work on Ubuntu and doesn't work in a virtual environment. The
> correction doesn't work in Python 2.7 so I was planning on correcting this
> in cx_Freeze 6 and making it Python 3.5+. Any and all thoughts appreciated.
> Thanks!
>
> Anthony
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> cx-freeze-users mailing list
> cx-freeze-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/cx-freeze-users
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
cx-freeze-users mailing list
cx-freeze-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cx-freeze-users
