Re: Bibliography and Python
On Thursday 22 February 2007 10:03:25 pm Uwe Stöhr wrote: Bill Wood schrieb: Am I correct in inferring that Python 2.5 is required for LyX 1.4.4? At least Python 2.3 is needed. The installer comes with Python but this is only used if you haven't already Python installed. The minimum requirement for lyx-1.4.4 is python 2.2, we even have that in the release notes. :-) regards Uwe -- José Abílio
Re: Bibliography and Python
On Thursday 22 February 2007 10:03:25 pm Uwe Stöhr wrote: Bill Wood schrieb: Am I correct in inferring that Python 2.5 is required for LyX 1.4.4? At least Python 2.3 is needed. The installer comes with Python but this is only used if you haven't already Python installed. The minimum requirement for lyx-1.4.4 is python 2.2, we even have that in the release notes. :-) regards Uwe -- José Abílio
Re: Bibliography and Python
On Thursday 22 February 2007 10:03:25 pm Uwe Stöhr wrote: > Bill Wood schrieb: > > Am I correct in inferring that Python 2.5 is required for LyX 1.4.4? > > At least Python 2.3 is needed. The installer comes with Python but this is > only used if you haven't already Python installed. The minimum requirement for lyx-1.4.4 is python 2.2, we even have that in the release notes. :-) > regards Uwe -- José Abílio
Re: Bibliography and Python
I have a Full Python 2.5 installation on my computer, so that's not the problem. I created the folder and added the Python script, reconfigured LyX... Nothing... Same error. Uninstalled LyX and reinstalled it with the Small Version of your latest installer (2.11)... Nothing... Same error... Another tip? On 2/22/07, Uwe Stöhr [EMAIL PROTECTED] wrote: Julio Rojas schrieb: Is Lib a folder? I don't have it on my installation. When you don't have a folder c:\program files\LyX1.4.4\bin\Lib\ on your system, then you also not have a python.exe in the folder c:\program files\LyX1.4.4\bin\ Right? If yes, you already have a Python installation on your computer. Try to upgrade your Python installation to Python 2.5 and then reconfigure LyX. Under what name should I copy the attached text? Sorry, I attached this as python file named __future__.py. It is attached again, I hope this time it work. regards Uwe Record of phased-in incompatible language changes. Each line is of the form: FeatureName = _Feature( OptionalRelease , MandatoryRelease , CompilerFlag ) where, normally, OptionalRelease MandatoryRelease, and both are 5-tuples of the same form as sys.version_info: (PY_MAJOR_VERSION, # the 2 in 2.1.0a3; an int PY_MINOR_VERSION, # the 1; an int PY_MICRO_VERSION, # the 0; an int PY_RELEASE_LEVEL, # alpha, beta, candidate or final; string PY_RELEASE_SERIAL # the 3; an int ) OptionalRelease records the first release in which from __future__ import FeatureName was accepted. In the case of MandatoryReleases that have not yet occurred, MandatoryRelease predicts the release in which the feature will become part of the language. Else MandatoryRelease records when the feature became part of the language; in releases at or after that, modules no longer need from __future__ import FeatureName to use the feature in question, but may continue to use such imports. MandatoryRelease may also be None, meaning that a planned feature got dropped. Instances of class _Feature have two corresponding methods, .getOptionalRelease() and .getMandatoryRelease(). CompilerFlag is the (bitfield) flag that should be passed in the fourth argument to the builtin function compile() to enable the feature in dynamically compiled code. This flag is stored in the .compiler_flag attribute on _Future instances. These values must match the appropriate #defines of CO_xxx flags in Include/compile.h. No feature line is ever to be deleted from this file. all_feature_names = [ nested_scopes, generators, division, absolute_import, with_statement, ] __all__ = [all_feature_names] + all_feature_names # The CO_xxx symbols are defined here under the same names used by # compile.h, so that an editor search will find them here. However, # they're not exported in __all__, because they don't really belong to # this module. CO_NESTED= 0x0010 # nested_scopes CO_GENERATOR_ALLOWED = 0# generators (obsolete, was 0x1000) CO_FUTURE_DIVISION = 0x2000 # division CO_FUTURE_ABSOLUTE_IMPORT = 0x4000 # perform absolute imports by default CO_FUTURE_WITH_STATEMENT = 0x8000 # with statement class _Feature: def __init__(self, optionalRelease, mandatoryRelease, compiler_flag): self.optional = optionalRelease self.mandatory = mandatoryRelease self.compiler_flag = compiler_flag def getOptionalRelease(self): Return first release in which this feature was recognized. This is a 5-tuple, of the same form as sys.version_info. return self.optional def getMandatoryRelease(self): Return release in which this feature will become mandatory. This is a 5-tuple, of the same form as sys.version_info, or, if the feature was dropped, is None. return self.mandatory def __repr__(self): return _Feature + repr((self.optional, self.mandatory, self.compiler_flag)) nested_scopes = _Feature((2, 1, 0, beta, 1), (2, 2, 0, alpha, 0), CO_NESTED) generators = _Feature((2, 2, 0, alpha, 1), (2, 3, 0, final, 0), CO_GENERATOR_ALLOWED) division = _Feature((2, 2, 0, alpha, 2), (3, 0, 0, alpha, 0), CO_FUTURE_DIVISION) absolute_import = _Feature((2, 5, 0, alpha, 1), (2, 7, 0, alpha, 0), CO_FUTURE_ABSOLUTE_IMPORT) with_statement = _Feature((2, 5, 0, alpha, 1), (2, 6, 0, alpha, 0), CO_FUTURE_WITH_STATEMENT) -- - Julio Rojas [EMAIL PROTECTED]
Re: Bibliography and Python
Julio Rojas schrieb: I have a Full Python 2.5 installation on my computer, so that's not the problem. This is then not needed: I created the folder and added the Python script, reconfigured LyX... Nothing... Same error. To fix your problem: - open LyX and go to LyX's preferences - Paths - check that there in the field PATH_Prefix is a path to the folder where the file python.exe of your Python installation lives. If necessary add it or modify the path that eventually points to another former existing python installation. - Save the change and then reconfigre LyX. regards Uwe
Re: Bibliography and Python
Yup, that was it. As always, thanks Uwe!!! On 2/23/07, Uwe Stöhr [EMAIL PROTECTED] wrote: Julio Rojas schrieb: I have a Full Python 2.5 installation on my computer, so that's not the problem. This is then not needed: I created the folder and added the Python script, reconfigured LyX... Nothing... Same error. To fix your problem: - open LyX and go to LyX's preferences - Paths - check that there in the field PATH_Prefix is a path to the folder where the file python.exe of your Python installation lives. If necessary add it or modify the path that eventually points to another former existing python installation. - Save the change and then reconfigre LyX. regards Uwe -- - Julio Rojas [EMAIL PROTECTED]
Re: Bibliography and Python
I have a Full Python 2.5 installation on my computer, so that's not the problem. I created the folder and added the Python script, reconfigured LyX... Nothing... Same error. Uninstalled LyX and reinstalled it with the Small Version of your latest installer (2.11)... Nothing... Same error... Another tip? On 2/22/07, Uwe Stöhr [EMAIL PROTECTED] wrote: Julio Rojas schrieb: Is Lib a folder? I don't have it on my installation. When you don't have a folder c:\program files\LyX1.4.4\bin\Lib\ on your system, then you also not have a python.exe in the folder c:\program files\LyX1.4.4\bin\ Right? If yes, you already have a Python installation on your computer. Try to upgrade your Python installation to Python 2.5 and then reconfigure LyX. Under what name should I copy the attached text? Sorry, I attached this as python file named __future__.py. It is attached again, I hope this time it work. regards Uwe Record of phased-in incompatible language changes. Each line is of the form: FeatureName = _Feature( OptionalRelease , MandatoryRelease , CompilerFlag ) where, normally, OptionalRelease MandatoryRelease, and both are 5-tuples of the same form as sys.version_info: (PY_MAJOR_VERSION, # the 2 in 2.1.0a3; an int PY_MINOR_VERSION, # the 1; an int PY_MICRO_VERSION, # the 0; an int PY_RELEASE_LEVEL, # alpha, beta, candidate or final; string PY_RELEASE_SERIAL # the 3; an int ) OptionalRelease records the first release in which from __future__ import FeatureName was accepted. In the case of MandatoryReleases that have not yet occurred, MandatoryRelease predicts the release in which the feature will become part of the language. Else MandatoryRelease records when the feature became part of the language; in releases at or after that, modules no longer need from __future__ import FeatureName to use the feature in question, but may continue to use such imports. MandatoryRelease may also be None, meaning that a planned feature got dropped. Instances of class _Feature have two corresponding methods, .getOptionalRelease() and .getMandatoryRelease(). CompilerFlag is the (bitfield) flag that should be passed in the fourth argument to the builtin function compile() to enable the feature in dynamically compiled code. This flag is stored in the .compiler_flag attribute on _Future instances. These values must match the appropriate #defines of CO_xxx flags in Include/compile.h. No feature line is ever to be deleted from this file. all_feature_names = [ nested_scopes, generators, division, absolute_import, with_statement, ] __all__ = [all_feature_names] + all_feature_names # The CO_xxx symbols are defined here under the same names used by # compile.h, so that an editor search will find them here. However, # they're not exported in __all__, because they don't really belong to # this module. CO_NESTED= 0x0010 # nested_scopes CO_GENERATOR_ALLOWED = 0# generators (obsolete, was 0x1000) CO_FUTURE_DIVISION = 0x2000 # division CO_FUTURE_ABSOLUTE_IMPORT = 0x4000 # perform absolute imports by default CO_FUTURE_WITH_STATEMENT = 0x8000 # with statement class _Feature: def __init__(self, optionalRelease, mandatoryRelease, compiler_flag): self.optional = optionalRelease self.mandatory = mandatoryRelease self.compiler_flag = compiler_flag def getOptionalRelease(self): Return first release in which this feature was recognized. This is a 5-tuple, of the same form as sys.version_info. return self.optional def getMandatoryRelease(self): Return release in which this feature will become mandatory. This is a 5-tuple, of the same form as sys.version_info, or, if the feature was dropped, is None. return self.mandatory def __repr__(self): return _Feature + repr((self.optional, self.mandatory, self.compiler_flag)) nested_scopes = _Feature((2, 1, 0, beta, 1), (2, 2, 0, alpha, 0), CO_NESTED) generators = _Feature((2, 2, 0, alpha, 1), (2, 3, 0, final, 0), CO_GENERATOR_ALLOWED) division = _Feature((2, 2, 0, alpha, 2), (3, 0, 0, alpha, 0), CO_FUTURE_DIVISION) absolute_import = _Feature((2, 5, 0, alpha, 1), (2, 7, 0, alpha, 0), CO_FUTURE_ABSOLUTE_IMPORT) with_statement = _Feature((2, 5, 0, alpha, 1), (2, 6, 0, alpha, 0), CO_FUTURE_WITH_STATEMENT) -- - Julio Rojas [EMAIL PROTECTED]
Re: Bibliography and Python
Julio Rojas schrieb: I have a Full Python 2.5 installation on my computer, so that's not the problem. This is then not needed: I created the folder and added the Python script, reconfigured LyX... Nothing... Same error. To fix your problem: - open LyX and go to LyX's preferences - Paths - check that there in the field PATH_Prefix is a path to the folder where the file python.exe of your Python installation lives. If necessary add it or modify the path that eventually points to another former existing python installation. - Save the change and then reconfigre LyX. regards Uwe
Re: Bibliography and Python
Yup, that was it. As always, thanks Uwe!!! On 2/23/07, Uwe Stöhr [EMAIL PROTECTED] wrote: Julio Rojas schrieb: I have a Full Python 2.5 installation on my computer, so that's not the problem. This is then not needed: I created the folder and added the Python script, reconfigured LyX... Nothing... Same error. To fix your problem: - open LyX and go to LyX's preferences - Paths - check that there in the field PATH_Prefix is a path to the folder where the file python.exe of your Python installation lives. If necessary add it or modify the path that eventually points to another former existing python installation. - Save the change and then reconfigre LyX. regards Uwe -- - Julio Rojas [EMAIL PROTECTED]
Re: Bibliography and Python
I have a Full Python 2.5 installation on my computer, so that's not
the problem. I created the folder and added the Python script,
reconfigured LyX... Nothing... Same error.
Uninstalled LyX and reinstalled it with the Small Version of your
latest installer (2.11)... Nothing... Same error...
Another tip?
On 2/22/07, Uwe Stöhr <[EMAIL PROTECTED]> wrote:
Julio Rojas schrieb:
> Is "Lib" a folder? I don't have it on my installation.
When you don't have a folder
c:\program files\LyX1.4.4\bin\Lib\
on your system, then you also not have a python.exe in the folder
c:\program files\LyX1.4.4\bin\
Right?
If yes, you already have a Python installation on your computer. Try to upgrade
your Python
installation to Python 2.5 and then reconfigure LyX.
> Under what name should I copy the attached text?
Sorry, I attached this as python file named __future__.py.
It is attached again, I hope this time it work.
regards Uwe
"""Record of phased-in incompatible language changes.
Each line is of the form:
FeatureName = "_Feature(" OptionalRelease "," MandatoryRelease ","
CompilerFlag ")"
where, normally, OptionalRelease < MandatoryRelease, and both are 5-tuples
of the same form as sys.version_info:
(PY_MAJOR_VERSION, # the 2 in 2.1.0a3; an int
PY_MINOR_VERSION, # the 1; an int
PY_MICRO_VERSION, # the 0; an int
PY_RELEASE_LEVEL, # "alpha", "beta", "candidate" or "final"; string
PY_RELEASE_SERIAL # the 3; an int
)
OptionalRelease records the first release in which
from __future__ import FeatureName
was accepted.
In the case of MandatoryReleases that have not yet occurred,
MandatoryRelease predicts the release in which the feature will become part
of the language.
Else MandatoryRelease records when the feature became part of the language;
in releases at or after that, modules no longer need
from __future__ import FeatureName
to use the feature in question, but may continue to use such imports.
MandatoryRelease may also be None, meaning that a planned feature got
dropped.
Instances of class _Feature have two corresponding methods,
.getOptionalRelease() and .getMandatoryRelease().
CompilerFlag is the (bitfield) flag that should be passed in the fourth
argument to the builtin function compile() to enable the feature in
dynamically compiled code. This flag is stored in the .compiler_flag
attribute on _Future instances. These values must match the appropriate
#defines of CO_xxx flags in Include/compile.h.
No feature line is ever to be deleted from this file.
"""
all_feature_names = [
"nested_scopes",
"generators",
"division",
"absolute_import",
"with_statement",
]
__all__ = ["all_feature_names"] + all_feature_names
# The CO_xxx symbols are defined here under the same names used by
# compile.h, so that an editor search will find them here. However,
# they're not exported in __all__, because they don't really belong to
# this module.
CO_NESTED= 0x0010 # nested_scopes
CO_GENERATOR_ALLOWED = 0# generators (obsolete, was 0x1000)
CO_FUTURE_DIVISION = 0x2000 # division
CO_FUTURE_ABSOLUTE_IMPORT = 0x4000 # perform absolute imports by default
CO_FUTURE_WITH_STATEMENT = 0x8000 # with statement
class _Feature:
def __init__(self, optionalRelease, mandatoryRelease, compiler_flag):
self.optional = optionalRelease
self.mandatory = mandatoryRelease
self.compiler_flag = compiler_flag
def getOptionalRelease(self):
"""Return first release in which this feature was recognized.
This is a 5-tuple, of the same form as sys.version_info.
"""
return self.optional
def getMandatoryRelease(self):
"""Return release in which this feature will become mandatory.
This is a 5-tuple, of the same form as sys.version_info, or, if
the feature was dropped, is None.
"""
return self.mandatory
def __repr__(self):
return "_Feature" + repr((self.optional,
self.mandatory,
self.compiler_flag))
nested_scopes = _Feature((2, 1, 0, "beta", 1),
(2, 2, 0, "alpha", 0),
CO_NESTED)
generators = _Feature((2, 2, 0, "alpha", 1),
(2, 3, 0, "final", 0),
CO_GENERATOR_ALLOWED)
division = _Feature((2, 2, 0, "alpha", 2),
(3, 0, 0, "alpha", 0),
CO_FUTURE_DIVISION)
absolute_import = _Feature((2, 5, 0, "alpha", 1),
(2, 7, 0, "alpha", 0),
CO_FUTURE_ABSOLUTE_IMPORT)
with_statement = _Feature((2, 5, 0, "alpha", 1),
(2, 6, 0, "alpha", 0),
CO_FUTURE_WITH_STATEMENT)
--
-
Julio Rojas
[EMAIL PROTECTED]
Re: Bibliography and Python
Julio Rojas schrieb: I have a Full Python 2.5 installation on my computer, so that's not the problem. This is then not needed: I created the folder and added the Python script, reconfigured LyX... Nothing... Same error. To fix your problem: - open LyX and go to LyX's preferences -> Paths - check that there in the field "PATH_Prefix" is a path to the folder where the file "python.exe" of your Python installation lives. If necessary add it or modify the path that eventually points to another former existing python installation. - Save the change and then reconfigre LyX. regards Uwe
Re: Bibliography and Python
Yup, that was it. As always, thanks Uwe!!! On 2/23/07, Uwe Stöhr <[EMAIL PROTECTED]> wrote: Julio Rojas schrieb: > I have a Full Python 2.5 installation on my computer, so that's not > the problem. This is then not needed: > I created the folder and added the Python script, > reconfigured LyX... Nothing... Same error. To fix your problem: - open LyX and go to LyX's preferences -> Paths - check that there in the field "PATH_Prefix" is a path to the folder where the file "python.exe" of your Python installation lives. If necessary add it or modify the path that eventually points to another former existing python installation. - Save the change and then reconfigre LyX. regards Uwe -- - Julio Rojas [EMAIL PROTECTED]
Re: Bibliography and Python
Julio Rojas wrote: I'm working with LyX 1.4.4 on Vista. On a document I have already worked on, I tried to open the bibliography and the following message is presented: The Script c:\program files\LyX1.4.4\Resources\scripts\TexFiles.py failed This is fixed in version 1.4.4-3, which will be released today. Joost
Re: Bibliography and Python
Julio Rojas schrieb: On a document I have already worked on, I tried to open the bibliography and the following message is presented: The Script c:\program files\LyX1.4.4\Resources\scripts\TexFiles.py failed This has been fixed in version 2.11 of this installer: https://developer.berlios.de/project/showfiles.php?group_id=5117release_id=12253 You don't need to reinstall LyX to fix this, just copy the attached file to c:\program files\LyX1.4.4\bin\Lib and restart LyX. regards Uwe Record of phased-in incompatible language changes. Each line is of the form: FeatureName = _Feature( OptionalRelease , MandatoryRelease , CompilerFlag ) where, normally, OptionalRelease MandatoryRelease, and both are 5-tuples of the same form as sys.version_info: (PY_MAJOR_VERSION, # the 2 in 2.1.0a3; an int PY_MINOR_VERSION, # the 1; an int PY_MICRO_VERSION, # the 0; an int PY_RELEASE_LEVEL, # alpha, beta, candidate or final; string PY_RELEASE_SERIAL # the 3; an int ) OptionalRelease records the first release in which from __future__ import FeatureName was accepted. In the case of MandatoryReleases that have not yet occurred, MandatoryRelease predicts the release in which the feature will become part of the language. Else MandatoryRelease records when the feature became part of the language; in releases at or after that, modules no longer need from __future__ import FeatureName to use the feature in question, but may continue to use such imports. MandatoryRelease may also be None, meaning that a planned feature got dropped. Instances of class _Feature have two corresponding methods, .getOptionalRelease() and .getMandatoryRelease(). CompilerFlag is the (bitfield) flag that should be passed in the fourth argument to the builtin function compile() to enable the feature in dynamically compiled code. This flag is stored in the .compiler_flag attribute on _Future instances. These values must match the appropriate #defines of CO_xxx flags in Include/compile.h. No feature line is ever to be deleted from this file. all_feature_names = [ nested_scopes, generators, division, absolute_import, with_statement, ] __all__ = [all_feature_names] + all_feature_names # The CO_xxx symbols are defined here under the same names used by # compile.h, so that an editor search will find them here. However, # they're not exported in __all__, because they don't really belong to # this module. CO_NESTED= 0x0010 # nested_scopes CO_GENERATOR_ALLOWED = 0# generators (obsolete, was 0x1000) CO_FUTURE_DIVISION = 0x2000 # division CO_FUTURE_ABSOLUTE_IMPORT = 0x4000 # perform absolute imports by default CO_FUTURE_WITH_STATEMENT = 0x8000 # with statement class _Feature: def __init__(self, optionalRelease, mandatoryRelease, compiler_flag): self.optional = optionalRelease self.mandatory = mandatoryRelease self.compiler_flag = compiler_flag def getOptionalRelease(self): Return first release in which this feature was recognized. This is a 5-tuple, of the same form as sys.version_info. return self.optional def getMandatoryRelease(self): Return release in which this feature will become mandatory. This is a 5-tuple, of the same form as sys.version_info, or, if the feature was dropped, is None. return self.mandatory def __repr__(self): return _Feature + repr((self.optional, self.mandatory, self.compiler_flag)) nested_scopes = _Feature((2, 1, 0, beta, 1), (2, 2, 0, alpha, 0), CO_NESTED) generators = _Feature((2, 2, 0, alpha, 1), (2, 3, 0, final, 0), CO_GENERATOR_ALLOWED) division = _Feature((2, 2, 0, alpha, 2), (3, 0, 0, alpha, 0), CO_FUTURE_DIVISION) absolute_import = _Feature((2, 5, 0, alpha, 1), (2, 7, 0, alpha, 0), CO_FUTURE_ABSOLUTE_IMPORT) with_statement = _Feature((2, 5, 0, alpha, 1), (2, 6, 0, alpha, 0), CO_FUTURE_WITH_STATEMENT)
Re: Bibliography and Python
Is Lib a folder? I don't have it on my installation. Under what name should I copy the attached text? Thanks for your help. On 2/22/07, Uwe Stöhr [EMAIL PROTECTED] wrote: Julio Rojas schrieb: On a document I have already worked on, I tried to open the bibliography and the following message is presented: The Script c:\program files\LyX1.4.4\Resources\scripts\TexFiles.py failed This has been fixed in version 2.11 of this installer: https://developer.berlios.de/project/showfiles.php?group_id=5117release_id=12253 You don't need to reinstall LyX to fix this, just copy the attached file to c:\program files\LyX1.4.4\bin\Lib and restart LyX. regards Uwe Record of phased-in incompatible language changes. Each line is of the form: FeatureName = _Feature( OptionalRelease , MandatoryRelease , CompilerFlag ) where, normally, OptionalRelease MandatoryRelease, and both are 5-tuples of the same form as sys.version_info: (PY_MAJOR_VERSION, # the 2 in 2.1.0a3; an int PY_MINOR_VERSION, # the 1; an int PY_MICRO_VERSION, # the 0; an int PY_RELEASE_LEVEL, # alpha, beta, candidate or final; string PY_RELEASE_SERIAL # the 3; an int ) OptionalRelease records the first release in which from __future__ import FeatureName was accepted. In the case of MandatoryReleases that have not yet occurred, MandatoryRelease predicts the release in which the feature will become part of the language. Else MandatoryRelease records when the feature became part of the language; in releases at or after that, modules no longer need from __future__ import FeatureName to use the feature in question, but may continue to use such imports. MandatoryRelease may also be None, meaning that a planned feature got dropped. Instances of class _Feature have two corresponding methods, .getOptionalRelease() and .getMandatoryRelease(). CompilerFlag is the (bitfield) flag that should be passed in the fourth argument to the builtin function compile() to enable the feature in dynamically compiled code. This flag is stored in the .compiler_flag attribute on _Future instances. These values must match the appropriate #defines of CO_xxx flags in Include/compile.h. No feature line is ever to be deleted from this file. all_feature_names = [ nested_scopes, generators, division, absolute_import, with_statement, ] __all__ = [all_feature_names] + all_feature_names # The CO_xxx symbols are defined here under the same names used by # compile.h, so that an editor search will find them here. However, # they're not exported in __all__, because they don't really belong to # this module. CO_NESTED= 0x0010 # nested_scopes CO_GENERATOR_ALLOWED = 0# generators (obsolete, was 0x1000) CO_FUTURE_DIVISION = 0x2000 # division CO_FUTURE_ABSOLUTE_IMPORT = 0x4000 # perform absolute imports by default CO_FUTURE_WITH_STATEMENT = 0x8000 # with statement class _Feature: def __init__(self, optionalRelease, mandatoryRelease, compiler_flag): self.optional = optionalRelease self.mandatory = mandatoryRelease self.compiler_flag = compiler_flag def getOptionalRelease(self): Return first release in which this feature was recognized. This is a 5-tuple, of the same form as sys.version_info. return self.optional def getMandatoryRelease(self): Return release in which this feature will become mandatory. This is a 5-tuple, of the same form as sys.version_info, or, if the feature was dropped, is None. return self.mandatory def __repr__(self): return _Feature + repr((self.optional, self.mandatory, self.compiler_flag)) nested_scopes = _Feature((2, 1, 0, beta, 1), (2, 2, 0, alpha, 0), CO_NESTED) generators = _Feature((2, 2, 0, alpha, 1), (2, 3, 0, final, 0), CO_GENERATOR_ALLOWED) division = _Feature((2, 2, 0, alpha, 2), (3, 0, 0, alpha, 0), CO_FUTURE_DIVISION) absolute_import = _Feature((2, 5, 0, alpha, 1), (2, 7, 0, alpha, 0), CO_FUTURE_ABSOLUTE_IMPORT) with_statement = _Feature((2, 5, 0, alpha, 1), (2, 6, 0, alpha, 0), CO_FUTURE_WITH_STATEMENT) -- - Julio Rojas [EMAIL PROTECTED]
Re: Bibliography and Python
Julio Rojas schrieb: Is Lib a folder? I don't have it on my installation. When you don't have a folder c:\program files\LyX1.4.4\bin\Lib\ on your system, then you also not have a python.exe in the folder c:\program files\LyX1.4.4\bin\ Right? If yes, you already have a Python installation on your computer. Try to upgrade your Python installation to Python 2.5 and then reconfigure LyX. Under what name should I copy the attached text? Sorry, I attached this as python file named __future__.py. It is attached again, I hope this time it work. regards Uwe Record of phased-in incompatible language changes. Each line is of the form: FeatureName = _Feature( OptionalRelease , MandatoryRelease , CompilerFlag ) where, normally, OptionalRelease MandatoryRelease, and both are 5-tuples of the same form as sys.version_info: (PY_MAJOR_VERSION, # the 2 in 2.1.0a3; an int PY_MINOR_VERSION, # the 1; an int PY_MICRO_VERSION, # the 0; an int PY_RELEASE_LEVEL, # alpha, beta, candidate or final; string PY_RELEASE_SERIAL # the 3; an int ) OptionalRelease records the first release in which from __future__ import FeatureName was accepted. In the case of MandatoryReleases that have not yet occurred, MandatoryRelease predicts the release in which the feature will become part of the language. Else MandatoryRelease records when the feature became part of the language; in releases at or after that, modules no longer need from __future__ import FeatureName to use the feature in question, but may continue to use such imports. MandatoryRelease may also be None, meaning that a planned feature got dropped. Instances of class _Feature have two corresponding methods, .getOptionalRelease() and .getMandatoryRelease(). CompilerFlag is the (bitfield) flag that should be passed in the fourth argument to the builtin function compile() to enable the feature in dynamically compiled code. This flag is stored in the .compiler_flag attribute on _Future instances. These values must match the appropriate #defines of CO_xxx flags in Include/compile.h. No feature line is ever to be deleted from this file. all_feature_names = [ nested_scopes, generators, division, absolute_import, with_statement, ] __all__ = [all_feature_names] + all_feature_names # The CO_xxx symbols are defined here under the same names used by # compile.h, so that an editor search will find them here. However, # they're not exported in __all__, because they don't really belong to # this module. CO_NESTED= 0x0010 # nested_scopes CO_GENERATOR_ALLOWED = 0# generators (obsolete, was 0x1000) CO_FUTURE_DIVISION = 0x2000 # division CO_FUTURE_ABSOLUTE_IMPORT = 0x4000 # perform absolute imports by default CO_FUTURE_WITH_STATEMENT = 0x8000 # with statement class _Feature: def __init__(self, optionalRelease, mandatoryRelease, compiler_flag): self.optional = optionalRelease self.mandatory = mandatoryRelease self.compiler_flag = compiler_flag def getOptionalRelease(self): Return first release in which this feature was recognized. This is a 5-tuple, of the same form as sys.version_info. return self.optional def getMandatoryRelease(self): Return release in which this feature will become mandatory. This is a 5-tuple, of the same form as sys.version_info, or, if the feature was dropped, is None. return self.mandatory def __repr__(self): return _Feature + repr((self.optional, self.mandatory, self.compiler_flag)) nested_scopes = _Feature((2, 1, 0, beta, 1), (2, 2, 0, alpha, 0), CO_NESTED) generators = _Feature((2, 2, 0, alpha, 1), (2, 3, 0, final, 0), CO_GENERATOR_ALLOWED) division = _Feature((2, 2, 0, alpha, 2), (3, 0, 0, alpha, 0), CO_FUTURE_DIVISION) absolute_import = _Feature((2, 5, 0, alpha, 1), (2, 7, 0, alpha, 0), CO_FUTURE_ABSOLUTE_IMPORT) with_statement = _Feature((2, 5, 0, alpha, 1), (2, 6, 0, alpha, 0), CO_FUTURE_WITH_STATEMENT)
Re: Bibliography and Python
Bill Wood schrieb: Am I correct in inferring that Python 2.5 is required for LyX 1.4.4? At least Python 2.3 is needed. The installer comes with Python but this is only used if you haven't already Python installed. regards Uwe
Re: Bibliography and Python
Julio Rojas wrote: I'm working with LyX 1.4.4 on Vista. On a document I have already worked on, I tried to open the bibliography and the following message is presented: The Script c:\program files\LyX1.4.4\Resources\scripts\TexFiles.py failed This is fixed in version 1.4.4-3, which will be released today. Joost
Re: Bibliography and Python
Julio Rojas schrieb: On a document I have already worked on, I tried to open the bibliography and the following message is presented: The Script c:\program files\LyX1.4.4\Resources\scripts\TexFiles.py failed This has been fixed in version 2.11 of this installer: https://developer.berlios.de/project/showfiles.php?group_id=5117release_id=12253 You don't need to reinstall LyX to fix this, just copy the attached file to c:\program files\LyX1.4.4\bin\Lib and restart LyX. regards Uwe Record of phased-in incompatible language changes. Each line is of the form: FeatureName = _Feature( OptionalRelease , MandatoryRelease , CompilerFlag ) where, normally, OptionalRelease MandatoryRelease, and both are 5-tuples of the same form as sys.version_info: (PY_MAJOR_VERSION, # the 2 in 2.1.0a3; an int PY_MINOR_VERSION, # the 1; an int PY_MICRO_VERSION, # the 0; an int PY_RELEASE_LEVEL, # alpha, beta, candidate or final; string PY_RELEASE_SERIAL # the 3; an int ) OptionalRelease records the first release in which from __future__ import FeatureName was accepted. In the case of MandatoryReleases that have not yet occurred, MandatoryRelease predicts the release in which the feature will become part of the language. Else MandatoryRelease records when the feature became part of the language; in releases at or after that, modules no longer need from __future__ import FeatureName to use the feature in question, but may continue to use such imports. MandatoryRelease may also be None, meaning that a planned feature got dropped. Instances of class _Feature have two corresponding methods, .getOptionalRelease() and .getMandatoryRelease(). CompilerFlag is the (bitfield) flag that should be passed in the fourth argument to the builtin function compile() to enable the feature in dynamically compiled code. This flag is stored in the .compiler_flag attribute on _Future instances. These values must match the appropriate #defines of CO_xxx flags in Include/compile.h. No feature line is ever to be deleted from this file. all_feature_names = [ nested_scopes, generators, division, absolute_import, with_statement, ] __all__ = [all_feature_names] + all_feature_names # The CO_xxx symbols are defined here under the same names used by # compile.h, so that an editor search will find them here. However, # they're not exported in __all__, because they don't really belong to # this module. CO_NESTED= 0x0010 # nested_scopes CO_GENERATOR_ALLOWED = 0# generators (obsolete, was 0x1000) CO_FUTURE_DIVISION = 0x2000 # division CO_FUTURE_ABSOLUTE_IMPORT = 0x4000 # perform absolute imports by default CO_FUTURE_WITH_STATEMENT = 0x8000 # with statement class _Feature: def __init__(self, optionalRelease, mandatoryRelease, compiler_flag): self.optional = optionalRelease self.mandatory = mandatoryRelease self.compiler_flag = compiler_flag def getOptionalRelease(self): Return first release in which this feature was recognized. This is a 5-tuple, of the same form as sys.version_info. return self.optional def getMandatoryRelease(self): Return release in which this feature will become mandatory. This is a 5-tuple, of the same form as sys.version_info, or, if the feature was dropped, is None. return self.mandatory def __repr__(self): return _Feature + repr((self.optional, self.mandatory, self.compiler_flag)) nested_scopes = _Feature((2, 1, 0, beta, 1), (2, 2, 0, alpha, 0), CO_NESTED) generators = _Feature((2, 2, 0, alpha, 1), (2, 3, 0, final, 0), CO_GENERATOR_ALLOWED) division = _Feature((2, 2, 0, alpha, 2), (3, 0, 0, alpha, 0), CO_FUTURE_DIVISION) absolute_import = _Feature((2, 5, 0, alpha, 1), (2, 7, 0, alpha, 0), CO_FUTURE_ABSOLUTE_IMPORT) with_statement = _Feature((2, 5, 0, alpha, 1), (2, 6, 0, alpha, 0), CO_FUTURE_WITH_STATEMENT)
Re: Bibliography and Python
Is Lib a folder? I don't have it on my installation. Under what name should I copy the attached text? Thanks for your help. On 2/22/07, Uwe Stöhr [EMAIL PROTECTED] wrote: Julio Rojas schrieb: On a document I have already worked on, I tried to open the bibliography and the following message is presented: The Script c:\program files\LyX1.4.4\Resources\scripts\TexFiles.py failed This has been fixed in version 2.11 of this installer: https://developer.berlios.de/project/showfiles.php?group_id=5117release_id=12253 You don't need to reinstall LyX to fix this, just copy the attached file to c:\program files\LyX1.4.4\bin\Lib and restart LyX. regards Uwe Record of phased-in incompatible language changes. Each line is of the form: FeatureName = _Feature( OptionalRelease , MandatoryRelease , CompilerFlag ) where, normally, OptionalRelease MandatoryRelease, and both are 5-tuples of the same form as sys.version_info: (PY_MAJOR_VERSION, # the 2 in 2.1.0a3; an int PY_MINOR_VERSION, # the 1; an int PY_MICRO_VERSION, # the 0; an int PY_RELEASE_LEVEL, # alpha, beta, candidate or final; string PY_RELEASE_SERIAL # the 3; an int ) OptionalRelease records the first release in which from __future__ import FeatureName was accepted. In the case of MandatoryReleases that have not yet occurred, MandatoryRelease predicts the release in which the feature will become part of the language. Else MandatoryRelease records when the feature became part of the language; in releases at or after that, modules no longer need from __future__ import FeatureName to use the feature in question, but may continue to use such imports. MandatoryRelease may also be None, meaning that a planned feature got dropped. Instances of class _Feature have two corresponding methods, .getOptionalRelease() and .getMandatoryRelease(). CompilerFlag is the (bitfield) flag that should be passed in the fourth argument to the builtin function compile() to enable the feature in dynamically compiled code. This flag is stored in the .compiler_flag attribute on _Future instances. These values must match the appropriate #defines of CO_xxx flags in Include/compile.h. No feature line is ever to be deleted from this file. all_feature_names = [ nested_scopes, generators, division, absolute_import, with_statement, ] __all__ = [all_feature_names] + all_feature_names # The CO_xxx symbols are defined here under the same names used by # compile.h, so that an editor search will find them here. However, # they're not exported in __all__, because they don't really belong to # this module. CO_NESTED= 0x0010 # nested_scopes CO_GENERATOR_ALLOWED = 0# generators (obsolete, was 0x1000) CO_FUTURE_DIVISION = 0x2000 # division CO_FUTURE_ABSOLUTE_IMPORT = 0x4000 # perform absolute imports by default CO_FUTURE_WITH_STATEMENT = 0x8000 # with statement class _Feature: def __init__(self, optionalRelease, mandatoryRelease, compiler_flag): self.optional = optionalRelease self.mandatory = mandatoryRelease self.compiler_flag = compiler_flag def getOptionalRelease(self): Return first release in which this feature was recognized. This is a 5-tuple, of the same form as sys.version_info. return self.optional def getMandatoryRelease(self): Return release in which this feature will become mandatory. This is a 5-tuple, of the same form as sys.version_info, or, if the feature was dropped, is None. return self.mandatory def __repr__(self): return _Feature + repr((self.optional, self.mandatory, self.compiler_flag)) nested_scopes = _Feature((2, 1, 0, beta, 1), (2, 2, 0, alpha, 0), CO_NESTED) generators = _Feature((2, 2, 0, alpha, 1), (2, 3, 0, final, 0), CO_GENERATOR_ALLOWED) division = _Feature((2, 2, 0, alpha, 2), (3, 0, 0, alpha, 0), CO_FUTURE_DIVISION) absolute_import = _Feature((2, 5, 0, alpha, 1), (2, 7, 0, alpha, 0), CO_FUTURE_ABSOLUTE_IMPORT) with_statement = _Feature((2, 5, 0, alpha, 1), (2, 6, 0, alpha, 0), CO_FUTURE_WITH_STATEMENT) -- - Julio Rojas [EMAIL PROTECTED]
Re: Bibliography and Python
Julio Rojas schrieb: Is Lib a folder? I don't have it on my installation. When you don't have a folder c:\program files\LyX1.4.4\bin\Lib\ on your system, then you also not have a python.exe in the folder c:\program files\LyX1.4.4\bin\ Right? If yes, you already have a Python installation on your computer. Try to upgrade your Python installation to Python 2.5 and then reconfigure LyX. Under what name should I copy the attached text? Sorry, I attached this as python file named __future__.py. It is attached again, I hope this time it work. regards Uwe Record of phased-in incompatible language changes. Each line is of the form: FeatureName = _Feature( OptionalRelease , MandatoryRelease , CompilerFlag ) where, normally, OptionalRelease MandatoryRelease, and both are 5-tuples of the same form as sys.version_info: (PY_MAJOR_VERSION, # the 2 in 2.1.0a3; an int PY_MINOR_VERSION, # the 1; an int PY_MICRO_VERSION, # the 0; an int PY_RELEASE_LEVEL, # alpha, beta, candidate or final; string PY_RELEASE_SERIAL # the 3; an int ) OptionalRelease records the first release in which from __future__ import FeatureName was accepted. In the case of MandatoryReleases that have not yet occurred, MandatoryRelease predicts the release in which the feature will become part of the language. Else MandatoryRelease records when the feature became part of the language; in releases at or after that, modules no longer need from __future__ import FeatureName to use the feature in question, but may continue to use such imports. MandatoryRelease may also be None, meaning that a planned feature got dropped. Instances of class _Feature have two corresponding methods, .getOptionalRelease() and .getMandatoryRelease(). CompilerFlag is the (bitfield) flag that should be passed in the fourth argument to the builtin function compile() to enable the feature in dynamically compiled code. This flag is stored in the .compiler_flag attribute on _Future instances. These values must match the appropriate #defines of CO_xxx flags in Include/compile.h. No feature line is ever to be deleted from this file. all_feature_names = [ nested_scopes, generators, division, absolute_import, with_statement, ] __all__ = [all_feature_names] + all_feature_names # The CO_xxx symbols are defined here under the same names used by # compile.h, so that an editor search will find them here. However, # they're not exported in __all__, because they don't really belong to # this module. CO_NESTED= 0x0010 # nested_scopes CO_GENERATOR_ALLOWED = 0# generators (obsolete, was 0x1000) CO_FUTURE_DIVISION = 0x2000 # division CO_FUTURE_ABSOLUTE_IMPORT = 0x4000 # perform absolute imports by default CO_FUTURE_WITH_STATEMENT = 0x8000 # with statement class _Feature: def __init__(self, optionalRelease, mandatoryRelease, compiler_flag): self.optional = optionalRelease self.mandatory = mandatoryRelease self.compiler_flag = compiler_flag def getOptionalRelease(self): Return first release in which this feature was recognized. This is a 5-tuple, of the same form as sys.version_info. return self.optional def getMandatoryRelease(self): Return release in which this feature will become mandatory. This is a 5-tuple, of the same form as sys.version_info, or, if the feature was dropped, is None. return self.mandatory def __repr__(self): return _Feature + repr((self.optional, self.mandatory, self.compiler_flag)) nested_scopes = _Feature((2, 1, 0, beta, 1), (2, 2, 0, alpha, 0), CO_NESTED) generators = _Feature((2, 2, 0, alpha, 1), (2, 3, 0, final, 0), CO_GENERATOR_ALLOWED) division = _Feature((2, 2, 0, alpha, 2), (3, 0, 0, alpha, 0), CO_FUTURE_DIVISION) absolute_import = _Feature((2, 5, 0, alpha, 1), (2, 7, 0, alpha, 0), CO_FUTURE_ABSOLUTE_IMPORT) with_statement = _Feature((2, 5, 0, alpha, 1), (2, 6, 0, alpha, 0), CO_FUTURE_WITH_STATEMENT)
Re: Bibliography and Python
Bill Wood schrieb: Am I correct in inferring that Python 2.5 is required for LyX 1.4.4? At least Python 2.3 is needed. The installer comes with Python but this is only used if you haven't already Python installed. regards Uwe
Re: Bibliography and Python
Julio Rojas wrote: I'm working with LyX 1.4.4 on Vista. On a document I have already worked on, I tried to open the bibliography and the following message is presented: The Script "c:\program files\LyX1.4.4\Resources\scripts\TexFiles.py" failed This is fixed in version 1.4.4-3, which will be released today. Joost
Re: Bibliography and Python
Julio Rojas schrieb:
On a document I have already worked on, I tried to open the bibliography
and
the following message is presented:
The Script "c:\program files\LyX1.4.4\Resources\scripts\TexFiles.py" failed
This has been fixed in version 2.11 of this installer:
https://developer.berlios.de/project/showfiles.php?group_id=5117_id=12253
You don't need to reinstall LyX to fix this, just copy the attached file to
c:\program files\LyX1.4.4\bin\Lib
and restart LyX.
regards Uwe
"""Record of phased-in incompatible language changes.
Each line is of the form:
FeatureName = "_Feature(" OptionalRelease "," MandatoryRelease ","
CompilerFlag ")"
where, normally, OptionalRelease < MandatoryRelease, and both are 5-tuples
of the same form as sys.version_info:
(PY_MAJOR_VERSION, # the 2 in 2.1.0a3; an int
PY_MINOR_VERSION, # the 1; an int
PY_MICRO_VERSION, # the 0; an int
PY_RELEASE_LEVEL, # "alpha", "beta", "candidate" or "final"; string
PY_RELEASE_SERIAL # the 3; an int
)
OptionalRelease records the first release in which
from __future__ import FeatureName
was accepted.
In the case of MandatoryReleases that have not yet occurred,
MandatoryRelease predicts the release in which the feature will become part
of the language.
Else MandatoryRelease records when the feature became part of the language;
in releases at or after that, modules no longer need
from __future__ import FeatureName
to use the feature in question, but may continue to use such imports.
MandatoryRelease may also be None, meaning that a planned feature got
dropped.
Instances of class _Feature have two corresponding methods,
.getOptionalRelease() and .getMandatoryRelease().
CompilerFlag is the (bitfield) flag that should be passed in the fourth
argument to the builtin function compile() to enable the feature in
dynamically compiled code. This flag is stored in the .compiler_flag
attribute on _Future instances. These values must match the appropriate
#defines of CO_xxx flags in Include/compile.h.
No feature line is ever to be deleted from this file.
"""
all_feature_names = [
"nested_scopes",
"generators",
"division",
"absolute_import",
"with_statement",
]
__all__ = ["all_feature_names"] + all_feature_names
# The CO_xxx symbols are defined here under the same names used by
# compile.h, so that an editor search will find them here. However,
# they're not exported in __all__, because they don't really belong to
# this module.
CO_NESTED= 0x0010 # nested_scopes
CO_GENERATOR_ALLOWED = 0# generators (obsolete, was 0x1000)
CO_FUTURE_DIVISION = 0x2000 # division
CO_FUTURE_ABSOLUTE_IMPORT = 0x4000 # perform absolute imports by default
CO_FUTURE_WITH_STATEMENT = 0x8000 # with statement
class _Feature:
def __init__(self, optionalRelease, mandatoryRelease, compiler_flag):
self.optional = optionalRelease
self.mandatory = mandatoryRelease
self.compiler_flag = compiler_flag
def getOptionalRelease(self):
"""Return first release in which this feature was recognized.
This is a 5-tuple, of the same form as sys.version_info.
"""
return self.optional
def getMandatoryRelease(self):
"""Return release in which this feature will become mandatory.
This is a 5-tuple, of the same form as sys.version_info, or, if
the feature was dropped, is None.
"""
return self.mandatory
def __repr__(self):
return "_Feature" + repr((self.optional,
self.mandatory,
self.compiler_flag))
nested_scopes = _Feature((2, 1, 0, "beta", 1),
(2, 2, 0, "alpha", 0),
CO_NESTED)
generators = _Feature((2, 2, 0, "alpha", 1),
(2, 3, 0, "final", 0),
CO_GENERATOR_ALLOWED)
division = _Feature((2, 2, 0, "alpha", 2),
(3, 0, 0, "alpha", 0),
CO_FUTURE_DIVISION)
absolute_import = _Feature((2, 5, 0, "alpha", 1),
(2, 7, 0, "alpha", 0),
CO_FUTURE_ABSOLUTE_IMPORT)
with_statement = _Feature((2, 5, 0, "alpha", 1),
(2, 6, 0, "alpha", 0),
CO_FUTURE_WITH_STATEMENT)
Re: Bibliography and Python
Is "Lib" a folder? I don't have it on my installation.
Under what name should I copy the attached text?
Thanks for your help.
On 2/22/07, Uwe Stöhr <[EMAIL PROTECTED]> wrote:
Julio Rojas schrieb:
> On a document I have already worked on, I tried to open the bibliography
> and
> the following message is presented:
>
> The Script "c:\program files\LyX1.4.4\Resources\scripts\TexFiles.py"
failed
This has been fixed in version 2.11 of this installer:
https://developer.berlios.de/project/showfiles.php?group_id=5117_id=12253
You don't need to reinstall LyX to fix this, just copy the attached file
to
c:\program files\LyX1.4.4\bin\Lib
and restart LyX.
regards Uwe
"""Record of phased-in incompatible language changes.
Each line is of the form:
FeatureName = "_Feature(" OptionalRelease "," MandatoryRelease ","
CompilerFlag ")"
where, normally, OptionalRelease < MandatoryRelease, and both are 5-tuples
of the same form as sys.version_info:
(PY_MAJOR_VERSION, # the 2 in 2.1.0a3; an int
PY_MINOR_VERSION, # the 1; an int
PY_MICRO_VERSION, # the 0; an int
PY_RELEASE_LEVEL, # "alpha", "beta", "candidate" or "final"; string
PY_RELEASE_SERIAL # the 3; an int
)
OptionalRelease records the first release in which
from __future__ import FeatureName
was accepted.
In the case of MandatoryReleases that have not yet occurred,
MandatoryRelease predicts the release in which the feature will become
part
of the language.
Else MandatoryRelease records when the feature became part of the
language;
in releases at or after that, modules no longer need
from __future__ import FeatureName
to use the feature in question, but may continue to use such imports.
MandatoryRelease may also be None, meaning that a planned feature got
dropped.
Instances of class _Feature have two corresponding methods,
.getOptionalRelease() and .getMandatoryRelease().
CompilerFlag is the (bitfield) flag that should be passed in the fourth
argument to the builtin function compile() to enable the feature in
dynamically compiled code. This flag is stored in the .compiler_flag
attribute on _Future instances. These values must match the appropriate
#defines of CO_xxx flags in Include/compile.h.
No feature line is ever to be deleted from this file.
"""
all_feature_names = [
"nested_scopes",
"generators",
"division",
"absolute_import",
"with_statement",
]
__all__ = ["all_feature_names"] + all_feature_names
# The CO_xxx symbols are defined here under the same names used by
# compile.h, so that an editor search will find them here. However,
# they're not exported in __all__, because they don't really belong to
# this module.
CO_NESTED= 0x0010 # nested_scopes
CO_GENERATOR_ALLOWED = 0# generators (obsolete, was 0x1000)
CO_FUTURE_DIVISION = 0x2000 # division
CO_FUTURE_ABSOLUTE_IMPORT = 0x4000 # perform absolute imports by default
CO_FUTURE_WITH_STATEMENT = 0x8000 # with statement
class _Feature:
def __init__(self, optionalRelease, mandatoryRelease, compiler_flag):
self.optional = optionalRelease
self.mandatory = mandatoryRelease
self.compiler_flag = compiler_flag
def getOptionalRelease(self):
"""Return first release in which this feature was recognized.
This is a 5-tuple, of the same form as sys.version_info.
"""
return self.optional
def getMandatoryRelease(self):
"""Return release in which this feature will become mandatory.
This is a 5-tuple, of the same form as sys.version_info, or, if
the feature was dropped, is None.
"""
return self.mandatory
def __repr__(self):
return "_Feature" + repr((self.optional,
self.mandatory,
self.compiler_flag))
nested_scopes = _Feature((2, 1, 0, "beta", 1),
(2, 2, 0, "alpha", 0),
CO_NESTED)
generators = _Feature((2, 2, 0, "alpha", 1),
(2, 3, 0, "final", 0),
CO_GENERATOR_ALLOWED)
division = _Feature((2, 2, 0, "alpha", 2),
(3, 0, 0, "alpha", 0),
CO_FUTURE_DIVISION)
absolute_import = _Feature((2, 5, 0, "alpha", 1),
(2, 7, 0, "alpha", 0),
CO_FUTURE_ABSOLUTE_IMPORT)
with_statement = _Feature((2, 5, 0, "alpha", 1),
(2, 6, 0, "alpha", 0),
CO_FUTURE_WITH_STATEMENT)
--
-
Julio Rojas
[EMAIL PROTECTED]
Re: Bibliography and Python
Julio Rojas schrieb:
Is "Lib" a folder? I don't have it on my installation.
When you don't have a folder
c:\program files\LyX1.4.4\bin\Lib\
on your system, then you also not have a python.exe in the folder
c:\program files\LyX1.4.4\bin\
Right?
If yes, you already have a Python installation on your computer. Try to upgrade your Python
installation to Python 2.5 and then reconfigure LyX.
Under what name should I copy the attached text?
Sorry, I attached this as python file named __future__.py.
It is attached again, I hope this time it work.
regards Uwe
"""Record of phased-in incompatible language changes.
Each line is of the form:
FeatureName = "_Feature(" OptionalRelease "," MandatoryRelease ","
CompilerFlag ")"
where, normally, OptionalRelease < MandatoryRelease, and both are 5-tuples
of the same form as sys.version_info:
(PY_MAJOR_VERSION, # the 2 in 2.1.0a3; an int
PY_MINOR_VERSION, # the 1; an int
PY_MICRO_VERSION, # the 0; an int
PY_RELEASE_LEVEL, # "alpha", "beta", "candidate" or "final"; string
PY_RELEASE_SERIAL # the 3; an int
)
OptionalRelease records the first release in which
from __future__ import FeatureName
was accepted.
In the case of MandatoryReleases that have not yet occurred,
MandatoryRelease predicts the release in which the feature will become part
of the language.
Else MandatoryRelease records when the feature became part of the language;
in releases at or after that, modules no longer need
from __future__ import FeatureName
to use the feature in question, but may continue to use such imports.
MandatoryRelease may also be None, meaning that a planned feature got
dropped.
Instances of class _Feature have two corresponding methods,
.getOptionalRelease() and .getMandatoryRelease().
CompilerFlag is the (bitfield) flag that should be passed in the fourth
argument to the builtin function compile() to enable the feature in
dynamically compiled code. This flag is stored in the .compiler_flag
attribute on _Future instances. These values must match the appropriate
#defines of CO_xxx flags in Include/compile.h.
No feature line is ever to be deleted from this file.
"""
all_feature_names = [
"nested_scopes",
"generators",
"division",
"absolute_import",
"with_statement",
]
__all__ = ["all_feature_names"] + all_feature_names
# The CO_xxx symbols are defined here under the same names used by
# compile.h, so that an editor search will find them here. However,
# they're not exported in __all__, because they don't really belong to
# this module.
CO_NESTED= 0x0010 # nested_scopes
CO_GENERATOR_ALLOWED = 0# generators (obsolete, was 0x1000)
CO_FUTURE_DIVISION = 0x2000 # division
CO_FUTURE_ABSOLUTE_IMPORT = 0x4000 # perform absolute imports by default
CO_FUTURE_WITH_STATEMENT = 0x8000 # with statement
class _Feature:
def __init__(self, optionalRelease, mandatoryRelease, compiler_flag):
self.optional = optionalRelease
self.mandatory = mandatoryRelease
self.compiler_flag = compiler_flag
def getOptionalRelease(self):
"""Return first release in which this feature was recognized.
This is a 5-tuple, of the same form as sys.version_info.
"""
return self.optional
def getMandatoryRelease(self):
"""Return release in which this feature will become mandatory.
This is a 5-tuple, of the same form as sys.version_info, or, if
the feature was dropped, is None.
"""
return self.mandatory
def __repr__(self):
return "_Feature" + repr((self.optional,
self.mandatory,
self.compiler_flag))
nested_scopes = _Feature((2, 1, 0, "beta", 1),
(2, 2, 0, "alpha", 0),
CO_NESTED)
generators = _Feature((2, 2, 0, "alpha", 1),
(2, 3, 0, "final", 0),
CO_GENERATOR_ALLOWED)
division = _Feature((2, 2, 0, "alpha", 2),
(3, 0, 0, "alpha", 0),
CO_FUTURE_DIVISION)
absolute_import = _Feature((2, 5, 0, "alpha", 1),
(2, 7, 0, "alpha", 0),
CO_FUTURE_ABSOLUTE_IMPORT)
with_statement = _Feature((2, 5, 0, "alpha", 1),
(2, 6, 0, "alpha", 0),
CO_FUTURE_WITH_STATEMENT)
Re: Bibliography and Python
Bill Wood schrieb: Am I correct in inferring that Python 2.5 is required for LyX 1.4.4? At least Python 2.3 is needed. The installer comes with Python but this is only used if you haven't already Python installed. regards Uwe
