José == José Matos [EMAIL PROTECTED] writes:
José The right fix is to take some code from twisted,
José
http://twistedmatrix.com/trac/browser/trunk/twisted/python/compat.py?rev=14178format=txt
José So if os.walk is not defined we define it. Conversely, the right
José fix for configure.py is
> "José" == José Matos <[EMAIL PROTECTED]> writes:
José> The right fix is to take some code from twisted,
José>
http://twistedmatrix.com/trac/browser/trunk/twisted/python/compat.py?rev=14178=txt
José> So if os.walk is not defined we define it. Conversely, the right
José> fix for
On Wednesday 20 September 2006 13:57, Rainer Dorsch wrote:
José,
did you apply this patch. I compiled 1.4.3svn and still get
Checking whether TeX allows spaces in file names...
Traceback (most recent call last):
File
/afs/bb/data/d3197/galaxy2/zLinux/lyx-1.4.3pre/share/lyx/configure.py,
José == José Matos [EMAIL PROTECTED] writes:
José The patch I sent has this issue fixed. I send the patch again
José attached. The patch is against the latest svn version.
José Could you try and see if the attached patch works. It is the
José only way to ask Jean-Marc to included it in the
Jean-Marc Lasgouttes wrote:
José == José Matos [EMAIL PROTECTED] writes:
José The patch I sent has this issue fixed. I send the patch again
José attached. The patch is against the latest svn version.
José Could you try and see if the attached patch works. It is the
José only way to ask
Stephan == Stephan Witt [EMAIL PROTECTED] writes:
Stephan Jean-Marc Lasgouttes wrote:
José == José Matos [EMAIL PROTECTED] writes:
José The patch I sent has this issue fixed. I send the patch again
José attached. The patch is against the latest svn version.
José Could you try and see if the
Jean-Marc Lasgouttes wrote:
José == José Matos [EMAIL PROTECTED] writes:
José The patch I sent has this issue fixed. I send the patch again
José attached. The patch is against the latest svn version.
José Could you try and see if the attached patch works. It is the
José only way to ask
On Thursday 21 September 2006 10:01, Jean-Marc Lasgouttes wrote:
Thanks. Jose', please apply.
I will do it Jean-Marc.
Suse (I always forget the proper capitalisation) 8.1 was released in October
2002, the same applies to Redhat 8.0. Both distributions support python 2.2.
Debian 3.0
José Matos wrote:
Suse (I always forget the proper capitalisation)
Novell also ;-)
Jürgen
On Thursday 21 September 2006 10:08, Stephan Witt wrote:
I've just detected another phyton problem.
The script lib/scripts/TeXFiles.py failed with
AttributeError: 'module' object has no attribute 'walk'
Indexing files of type cls
Traceback (most recent call last):
File
José == José Matos [EMAIL PROTECTED] writes:
José Given this, I think that we can raise the bar and require
José python 2.2 (2.1.3 if really necessary) for lyx 1.4.x. What do
José you think?
I can agree with that. I think we should have decided that for 1.4.0,
actually.
JMarc
On Thursday 21 September 2006 10:01, Jean-Marc Lasgouttes wrote:
Thanks. Jose', please apply.
I committed the patch. But I did not change status.14x, where should this
entry go?
JMarc
--
José Abílio
José == José Matos [EMAIL PROTECTED] writes:
José On Thursday 21 September 2006 10:01, Jean-Marc Lasgouttes wrote:
Thanks. Jose', please apply.
José I committed the patch. But I did not change status.14x, where
José should this entry go?
In the misc section at the end. You should document
On Thursday 21 September 2006 12:00, Jean-Marc Lasgouttes wrote:
In the misc section at the end. You should document that we require
2.2 now (in README and INSTALL).
Something like the following attached patch?
We should also rework the test in configure.ac from
# Check for installed
José == José Matos [EMAIL PROTECTED] writes:
José On Thursday 21 September 2006 12:00, Jean-Marc Lasgouttes wrote:
In the misc section at the end. You should document that we
require 2.2 now (in README and INSTALL).
José Something like the following attached patch?
Yes.
José We should
On Thursday 21 September 2006 12:57, Jean-Marc Lasgouttes wrote:
José Something like the following attached patch?
Yes.
Committed with the corresponding Changelog entry.
José We should also rework the test in configure.ac from # Check
José for installed python AM_PATH_PYTHON(1.5.2,,
José == José Matos [EMAIL PROTECTED] writes:
José On Thursday 21 September 2006 12:57, Jean-Marc Lasgouttes wrote:
José Something like the following attached patch?
Yes.
José Committed with the corresponding Changelog entry.
Good boy.
JMarc
On Thursday 21 September 2006 10:08, Stephan Witt wrote:
I've just detected another phyton problem.
The script lib/scripts/TeXFiles.py failed with
Indexing files of type cls
Traceback (most recent call last):
File /home/witt/src/lyx/lyx-1.4.x/lib/scripts/TeXFiles.py, line 110,
in ? for
On Wednesday 20 September 2006 13:57, Rainer Dorsch wrote:
> José,
>
> did you apply this patch. I compiled 1.4.3svn and still get
>
> Checking whether TeX allows spaces in file names...
> Traceback (most recent call last):
>
> File
>
> "José" == José Matos <[EMAIL PROTECTED]> writes:
José> The patch I sent has this issue fixed. I send the patch again
José> attached. The patch is against the latest svn version.
José> Could you try and see if the attached patch works. It is the
José> only way to ask Jean-Marc to
Jean-Marc Lasgouttes wrote:
"José" == José Matos <[EMAIL PROTECTED]> writes:
José> The patch I sent has this issue fixed. I send the patch again
José> attached. The patch is against the latest svn version.
José> Could you try and see if the attached patch works. It is the
José> only way
> "Stephan" == Stephan Witt <[EMAIL PROTECTED]> writes:
Stephan> Jean-Marc Lasgouttes wrote:
>>> "José" == José Matos <[EMAIL PROTECTED]> writes:
>>
José> The patch I sent has this issue fixed. I send the patch again
José> attached. The patch is against the latest svn version.
>>
José>
Jean-Marc Lasgouttes wrote:
"José" == José Matos <[EMAIL PROTECTED]> writes:
José> The patch I sent has this issue fixed. I send the patch again
José> attached. The patch is against the latest svn version.
José> Could you try and see if the attached patch works. It is the
José> only way
On Thursday 21 September 2006 10:01, Jean-Marc Lasgouttes wrote:
> Thanks. Jose', please apply.
I will do it Jean-Marc.
Suse (I always forget the proper capitalisation) 8.1 was released in October
2002, the same applies to Redhat 8.0. Both distributions support python 2.2.
Debian 3.0
José Matos wrote:
> Suse (I always forget the proper capitalisation)
Novell also ;-)
Jürgen
On Thursday 21 September 2006 10:08, Stephan Witt wrote:
>
> I've just detected another phyton problem.
> The script lib/scripts/TeXFiles.py failed with
>
> AttributeError: 'module' object has no attribute 'walk'
> Indexing files of type cls
> Traceback (most recent call last):
>File
> "José" == José Matos <[EMAIL PROTECTED]> writes:
José> Given this, I think that we can raise the bar and require
José> python 2.2 (2.1.3 if really necessary) for lyx 1.4.x. What do
José> you think?
I can agree with that. I think we should have decided that for 1.4.0,
actually.
JMarc
On Thursday 21 September 2006 10:01, Jean-Marc Lasgouttes wrote:
> Thanks. Jose', please apply.
I committed the patch. But I did not change status.14x, where should this
entry go?
> JMarc
--
José Abílio
> "José" == José Matos <[EMAIL PROTECTED]> writes:
José> On Thursday 21 September 2006 10:01, Jean-Marc Lasgouttes wrote:
>> Thanks. Jose', please apply.
José> I committed the patch. But I did not change status.14x, where
José> should this entry go?
In the misc section at the end. You
On Thursday 21 September 2006 12:00, Jean-Marc Lasgouttes wrote:
>
> In the misc section at the end. You should document that we require
> 2.2 now (in README and INSTALL).
Something like the following attached patch?
We should also rework the test in configure.ac from
# Check for installed
> "José" == José Matos <[EMAIL PROTECTED]> writes:
José> On Thursday 21 September 2006 12:00, Jean-Marc Lasgouttes wrote:
>> In the misc section at the end. You should document that we
>> require 2.2 now (in README and INSTALL).
José> Something like the following attached patch?
Yes.
On Thursday 21 September 2006 12:57, Jean-Marc Lasgouttes wrote:
> José> Something like the following attached patch?
>
> Yes.
Committed with the corresponding Changelog entry.
> José> We should also rework the test in configure.ac from # Check
> José> for installed python
> "José" == José Matos <[EMAIL PROTECTED]> writes:
José> On Thursday 21 September 2006 12:57, Jean-Marc Lasgouttes wrote:
José> Something like the following attached patch?
>> Yes.
José> Committed with the corresponding Changelog entry.
Good boy.
JMarc
On Thursday 21 September 2006 10:08, Stephan Witt wrote:
> I've just detected another phyton problem.
> The script lib/scripts/TeXFiles.py failed with
>
> Indexing files of type cls
> Traceback (most recent call last):
>File "/home/witt/src/lyx/lyx-1.4.x/lib/scripts/TeXFiles.py", line 110,
>
José,
did you apply this patch. I compiled 1.4.3svn and still get
Checking whether TeX allows spaces in file names...
Traceback (most recent call last):
File /afs/bb/data/d3197/galaxy2/zLinux/lyx-1.4.3pre/share/lyx/configure.py,
line 730, in ?
checkTeXAllowSpaces()
File
José,
did you apply this patch. I compiled 1.4.3svn and still get
Checking whether TeX allows spaces in file names...
Traceback (most recent call last):
File "/afs/bb/data/d3197/galaxy2/zLinux/lyx-1.4.3pre/share/lyx/configure.py",
line 730, in ?
checkTeXAllowSpaces()
File
On Friday 15 September 2006 21:52, Jean-Marc Lasgouttes wrote:
Yes.
Do you think that it is worth to revert to 1.5.2 support?
I can do it if you want to. :-)
JMarc
--
José Abílio
On Friday 15 September 2006 21:52, Jean-Marc Lasgouttes wrote:
> Yes.
Do you think that it is worth to revert to 1.5.2 support?
I can do it if you want to. :-)
> JMarc
--
José Abílio
José,
thanks for the patch.
I could not apply the patch using the patch command, you apparently generated
it for a different version of configure.py.
I applied it manually and it worked, configure runs now thorugh.
How do I know when your two patches are applied to the 1.4.x tree, such that
On Friday 15 September 2006 10:36, Rainer Dorsch wrote:
José,
thanks for the patch.
I could not apply the patch using the patch command, you apparently
generated it for a different version of configure.py.
I have used the version that will become lyx-1.4.3
I applied it manually and it
José == José Matos [EMAIL PROTECTED] writes:
José I am CC'ing this message to Jean-Marc the release coordinator
José of the stable version.
José With the proposed patch for configure.py lyx requires a python
José version between 2.0 and 2.2.1.
José May I apply the patch to lyx-1.4.3?
Enrico == Enrico Forestieri [EMAIL PROTECTED] writes:
Enrico according to Rainer Dorsch the attached patch let LyX compile
Enrico again with qt3.0. Please let me know if I can apply it to
Enrico 1.4.x.
The change in toqstr should be conditionned on qt version too. Using
fromLatin1 defeats the
On Fri, Sep 15, 2006 at 02:06:09PM +0200, Jean-Marc Lasgouttes wrote:
Enrico == Enrico Forestieri [EMAIL PROTECTED] writes:
Enrico according to Rainer Dorsch the attached patch let LyX compile
Enrico again with qt3.0. Please let me know if I can apply it to
Enrico 1.4.x.
The change in
On Friday 15 September 2006 13:02, Jean-Marc Lasgouttes wrote:
Hmm, I see in README that we say python 1.5. If it is 2.x, we should
say so. The patches I have seen discussed are definitely OK anyway.
Is configure.py used for all users?
--
José Abílio
José == José Matos [EMAIL PROTECTED] writes:
José On Friday 15 September 2006 13:02, Jean-Marc Lasgouttes wrote:
Hmm, I see in README that we say python 1.5. If it is 2.x, we
should say so. The patches I have seen discussed are definitely OK
anyway.
José Is configure.py used for all users?
José,
thanks for the patch.
I could not apply the patch using the patch command, you apparently generated
it for a different version of configure.py.
I applied it manually and it worked, configure runs now thorugh.
How do I know when your two patches are applied to the 1.4.x tree, such that
On Friday 15 September 2006 10:36, Rainer Dorsch wrote:
> José,
>
> thanks for the patch.
>
> I could not apply the patch using the patch command, you apparently
> generated it for a different version of configure.py.
I have used the version that will become lyx-1.4.3
> I applied it manually
> "José" == José Matos <[EMAIL PROTECTED]> writes:
José> I am CC'ing this message to Jean-Marc the release coordinator
José> of the stable version.
José> With the proposed patch for configure.py lyx requires a python
José> version between 2.0 and 2.2.1.
José> May I apply the patch to
> "Enrico" == Enrico Forestieri <[EMAIL PROTECTED]> writes:
Enrico> according to Rainer Dorsch the attached patch let LyX compile
Enrico> again with qt3.0. Please let me know if I can apply it to
Enrico> 1.4.x.
The change in toqstr should be conditionned on qt version too. Using
fromLatin1
On Fri, Sep 15, 2006 at 02:06:09PM +0200, Jean-Marc Lasgouttes wrote:
> > "Enrico" == Enrico Forestieri <[EMAIL PROTECTED]> writes:
>
> Enrico> according to Rainer Dorsch the attached patch let LyX compile
> Enrico> again with qt3.0. Please let me know if I can apply it to
> Enrico> 1.4.x.
>
On Friday 15 September 2006 13:02, Jean-Marc Lasgouttes wrote:
> Hmm, I see in README that we say python 1.5. If it is 2.x, we should
> say so. The patches I have seen discussed are definitely OK anyway.
Is configure.py used for all users?
--
José Abílio
> "José" == José Matos <[EMAIL PROTECTED]> writes:
José> On Friday 15 September 2006 13:02, Jean-Marc Lasgouttes wrote:
>> Hmm, I see in README that we say python 1.5. If it is 2.x, we
>> should say so. The patches I have seen discussed are definitely OK
>> anyway.
José> Is configure.py
On Wed, Sep 13, 2006 at 12:42:01PM +0200, Jean-Marc Lasgouttes wrote:
Rainer == Rainer Dorsch [EMAIL PROTECTED] writes:
Rainer So that means lyx 1.4.2 does not support qt 3.0.x, right?
Rainer If yes, someone should update the README for 1.4.3. It says
Rainer that even QT2 might be
Enrico Forestieri [EMAIL PROTECTED] writes:
| Then there's an issue with the required minimum version of python
| but I think that Josè can handle it.
It is not unlikely that we have to up the requirement a bit more for
1.5. Lyx2lyx conversion of the latexaccent really wants to use the
Lars Gullik Bjønnes wrote:
Enrico Forestieri [EMAIL PROTECTED] writes:
| Then there's an issue with the required minimum version of python
| but I think that Josè can handle it.
That issue was an invalid .lyx file as it turned out.
It is not unlikely that we have to up the requirement a
On Thursday 14 September 2006 09:17, Lars Gullik Bjønnes wrote:
It is not unlikely that we have to up the requirement a bit more for
1.5. Lyx2lyx conversion of the latexaccent really wants to use the
unicodedata module and its normalize function, that was new in 2.3.
We have discussed that
On Thu, Sep 14, 2006 at 10:27:02AM +0200, Georg Baum wrote:
Lars Gullik Bjønnes wrote:
Enrico Forestieri [EMAIL PROTECTED] writes:
| Then there's an issue with the required minimum version of python
| but I think that Josè can handle it.
That issue was an invalid .lyx file as it
José Matos [EMAIL PROTECTED] writes:
| On Thursday 14 September 2006 09:17, Lars Gullik Bjønnes wrote:
| It is not unlikely that we have to up the requirement a bit more for
| 1.5. Lyx2lyx conversion of the latexaccent really wants to use the
| unicodedata module and its normalize function,
On Thursday 14 September 2006 09:54, Lars Gullik Bjønnes wrote:
Good. I saw you mention 2.2 here the other day and assumed (I know...)
that to be the requirement.
Use the source Luke. (I always wanted to say that. ;-) )
One pity with python of corse is that is is 16-bit unicode only.
It
José Matos [EMAIL PROTECTED] writes:
| On Thursday 14 September 2006 09:54, Lars Gullik Bjønnes wrote:
| Good. I saw you mention 2.2 here the other day and assumed (I know...)
| that to be the requirement.
|
| Use the source Luke. (I always wanted to say that. ;-) )
|
| One pity with
On Thursday 14 September 2006 11:08, Lars Gullik Bjønnes wrote:
Yeah. But python module unicode data is using Unicode-3.2. The latest
Unicode standard is now at 5.0.
Come on Lars, that is unfair. ;-)
python 2.5 that will come in a week or so supports Unicode 4.1.
José Matos [EMAIL PROTECTED] writes:
| On Thursday 14 September 2006 11:08, Lars Gullik Bjønnes wrote:
| Yeah. But python module unicode data is using Unicode-3.2. The latest
| Unicode standard is now at 5.0.
|
| Come on Lars, that is unfair. ;-)
|
| python 2.5 that will come in a week or
On Thursday 14 September 2006 11:28, Lars Gullik Bjønnes wrote:
| You should not expect for python to support unreleased unicode specs at
| the time it is released. :-)
in a week. 5.0 is already released (for some month now. AFAIK)
Aha, python 2.5 was frozen in June/July, as release
On Thursday 14 September 2006 09:54, Lars Gullik Bjønnes wrote:
One pity with python of corse is that is is 16-bit unicode only.
OK. Just to be sure one test is:
$ python -c import sys; print (sys.maxunicode 66000) and 'UCS2' or 'UCS4'
As expected I get
UCS4
--
Lgb
--
José
José,
that brings me further:
+checking for graphics driver... default
+checking for package psnfss [times.sty]... yes
+Inspection done.
+Read the file doc/LaTeXConfig.lyx for more information.
Traceback (most recent call last):
File /opt/lyx-1.4.2/share/lyx/configure.py, line 710, in ?
On Thursday 14 September 2006 21:59, Rainer Dorsch wrote:
Any ideas here?
Yes, this method was implemented in python 2.2.2 and you 2.2.1. :-D
I attach a patch that fixes yesterday problem and another similar as well.
Please apply to the original file.
Thanks,
Rainer
--
José Abílio
On Wed, Sep 13, 2006 at 12:42:01PM +0200, Jean-Marc Lasgouttes wrote:
> > "Rainer" == Rainer Dorsch <[EMAIL PROTECTED]> writes:
>
> Rainer> So that means lyx 1.4.2 does not support qt 3.0.x, right?
>
> Rainer> If yes, someone should update the README for 1.4.3. It says
> Rainer> that even
Enrico Forestieri <[EMAIL PROTECTED]> writes:
| Then there's an issue with the required minimum version of python
| but I think that Josè can handle it.
It is not unlikely that we have to up the requirement a bit more for
1.5. Lyx2lyx conversion of the latexaccent really wants to use the
Lars Gullik Bjønnes wrote:
> Enrico Forestieri <[EMAIL PROTECTED]> writes:
>
> | Then there's an issue with the required minimum version of python
> | but I think that Josè can handle it.
That issue was an invalid .lyx file as it turned out.
> It is not unlikely that we have to up the
On Thursday 14 September 2006 09:17, Lars Gullik Bjønnes wrote:
> It is not unlikely that we have to up the requirement a bit more for
> 1.5. Lyx2lyx conversion of the latexaccent really wants to use the
> unicodedata module and its normalize function, that was new in 2.3.
We have discussed
On Thu, Sep 14, 2006 at 10:27:02AM +0200, Georg Baum wrote:
> Lars Gullik Bjønnes wrote:
>
> > Enrico Forestieri <[EMAIL PROTECTED]> writes:
> >
> > | Then there's an issue with the required minimum version of python
> > | but I think that Josè can handle it.
>
> That issue was an invalid .lyx
José Matos <[EMAIL PROTECTED]> writes:
| On Thursday 14 September 2006 09:17, Lars Gullik Bjønnes wrote:
| > It is not unlikely that we have to up the requirement a bit more for
| > 1.5. Lyx2lyx conversion of the latexaccent really wants to use the
| > unicodedata module and its normalize
On Thursday 14 September 2006 09:54, Lars Gullik Bjønnes wrote:
> Good. I saw you mention 2.2 here the other day and assumed (I know...)
> that to be the requirement.
Use the source Luke. (I always wanted to say that. ;-) )
> One pity with python of corse is that is is 16-bit unicode only.
José Matos <[EMAIL PROTECTED]> writes:
| On Thursday 14 September 2006 09:54, Lars Gullik Bjønnes wrote:
| > Good. I saw you mention 2.2 here the other day and assumed (I know...)
| > that to be the requirement.
|
| Use the source Luke. (I always wanted to say that. ;-) )
|
| > One pity with
On Thursday 14 September 2006 11:08, Lars Gullik Bjønnes wrote:
> Yeah. But python module unicode data is using Unicode-3.2. The latest
> Unicode standard is now at 5.0.
Come on Lars, that is unfair. ;-)
python 2.5 that will come in a week or so supports Unicode 4.1.
José Matos <[EMAIL PROTECTED]> writes:
| On Thursday 14 September 2006 11:08, Lars Gullik Bjønnes wrote:
| > Yeah. But python module unicode data is using Unicode-3.2. The latest
| > Unicode standard is now at 5.0.
|
| Come on Lars, that is unfair. ;-)
|
| python 2.5 that will come in a
On Thursday 14 September 2006 11:28, Lars Gullik Bjønnes wrote:
> | You should not expect for python to support unreleased unicode specs at
> | the time it is released. :-)
>
> "in a week". 5.0 is already released (for some month now. AFAIK)
Aha, python 2.5 was frozen in June/July, as release
On Thursday 14 September 2006 09:54, Lars Gullik Bjønnes wrote:
> One pity with python of corse is that is is 16-bit unicode only.
OK. Just to be sure one test is:
$ python -c "import sys; print (sys.maxunicode < 66000) and 'UCS2' or 'UCS4'"
As expected I get
UCS4
> --
> Lgb
--
José,
that brings me further:
+checking for graphics driver... default
+checking for package psnfss [times.sty]... yes
+Inspection done.
+Read the file doc/LaTeXConfig.lyx for more information.
Traceback (most recent call last):
File "/opt/lyx-1.4.2/share/lyx/configure.py", line 710, in ?
On Thursday 14 September 2006 21:59, Rainer Dorsch wrote:
> Any ideas here?
Yes, this method was implemented in python 2.2.2 and you 2.2.1. :-D
I attach a patch that fixes yesterday problem and another similar as well.
Please apply to the original file.
> Thanks,
> Rainer
--
José Abílio
Rainer == Rainer Dorsch [EMAIL PROTECTED] writes:
Rainer So that means lyx 1.4.2 does not support qt 3.0.x, right?
Rainer If yes, someone should update the README for 1.4.3. It says
Rainer that even QT2 might be supported though untested. This would
Rainer mean at least qt=3.1 is required.
I
Am Mittwoch, 13. September 2006 12:42 schrieb Jean-Marc Lasgouttes:
Rainer == Rainer Dorsch [EMAIL PROTECTED] writes:
Rainer So that means lyx 1.4.2 does not support qt 3.0.x, right?
Rainer If yes, someone should update the README for 1.4.3. It says
Rainer that even QT2 might be supported
On Wed, Sep 13, 2006 at 04:07:12PM +0200, Rainer Dorsch wrote:
LyX comes up after that, but I get an error reported:
Checking whether TeX allows spaces in file names...
Traceback (most recent call last):
File /afs/bb/data/d3197/galaxy2/zLinux/lyx-1.4.2/share/lyx/configure.py,
line 705,
On Wednesday 13 September 2006 15:07, Rainer Dorsch wrote:
LyX comes up after that, but I get an error reported:
Checking whether TeX allows spaces in file names...
Traceback (most recent call last):
File
/afs/bb/data/d3197/galaxy2/zLinux/lyx-1.4.2/share/lyx/configure.py, line
705, in ?
Am Mittwoch, 13. September 2006 19:57 schrieb José Matos:
On Wednesday 13 September 2006 15:07, Rainer Dorsch wrote:
LyX comes up after that, but I get an error reported:
Checking whether TeX allows spaces in file names...
Traceback (most recent call last):
File
On Wednesday 13 September 2006 20:19, Rainer Dorsch wrote:
[EMAIL PROTECTED]:~ python -V
Python 2.2.1
[EMAIL PROTECTED]:~
Does not look bad (?)
Nope it is fine. :-)
I found the reference to this in http://docs.python.org/lib/typesseq.html
(1)
When s is a string or Unicode string object
> "Rainer" == Rainer Dorsch <[EMAIL PROTECTED]> writes:
Rainer> So that means lyx 1.4.2 does not support qt 3.0.x, right?
Rainer> If yes, someone should update the README for 1.4.3. It says
Rainer> that even QT2 might be supported though untested. This would
Rainer> mean at least qt>=3.1 is
Am Mittwoch, 13. September 2006 12:42 schrieb Jean-Marc Lasgouttes:
> > "Rainer" == Rainer Dorsch <[EMAIL PROTECTED]> writes:
>
> Rainer> So that means lyx 1.4.2 does not support qt 3.0.x, right?
>
> Rainer> If yes, someone should update the README for 1.4.3. It says
> Rainer> that even QT2
On Wed, Sep 13, 2006 at 04:07:12PM +0200, Rainer Dorsch wrote:
> LyX comes up after that, but I get an error reported:
>
> Checking whether TeX allows spaces in file names...
> Traceback (most recent call last):
> File "/afs/bb/data/d3197/galaxy2/zLinux/lyx-1.4.2/share/lyx/configure.py",
>
On Wednesday 13 September 2006 15:07, Rainer Dorsch wrote:
> LyX comes up after that, but I get an error reported:
>
> Checking whether TeX allows spaces in file names...
> Traceback (most recent call last):
> File
> "/afs/bb/data/d3197/galaxy2/zLinux/lyx-1.4.2/share/lyx/configure.py", line
>
Am Mittwoch, 13. September 2006 19:57 schrieb José Matos:
> On Wednesday 13 September 2006 15:07, Rainer Dorsch wrote:
> > LyX comes up after that, but I get an error reported:
> >
> > Checking whether TeX allows spaces in file names...
> > Traceback (most recent call last):
> > File
> >
On Wednesday 13 September 2006 20:19, Rainer Dorsch wrote:
> [EMAIL PROTECTED]:~> python -V
> Python 2.2.1
> [EMAIL PROTECTED]:~>
>
> Does not look bad (?)
Nope it is fine. :-)
I found the reference to this in http://docs.python.org/lib/typesseq.html
(1)
When s is a string or Unicode string
Am Montag, 11. September 2006 23:23 schrieb Enrico Forestieri:
On Mon, Sep 11, 2006 at 08:00:21PM +0200, Rainer Dorsch wrote:
Hello,
I tried to compile lyx 1.4.2 with QT 3.0.5 using
$ ./configure --prefix /opt/lyx-1.4.2 --with-frontend=qt
--with-qt-dir=/usr/lib/qt-3.0.5
$ make
On Tuesday 12 September 2006 11:35, Rainer Dorsch wrote:
So that means lyx 1.4.2 does not support qt 3.0.x, right?
I think so.
The question now is if this is the only place where this happens or if there
are others.
If you run with make -k where are there other places in code where you
On Tuesday 12 September 2006 11:51, José Matos wrote:
So if you can support qt 3.0 with very few effort we should do it. :-)
Sorry I meant *we* not *you*.
My point is that there are several places in code where we test for qt 3.1
and for some reason that chunk avoided that check.
If
José,
I found another issue when running make -k:
g++ -DHAVE_CONFIG_H -I. -I. -I../../../src -DQT_CLEAN_NAMESPACE
-DQT_GENUINE_STR -DQT_NO_STL -DQT_THREAD_SUPPORT -I../../../src -I../../../s\
rc/frontends -I../../../images -I/usr/lib/qt-3.0.5//include -I../../../boost
On Tue, Sep 12, 2006 at 02:12:01PM +0200, Rainer Dorsch wrote:
g++ -DHAVE_CONFIG_H -I. -I. -I../../../src -DQT_CLEAN_NAMESPACE
-DQT_GENUINE_STR -DQT_NO_STL -DQT_THREAD_SUPPORT -I../../../src -I../../../s\
rc/frontends -I../../../images -I/usr/lib/qt-3.0.5//include -I../../../boost
Am Montag, 11. September 2006 23:23 schrieb Enrico Forestieri:
> On Mon, Sep 11, 2006 at 08:00:21PM +0200, Rainer Dorsch wrote:
> > Hello,
> >
> > I tried to compile lyx 1.4.2 with QT 3.0.5 using
> >
> > $ ./configure --prefix /opt/lyx-1.4.2 --with-frontend=qt
> > --with-qt-dir=/usr/lib/qt-3.0.5
>
On Tuesday 12 September 2006 11:35, Rainer Dorsch wrote:
> So that means lyx 1.4.2 does not support qt 3.0.x, right?
I think so.
The question now is if this is the only place where this happens or if there
are others.
If you run with make -k where are there other places in code where you
On Tuesday 12 September 2006 11:51, José Matos wrote:
> So if you can support qt 3.0 with very few effort we should do it. :-)
Sorry I meant *we* not *you*.
My point is that there are several places in code where we test for qt < 3.1
and for some reason that chunk avoided that check.
1 - 100 of 106 matches
Mail list logo
