Am Mittwoch, 29. März 2017 um 15:52:22, schrieb José Abílio Matos
> On Wednesday, 29 March 2017 15.25.12 WEST Kornel Benko wrote:
> > > > There is one task remaining. Creation of lyxrc.defaults uses string
> > > > 'python' as executable even if lyx is configured for use with python3.
> >
> > > I
On Wednesday, 29 March 2017 15.25.12 WEST Kornel Benko wrote:
> > > There is one task remaining. Creation of lyxrc.defaults uses string
> > > 'python' as executable even if lyx is configured for use with python3.
>
> > I agree that this could change.
Actually here I meant to say not just that it
Am Mittwoch, 29. März 2017 um 14:50:46, schrieb José Abílio Matos
> On Wednesday, 29 March 2017 13.19.23 WEST Kornel Benko wrote:
> > So, should we make python3 be the default for lyx2.3?
>
> We want it to work as well as it works python 2. If it is the default or not
> I
> have no strong opin
On Wednesday, 29 March 2017 13.19.23 WEST Kornel Benko wrote:
> So, should we make python3 be the default for lyx2.3?
We want it to work as well as it works python 2. If it is the default or not I
have no strong opinion.
> There is one task remaining. Creation of lyxrc.defaults uses string 'pyt
Am Mittwoch, 29. März 2017 um 12:41:37, schrieb José Abílio Matos
> On Wednesday, 29 March 2017 12.14.29 WEST Kornel Benko wrote:
> > Export tests to previous lyx-versions using python3 are failing.
>
> It should be working now.
Yes, all 990 tests succeeded. (e.g. 'ctest -R '_lyx(16|21|22)$')
On Wednesday, 29 March 2017 12.14.29 WEST Kornel Benko wrote:
> Export tests to previous lyx-versions using python3 are failing.
It should be working now.
Using iteritems() returns an iterator while items() returns a list in python
2.
For python 3 items() returns and iterator and iteritems() do
Am Mittwoch, 29. März 2017 um 01:32:05, schrieb Scott Kostyshak
> On Tue, Mar 28, 2017 at 11:43:10AM +0100, José Abílio Matos wrote:
>
> > At the same time and do not expect pressure from the users who want to
> > convert
> > lyx-0.10 documents so I do no expect that Scott makes this a release
On Tue, Mar 28, 2017 at 11:43:10AM +0100, José Abílio Matos wrote:
> At the same time and do not expect pressure from the users who want to
> convert
> lyx-0.10 documents so I do no expect that Scott makes this a release blocker
> for 2.3. :-D
Thanks for the investigation on this issue, José.
On Tuesday, 28 March 2017 23.57.39 WEST José Abílio Matos wrote:
> FWIW the culprit seems to be normalize_font_whitespace in lyx_1_5.py, that
> is used for formats 259 and 274.
I found the reason.
In that function the is a variable called changes that is a dictionary. We
access to the list of ke
On Tuesday, 28 March 2017 15.07.17 WEST Jean-Marc Lasgouttes wrote:
> It looks like something that can be handled by a bisect, either a real
> one or a hand-made one where a dichotomy is done on the intermediate
> commits.
Nah... I prefer to follow Ken Thompson's advice:
"When in doubt, use brute
Le 28/03/2017 à 12:43, José Abílio Matos a écrit :
Using the 0.12.0 User Guide as the starting point the only differences between
the two conversions is that python 2 way gets at some points:
\bar default
\family default
while the python 3 gets
\family default
\bar default
This happens in 12
First the good news: after Georg's work we are almost there (99.999%). :-)
And now the fine details.
I have fixed #9006 that results in lyx2lyx working with python 3 for systems
where the system default encoding is not UTF-8.
Using the 0.12.0 User Guide as the starting point the only difference
12 matches
Mail list logo
