Created attachment 48712 [details] the project that fails to return an array in the spreadsheet the project that fails to return an array in the spreadsheet I have been developing LO add-in for Calc using python. I can successfully create a in-cell function returning a single value, however, when I try and convert it to an array function I continually get a value error (http://www.oooforum.org/forum/viewtopic.phtml?t=124615&start=0&postdays=0&postorder=asc&highlight=). I fear there is a bug within the python machinery preventing the correct returning of the array to the spreadsheet cells. I have attached the package of the project as I use it. I do hope someone can diagnose and potentially fix this bug.
I can't even install your extension. That's because -by default- numpy isn't installed, at least not under windows [Win2K LibreOffice 3.4.1 OOO340m1 (Build:103)].
Created attachment 48713 [details] No numpy
Created attachment 48714 [details] a version of the addin without numpy this is a version of the add-in removing the numpy requirement.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
This bug is still present. Tested on Windows 7 and still receive the same error.
Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
Kurt: any update with last stable LO version 4.3.4 (which uses Python 3.3)
the problem still exists (Windows 8.1 Libreoffice 4.3.4.1)
Thank you Kurt for your feedback, I put it back to NEW.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.