org/
>>
>> Cheers,
>>
>> Pedro.
>
>
>Since PyPy is built on top of Python, I wonder how will that impact the gcc
>issue?
>
PyPy supports the C API so it should just work by using it as the external
python implementation. A quick google search would imply someone did i
ge you make make sure you take into account other
> platforms like OS/2 (yes, there´s an OS/2 port of OO) where Python
> does not come standard with the OS.
>
sure but we have to move forward and if a platform is not able to follow
with all features we always have the possibility to drop
2 (yes, there´s an OS/2 port of OO) where Python
does not come standard with the OS.
FC
On 03.08.2012 07:06, Pedro Giffuni wrote:
Hello guys;
FWIW, the update to version 2.7.3 doesnt really bring a big difference
wrt 2.6.1 but I dont think we will be able to update python further in
a long while because there are extensions out there that depend on
Python2.
It has the
On Fri, Aug 3, 2012 at 12:06 AM, Pedro Giffuni wrote:
> Hello guys;
>
> FWIW, the update to version 2.7.3 doesnt really bring a big difference wrt
> 2.6.1 but I dont think we will be able to update python further in a long
> while because there are extensions out there that de
Hello guys;
FWIW, the update to version 2.7.3 doesnt really bring a big difference wrt
2.6.1 but I dont think we will be able to update python further in a long while
because there are extensions out there that depend on Python2.
Adding Python3 compatibility is not difficult, I think, but an
On 02.08.2012 14:48, Alexandro Colorado wrote:
On 8/2/12, Alexandro Colorado wrote:
The issue was written on the UDK site explaining this issue.
http://www.openoffice.org/udk/python/python-bridge.html#faq
I already have python installed on my system, why does the office ship
another python
On 8/2/12, Alexandro Colorado wrote:
> The issue was written on the UDK site explaining this issue.
> http://www.openoffice.org/udk/python/python-bridge.html#faq
>
> I already have python installed on my system, why does the office ship
> another python ?
>
> Python i
The issue was written on the UDK site explaining this issue.
http://www.openoffice.org/udk/python/python-bridge.html#faq
I already have python installed on my system, why does the office ship
another python ?
Python itself is shipped with OpenOffice.org, because
python must have been compiled
Hi all,
Can anybody remind me of why we bring our own Python?
Are the reasons still valid after the update to 2.7.3?
I just updated main/external_deps.lst to load the tarball from
python.org and had almost chosen the windows binary instead of the
source tarball. I am now wondering why we
Hi Pedro,
I have got a build now too :)
Kind regards
Regina
Pedro Giffuni schrieb:
Thank you Tsutomu!
The other patches should also be used. I am not sure if dmake supports
the += operator so I just went back to the old patching method on
revision 1367616.
This is hopefully the last change
revision 1367616.
This is hopefully the last change there. Sorry to take you guys
as guinea pigs ;).
Pedro.
From: Tsutomu Uchino
To: ooo-dev@incubator.apache.org
Sent: Tuesday, July 31, 2012 8:57 AM
Subject: Re: trunk build fails, likely in python
Hi,
2012/7/31
With updating to revision 1367616, I can build python module successfully
in Windows XP. Thank you for your fixing.
On Tue, Jul 31, 2012 at 11:32 PM, Pedro Giffuni wrote:
> Thank you Tsutomu!
>
> The other patches should also be used. I am not sure if dmake supports
> the += operat
.
>
> From: Tsutomu Uchino
>To: ooo-dev@incubator.apache.org
>Sent: Tuesday, July 31, 2012 8:57 AM
>Subject: Re: trunk build fails, likely in python
>
>Hi,
>
>2012/7/31 Regina Henschel :
>> Hi Pedro,
>>
>> I still cannot build Python.
>>
Hi,
2012/7/31 Regina Henschel :
> Hi Pedro,
>
> I still cannot build Python.
>
> Messages are:
> dmake: Warning: -- Found file corresponding to virtual target
> [./wntmsci12/misc/build/Python-2.7.3/PC/pyconfig.h].
>
>
> Build started: Project: _ssl, Configuration:
Hi Pedro,
I still cannot build Python.
Messages are:
dmake: Warning: -- Found file corresponding to virtual target
[./wntmsci12/misc/build/Python-2.7.3/PC/pyconfig.h].
Build started: Project: _ssl, Configuration: Release|Win32
Performing Pre-Build Event...
Can not find a suitable PERL:
the
;Subject: Re: trunk build fails, likely in python
>
>Thank you.
>
>I will use this as an opportunity to do some further cleanup
>
>Pedro.
>
>
>
>>
>> From: Lin Yuan
>>To: ooo-dev@incubator.apache.org
>>Sent: Mond
Thank you.
I will use this as an opportunity to do some further cleanup
Pedro.
>
> From: Lin Yuan
>To: ooo-dev@incubator.apache.org
>Sent: Monday, July 30, 2012 8:26 PM
>Subject: Re: trunk build fails, likely in python
>
>I can reproduce
I can reproduce this issue on my Win 7.
In Python-2.7.3\PCbuild\pcbuild.sln, there are two projects related to
sqlite3. One named "sqlite3". Another named "_sqlite3". Both of them need
to be remarked. But in python-2.7.3.patch, it only remark project
"sqlite3". Need
Hi Armin,
I have rebased and deleted all the wbtmsci12*, then started a new build.
I now get the same error as you.
Kind regards
Regina
Armin Le Grand schrieb:
Hi,
just checked out current version and build stopped in python (win7).
Message is as follows.
Where does sqlite3.h come from
Uchino...
Thanks for the hints so far. More are of course welcome...
On 30.07.2012 18:38, Pedro Giffuni wrote:
FWIW,
One hint: googling around it looks like it's and issue when building a
debug python.
Pedro.
[..]
Sincerely,
Armin
--
ALG
...
Thanks for the hints so far. More are of course welcome...
On 30.07.2012 18:38, Pedro Giffuni wrote:
FWIW,
One hint: googling around it looks like it's and issue when building a
debug python.
Pedro.
[..]
around it looks like it's and issue when building a debug
python.
Pedro.
[..]
FWIW,
One hint: googling around it looks like it's and issue when building a debug
python.
Pedro.
>
> From: Armin Le Grand
>To: ooo-dev@incubator.apache.org
>Sent: Monday, July 30, 2012 11:02 AM
>Subject: Re: trunk build fails, lik
Hi Pedro,
Pedro Giffuni schrieb:
Hello Armin;
This builds cleanly on FreeBSD/linux , and apparently at least Regina got it to
build beyond python.
Yes, I get no longer errors in python.
Kind regards
Regina
Hi,
2012/7/31 Armin Le Grand :
> Hi,
>
> just checked out current version and build stopped in python (win7). Message
> is as follows.
>
> Where does sqlite3.h come from? There is a folder
> main\python\wntmsci12\misc\build\Python-2.7.3\Doc\includes\sqlite3 but no
> sqlit
Hello Armin;
This builds cleanly on FreeBSD/linux , and apparently at least Regina got it to
build beyond python.
That's pretty weird:
python-2.7.3.patch comments out the sqlite3 project for MSVC (just like
python-2.6.1.patch did before that).
I don't have a Windows build so I am
Hi,
just checked out current version and build stopped in python (win7).
Message is as follows.
Where does sqlite3.h come from? There is a folder
main\python\wntmsci12\misc\build\Python-2.7.3\Doc\includes\sqlite3 but
no sqlite3.h in there. Should it be there...?
Can someone help please
Thank you Regina!
That crept in from a previous patchset and I didn't notice (plus the buildbots
havent been building lately).
Fixed in r1366577, by removing the extra cruft in python/makefile.mk
Pedro.
--- Ven 27/7/12, Regina Henschel ha scritto:
Da: Regina Henschel
Oggetto: trunk
Hi,
I start a build on WinXP with MSVC Express. It fails with error message
dmake: Error: -- `./Python-2.7.3-vc.patch' not found, and can't be made
What do I miss?
Kind regards
Regina
Hi again;
My build with the more recent python has gone smoothly. FreeBSDhas been using
the system Python 2.7.3 by default for a while.
In addition to the general improvements there are also severalimportant
enhancements, this version also helps the build onnewer MacOS X and fixes
security
I solved the issue ... building now :).
>
>
>Thank you Ariel.
>
>I will see if I can split the patches according to the LF type to solve that
>issue :(.
>
>Pedro.
>
>>
>
>
Thank you Ariel.
I will see if I can split the patches according to the LF type to solve that
issue :(.
Pedro.
>
> From: Ariel Constenla-Haile
>To: ooo-dev@incubator.apache.org
>Sent: Wednesday, July 25, 2012 5:48 PM
>Subject: Re: Bug 119384
Hi Pedro,
On Wed, Jul 25, 2012 at 03:20:44PM -0700, Pedro Giffuni wrote:
> Hello guys;
>
> With some help from Hanya I have been slowly working on an update
> to our internal Python. The patch is rather big but it is necessary
> because:
>
> - The older 2.6.1 python is
Hello guys;
With some help from Hanya I have been slowly working on an update
to our internal Python. The patch is rather big but it is necessary
because:
- The older 2.6.1 python is basically unsupported upstream.
- Newer versions of python have better performance and solve
security issues
Hi Alexandre,
On Fri, May 18, 2012 at 01:06:47PM +0200, Alexandre Bezroutchko wrote:
> Hello,
>
> I am looking for a consultant to improve integration of my python
> extension code with UNO. Is this mailing list an appropriate place
> to post a detailed consultancy request? If
Hello,
I am looking for a consultant to improve integration of my python
extension code with UNO. Is this mailing list an appropriate place to
post a detailed consultancy request? If not, could you please advise
where should I post it? Thanks.
Best regards,
Alex
--
Alexandre Bezroutchko
Hi Yakov;
--- Sab 21/4/12, Yakov Reztsov ha scritto:
...
> I review Apache OpenOffice 3.4
> (incubating) release candidate 1 (RC1) is based on the svn
> revision 1327774 (Windows version)
>
> Python operator license() type Apache license in this
> version.
>
I am not
Am 20.10.2011 17:47, schrieb Alexandro Colorado:
> Wonder what is the future of the UNO scripting framework since there are
> many languages with different languages like Python, Beanshell and other
> scriptings that OOo ships. OOo builds have a full Python 2.6 version and
> also ID
Wonder what is the future of the UNO scripting framework since there are
many languages with different languages like Python, Beanshell and other
scriptings that OOo ships. OOo builds have a full Python 2.6 version and
also IDE like Rhino and other applications that are stringly attached to the
40 matches
Mail list logo