FS#42907 - [python-xlsxwrite] [python2-xlsxwriter] conflicting file: /bin/usr/vba_extract.py

Attached to Project: Community Packages
Opened by David V (davidovitch) - Wednesday, 26 November 2014, 08:50 GMT
Last edited by Andrzej Giniewicz (Giniu) - Wednesday, 03 December 2014, 11:19 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Andrzej Giniewicz (Giniu)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Since the update to version 0.6.4-1, python-xlsxwriter and python2-xlsxwriter both contain a small python utility script /bin/usr/vba_extract.py. As a result, you can not install python2-xlsxwriter alongside python-xlsxwriter due to a file conflict.

For more info on vba_extract.py, see the documentation: http://xlsxwriter.readthedocs.org/en/latest/example_macros.html, and http://xlsxwriter.readthedocs.org/en/latest/working_with_macros.html.

As far as I can see, there are no references in the xlsxwriter code to vba_extract.py. Altough I haven't tested this, maybe the solution can simply be to rename vba_extract.py to vba_extract2.py for the python2 package.
This task depends upon

Closed by  Andrzej Giniewicz (Giniu)
Wednesday, 03 December 2014, 11:19 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 0.6.4-2 by renaming to vba_extract2.py
Comment by David V (davidovitch) - Wednesday, 26 November 2014, 08:55 GMT
From the documentation I see that the vba_extract.py utility can be used to extract the vbaProject.bin file that contains the macro's from an xlsx file. This is not automated in any way and the user has to do this manually. Therefore I think renaming to vba_extract2.py for the python2 package is probably the most simple way forward.
Comment by David V (davidovitch) - Wednesday, 26 November 2014, 10:10 GMT
ow...the path of vba_extract.py should obviously be: /usr/bin/vba_extract.py

Loading...