You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openoffice.apache.org by bu...@apache.org on 2014/01/05 17:08:22 UTC
[Bug 123975] New: Update to Python 3.3
https://issues.apache.org/ooo/show_bug.cgi?id=123975
Bug ID: 123975
Issue Type: DEFECT
Summary: Update to Python 3.3
Product: General
Version: 4.1.0-dev
Hardware: All
OS: All
Status: CONFIRMED
Severity: normal
Priority: P3
Component: code
Assignee: issues@openoffice.apache.org
Reporter: hanya.runo@gmail.com
CC: issues@openoffice.apache.org
Please update shipped Python to version 3.X.
Python 2.7.X will be maintained until May 2015 [1]. It should be moved to
Python 3k until then.
[1] http://www.python.org/dev/peps/pep-0373/
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Bug 123975] Update to Python 3.3
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=123975
--- Comment #11 from Ariel Constenla-Haile <ar...@apache.org> ---
(In reply to papayes from comment #10)
> Sorry, but I do not think that this beta is a major version, but simply one
> 4.0.2.
Well, this was my point, AOO 5 will be the next major version were incompatible
changes like switching to Python 3 can to be introduced.
> One beta exactly has to allow to test the setting-up of Python 3.3 without
> waiting for 2015 like that allows to test Java 1.7 with Mac Os!
This is rather different and cannot be compared. Since Revision 1229371 for Bug
118352 AOO can detected and use Java 1.7 and client code didn't need to change
a single line of code because Java 1.7 can execute Java 1.6 code; with Python 3
the situation is completely different, as explained in comment 6 .
> You were less sensitive to cold when you modified in AOO 4 the management of
> the menus what involved the modification of the extensions !
This was an incompatible change in a major version switch (which by the way,
wasn't asked be my, and could have been reverted in time if it were considered
something bad, in context: http://markmail.org/message/jpn4e3no4jgv3n4d
http://markmail.org/message/fhsepy2a56yhubi2); an incompatible change like
switching from Python 2 to Python 3 will have to wait - IMO - to the next
major, AOO 5.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Bug 123975] Update to Python 3.3
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=123975
papayes <jy...@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jyl44@free.fr
--- Comment #8 from papayes <jy...@free.fr> ---
Hello,
I hoped with AOO 4.1 beta 1573601 finally see Python 3.3.3 replace an outdated
version.
I tested with Python 3 LibO 4.2.2 and also on OsX10.9.2 without problems:
for example, the French extension "Grammalect 3.8.3"
http://www.dicollecte.org/grammalecte/oxt/Grammalecte-v0.3.8.3.oxt settles
properly.
AOO for Win, OSX or Linux, we are forced to use an older version built with
python 2.7!
http://www.dicollecte.org/grammalecte/oxt/Grammalecte-v0.3.6.2-py2x.oxt
It is a pity!
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Bug 123975] Update to Python 3.3
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=123975
Andrea Pescetti <pe...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pescetti@apache.org
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Issue 123975] Update to Python 3.3
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=123975
--- Comment #13 from hanya <ha...@gmail.com> ---
I met the problem during to build gtest with Python 3.X shipping because
gtest-1.7.0 needs Python 2.X to be built.
Once shipped Python is built, it is used from solver since the path to the
solver is there before system paths in PATH.
In the target "fused-gtest:" from misc/build/gtest-1.7.0/Makefile,
the following file is executed like this:
> "$(srcdir)/scripts/fuse_gtest_files.py" "$(srcdir)/fused-src"
It seems the problems are:
- syntax for print statement -> should be called as function
- sets module -> gone and they can be used without imporing some modules
used in the fuse_gtest/files.py file.
--
You are receiving this mail because:
You are on the CC list for the issue.
You are the assignee for the issue.
You are watching all issue changes.
[Bug 123975] Update to Python 3.3
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=123975
hanya <ha...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Issue Type|DEFECT |TASK
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Bug 123975] Update to Python 3.3
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=123975
oooforum <oo...@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |oooforum@free.fr
--- Comment #4 from oooforum <oo...@free.fr> ---
Hello,
I don't see this issue in
http://people.apache.org/~jsc/developer-snapshots/snapshot/AOO4.1.0_Beta_fixes.html
Did you think that it could be added?
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Bug 123975] Update to Python 3.3
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=123975
--- Comment #2 from hanya <ha...@gmail.com> ---
Created attachment 82231
--> https://issues.apache.org/ooo/attachment.cgi?id=82231&action=edit
For delivering all test files for regression test
Use this d.lst files to deliver regression test of Python.
Regression test can be executed as follows:
> python -m test
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Bug 123975] Update to Python 3.3
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=123975
--- Comment #3 from hanya <ha...@gmail.com> ---
There is error.py file in urllib module. When it was copied during
make_installer.pl, I got the following error:
>ERROR: ERROR: Found an error in the logfile. Packaging failed.
>in function: analyze_and_save_logfile
> ERROR: Copy: /tmp/ooopackaging/i_40161389076232/wntmsci12.pro/Apache_OpenOffice
>/archive/zip/en-US/00/python-core-3_3_3_zip/python-core-3.3.3/lib/urllib/error.py
>to /tmp/m6mdIkUwMy/Apache_OpenOffice_4.0.0_Win_x86_install-arc_en-US/OpenOffice 4
>/program/python-core-3.3.3/lib/urllib/error.py
In installer::control::check_logfile function, each log lines are checked
against
the occurrence with /\bError\b/i expression.
The above line matched with the expression and it treated as error and stopped
the packing process.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Bug 123975] Update to Python 3.3
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=123975
--- Comment #6 from hanya <ha...@gmail.com> ---
This is not finished yet. The following tasks are remained:
- Building code for Windows, Mac OS X, mingw
- Testing on all platform
- Building problem of Python on Linux environment caused by multithreaded make
Almost all macros and UNO components written in Python will not work without
porting from Python 2 to 3 after this update.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Issue 123975] Update to Python 3.3
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=123975
Andrea Pescetti <pe...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |AOO Later
--- Comment #12 from Andrea Pescetti <pe...@apache.org> ---
Targeting to AOO Later, meaning that this will be for OpenOffice 5.0. Note that
despite all the nice work from hanya the work is unifinished, so this must be
completed and tested early in the 5.0 cycle.
On the other hand, the death of Python 2 has been postponed from May 2015 until
May 2020: http://legacy.python.org/dev/peps/pep-0373/ . So, while it is still
totally recommended to upgrade to Python 3, this is no longer urgent as it used
to be.
--
You are receiving this mail because:
You are on the CC list for the issue.
You are the assignee for the issue.
You are watching all issue changes.
[Bug 123975] Update to Python 3.3
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=123975
--- Comment #10 from papayes <jy...@free.fr> ---
Hello,
To Ariel Constenla-Haile
I know how to read, thank you, even if English is not my mother tongue.
Sorry, but I do not think that this beta is a major version, but simply one
4.0.2.
One beta exactly has to allow to test the setting-up of Python 3.3 without
waiting for 2015 like that allows to test Java 1.7 with Mac Os!
You were less sensitive to cold when you modified in AOO 4 the management of
the menus what involved the modification of the extensions !
Best Regards,
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Bug 123975] Update to Python 3.3
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=123975
--- Comment #7 from jsc@apache.org ---
I am not sure if we really still support mingw, I don|t know anybody who is
building under mingw
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Bug 123975] Update to Python 3.3
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=123975
--- Comment #1 from hanya <ha...@gmail.com> ---
Created attachment 82222
--> https://issues.apache.org/ooo/attachment.cgi?id=82222&action=edit
Experimental patch to update Python 3.3.3 for Linux and Windows environment
Changes contained only for Linux and Windows VS9 build.
pyuno has been migrated to be work with Python 3k. Therefore most changes are
in building Python itself.
Changes:
- without imp module: imp module is deprecated since Python 3.4. Instantiate
new module without using it.
- pyuno has some warnings, the patch contains fix for them.
- Official compiler for Python has been changed to VS 2010 for Windows
environment.
And solution file for VS 2008 is there in PC/VS9.0.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Bug 123975] Update to Python 3.3
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=123975
jsc@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jsc@apache.org
--- Comment #5 from jsc@apache.org ---
Python updates are always not easy to decide. Can somebody explain the
implication for users with scripts written in older versions?
For 4.1 I would not really add it because it not tested and available on all
platforms. But in general I agree that we should test it asap
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Bug 123975] Update to Python 3.3
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=123975
--- Comment #9 from Ariel Constenla-Haile <ar...@apache.org> ---
(In reply to papayes from comment #8)
> Hello,
> I hoped with AOO 4.1 beta 1573601 finally see Python 3.3.3 replace an
> outdated version.
As explained in comment 6 "Almost all macros and UNO components written in
Python will not work without porting from Python 2 to 3 after this update."
Such an incompatible change in client code can only happen on a major release.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.