On 08.12.2010 22:43:06
b...@moolenaar.net wrote :
Can you please also write some text for the help about this?
I'll change the E999 to a valid number, we should have a tag in the help
file that explains the message.
In my yesterday's patch I have changed the E999 line in if_python.c and
Roland Puntaier wrote:
On 08.12.2010 22:43:06
b...@moolenaar.net wrote :
Can you please also write some text for the help about this?
I'll change the E999 to a valid number, we should have a tag in the help
file that explains the message.
In my yesterday's patch I have changed the
On 12.08.2010 06:33:07
James Vega james...@jamessan.com wrote:
On Tue, Aug 10, 2010 at 11:15:41PM +0200, Bram Moolenaar wrote:
A configure check would help to decide whether everything works
without
RTLD_GLOBAL global. If it does, then the current solution is best. If
it doesn't it might
Bram Moolenaar wrote:
I'll change the E999 to a valid number, we should have a tag in the help
file that explains the message.
Should each translator update the E999 in src/po/*.po files to the new
value or can it be done automatically?
Here are the po file which already contain E999:
$ cd
On 08.09.2010 22:02:50
b...@moolenaar.net wrote:
James Vega wrote:
On Mon, Aug 9, 2010 at 9:49 AM, Roland Puntaier
roland.punta...@br-automation.com wrote:
On Mon, 09 Aug 2010 13:49:43
Andy Kittner and...@gmx.de wrote:
I made the test in Vim 7.3: After removing RTLD_GLOBAL there
On 08.09.2010 22:02:48
b...@moolenaar.net wrote:
I would opt for the following:
If only one, Python 2.x xor Python 3.x, is configured (and if
DYNAMIC_PYTHON), then use RTLD_GLOBAL:
#define load_dll(n) dlopen((n), RTLD_LAZY|RTLD_GLOBAL)
If both are configured use without
Roland Puntaier wrote:
What do you suggest we do when RTLD_GLOBAL is needed? Disallow building
with two versions of Python? Or restrict use at runtime, as it is now?
We could add an option to switch using RTLD_GLOBAL on/off, but it's
really ugly. I would rather tell users to build two
Roland Puntaier wrote:
There are no differences apart from :py3 - :py[thon], and the discussed
consequences,
and the possible restrictions in python functionality, if both versions
are enabled, as discussed in this thread.
I had a look at the current documentation. You already mention
Roland Puntaier wrote:
Hello Bram,
sorry about my late response, first I was on holiday, then I was quite
busy.
I compared the vim7.3d sources to my original ones on Saturday.
Most of the functions are basically the same,
but I spotted a relevant difference:
I had:
#define
On Mon, Aug 09, 2010 at 12:58:20PM +0200, Bram Moolenaar wrote:
Roland Puntaier wrote:
Hello Bram,
sorry about my late response, first I was on holiday, then I was quite
busy.
I compared the vim7.3d sources to my original ones on Saturday.
Most of the functions are basically
On Mon, 09 Aug 2010 12:58:20 +0200
Bram Moolenaar b...@moolenaar.net wrote:
Roland Puntaier wrote:
... snip...
I made the test in Vim 7.3: After removing RTLD_GLOBAL there was no crash
any more.
If I'm not mistaken this flag was added to make import termios work.
Or something like
On Mon, 09 Aug 2010 13:49:43
Andy Kittner and...@gmx.de wrote:
I made the test in Vim 7.3: After removing RTLD_GLOBAL there wasno
crash
any more.
If I'm not mistaken this flag was added to make import termios work.
Or something like that.
The issue was that at least on some
On Mon, Aug 9, 2010 at 9:49 AM, Roland Puntaier
roland.punta...@br-automation.com wrote:
On Mon, 09 Aug 2010 13:49:43
Andy Kittner and...@gmx.de wrote:
I made the test in Vim 7.3: After removing RTLD_GLOBAL there wasno
crash
any more.
If I'm not mistaken this flag was added to make
James Vega wrote:
On Mon, Aug 9, 2010 at 9:49 AM, Roland Puntaier
roland.punta...@br-automation.com wrote:
On Mon, 09 Aug 2010 13:49:43
Andy Kittner and...@gmx.de wrote:
I made the test in Vim 7.3: After removing RTLD_GLOBAL there wasno
crash
any more.
If I'm not mistaken
Roland -
You have been quiet for a while. I still have the workaround that in
one Vim session one can only use either :python or :py3 to avoid
problems mixing the shared library. Is there a better solution? I hope
you can come up with something really soon, since we are getting very
close to
On Fri, Aug 6, 2010 at 3:16 PM, Bram Moolenaar b...@moolenaar.net wrote:
Roland -
You have been quiet for a while. I still have the workaround that in
one Vim session one can only use either :python or :py3 to avoid
problems mixing the shared library. Is there a better solution?
As far as
Datum: 25.07.2010 14:24
Betreff: Vim 7.3: Python3 support
Gesendet von: b...@moolenaar.net
Roland -
The Python 3 support has been included in Vim 7.3b. Please take a look
and verify recent changes didn't cause trouble.
We did encounter one serious problem: On Unix, when using
On Sat, Jul 17, 2010 at 3:28 PM, Bram Moolenaar b...@moolenaar.net wrote:
Roland Puntaier wrote:
No, Python 3.x is considered as another language. So most Python 2.x
scripts will not work under Python 3.x.
The patch has
:py3
for Python 3.x
and legacy
:py[thon]
for
James Vega wrote:
On Sat, Jul 17, 2010 at 3:28 PM, Bram Moolenaar b...@moolenaar.net wrote:
Roland Puntaier wrote:
No, Python 3.x is considered as another language. =A0So most Python 2.=
x
scripts will not work under Python 3.x.
The patch has
=A0 =A0 =A0 =A0 :py3
for Python
James Vega wrote:
On Mon, Jul 19, 2010 at 10:18 AM, James Vega james...@jamessan.com wrote:
On Sat, Jul 17, 2010 at 3:28 PM, Bram Moolenaar b...@moolenaar.net wrote:
Roland Puntaier wrote:
No, Python 3.x is considered as another language. Â So most Python 2.x
scripts will not work
Roland Puntaier wrote:
No, Python 3.x is considered as another language. So most Python 2.x
scripts will not work under Python 3.x.
The patch has
:py3
for Python 3.x
and legacy
:py[thon]
for Python 2.x.
Python 3.x is treated as another language.
Both Python
Hi,
On Thu, Apr 29, 2010 at 03:22:51PM +0200, Roland Puntaier wrote:
[..]
The patch has
:py3
for Python 3.x
and legacy
:py[thon]
for Python 2.x.
Python 3.x is treated as another language.
Both Python 2.x and Python 3.x can be supported at the same time, if vim
is configured
Roland Puntaier wrote:
since I had to set up windows I updated the patch for the python3 support
to vim trunk 7.2.411.
It is attached.
Thanks. I didn't hear about anybody using the patch. That might mean
it works without problems. Or that nobody uses it...
Who tested the Python 3
On Thu, Apr 29, 2010 at 20:27, Bram Moolenaar b...@moolenaar.net wrote:
Roland Puntaier wrote:
since I had to set up windows I updated the patch for the python3 support
to vim trunk 7.2.411.
It is attached.
Thanks. I didn't hear about anybody using the patch. That might mean
it works
vim_dev@googlegroups.com schrieb am 29.04.2010 14:59:57:
Edward L. Fox edy...@gmail.com
Gesendet von: vim_dev@googlegroups.com
On Thu, Apr 29, 2010 at 20:27, Bram Moolenaar b...@moolenaar.net
wrote:
Thanks. I didn't hear about anybody using the patch. That might mean
it works
25 matches
Mail list logo
