Commits

Vinay Sajip committed e73603f

Updated version resources, README and documentation.

Comments (0)

Files changed (4)

CLILauncher/CLILauncher.rc

 //
 
 VS_VERSION_INFO VERSIONINFO
- FILEVERSION 1,0,0,3
- PRODUCTVERSION 1,0,0,3
+ FILEVERSION 1,0,0,8
+ PRODUCTVERSION 1,0,0,8
  FILEFLAGSMASK 0x17L
 #ifdef _DEBUG
  FILEFLAGS 0x1L
             VALUE "Comments", "Python Launcher for Windows"
             VALUE "CompanyName", "Python Software Foundation"
             VALUE "FileDescription", "Python Launcher for Windows (Console)"
-            VALUE "FileVersion", "1, 0, 0, 3"
+            VALUE "FileVersion", "1, 0, 0, 8"
             VALUE "InternalName", "py"
             VALUE "LegalCopyright", "Copyright (C) 2011 Python Software Foundation"
             VALUE "OriginalFilename", "py"
             VALUE "ProductName", "Python Launcher for Windows"
-            VALUE "ProductVersion", "1, 0, 0, 3"
+            VALUE "ProductVersion", "1, 0, 0, 8"
         END
     END
     BLOCK "VarFileInfo"
-===========================
---------------
---------------
---------------------
  py
  py -2.6
  py -3
-------------
    #! python
    import sys
    sys.stdout.write("hello from Python %s\n" % (sys.version,))
   py hello.py
    #! python3
----------------------
-------------
-------------
  #! /usr/bin/python
--------------------------
  #! /usr/bin/python -v
-------------
-------------
---------------------------
    Two .ini files will be searched by the launcher - ``py.ini`` in the
    current user's "application data" directory (i.e., the directory returned
    by calling the Windows function SHGetFolderPath with CSIDL_LOCAL_APPDATA)
    and ``py.ini`` in the same directory as the launcher.  The same .ini
    files are used for both the 'console' version of the launcher (i.e.,
    py.exe) and for the 'windows' version (ie, pyw.exe)
    
    Customization specified in the "application directory" will have
    precendence over the one next to the executable, so a user, who may not
    have write access to the .ini file next to the launcher, can override
    commands in that global .ini file)
-----------------------------------
  ``python2`` will use the latest Python 2.x version installed and
  the command ``python3`` will use the lastest Python 3.x installed.
  options at all as the versions are fully specified.
  the latest installed Python 3 version.
  implementation of 3.1 whereas the command ``python3`` will use the latest
  installed Python (PY_PYTHON was not considered at all as a major
  version was specified.)
  ``python`` and ``python3`` will both use specifically 3.1
  [defaults]
  python=3.1
  containing:
  [defaults]
  python=3
  python3=3.1
-----------
-----------
+===========================
---------------
---------------
---------------------
  py
  py -2.6
  py -3
-------------
    #! python
    import sys
    sys.stdout.write("hello from Python %s\n" % (sys.version,))
   py hello.py
    #! python3
----------------------
-------------
-------------
  #! /usr/bin/python
--------------------------
  #! /usr/bin/python -v
-------------
-------------
---------------------------
    Two .ini files will be searched by the launcher - ``py.ini`` in the
    current user's "application data" directory (i.e. the directory returned
    by calling the Windows function SHGetFolderPath with CSIDL_LOCAL_APPDATA)
    and ``py.ini`` in the same directory as the launcher.  The same .ini
    files are used for both the 'console' version of the launcher (i.e.
    py.exe) and for the 'windows' version (i.e. pyw.exe)
    
    Customization specified in the "application directory" will have
    precedence over the one next to the executable, so a user, who may not
    have write access to the .ini file next to the launcher, can override
    commands in that global .ini file)
-----------------------------------
  ``python2`` will use the latest Python 2.x version installed and
  the command ``python3`` will use the latest Python 3.x installed.
  options at all as the versions are fully specified.
  the latest installed Python 3 version.
  implementation of 3.1 whereas the command ``python3`` will use the latest
  installed Python (PY_PYTHON was not considered at all as a major
  version was specified.)
  ``python`` and ``python3`` will both use specifically 3.1
  [defaults]
  python=3.1
  containing:
  [defaults]
  python=3
  python3=3.1
-----------
-----------

GUILauncher/GUILauncher.rc

 //
 
 VS_VERSION_INFO VERSIONINFO
- FILEVERSION 1,0,0,3
- PRODUCTVERSION 1,0,0,3
+ FILEVERSION 1,0,0,8
+ PRODUCTVERSION 1,0,0,8
  FILEFLAGSMASK 0x17L
 #ifdef _DEBUG
  FILEFLAGS 0x1L
             VALUE "Comments", "Python Launcher for Windows"
             VALUE "CompanyName", "Python Software Foundation"
             VALUE "FileDescription", "Python Launcher for Windows (GUI)"
-            VALUE "FileVersion", "1, 0, 0, 3"
+            VALUE "FileVersion", "1, 0, 0, 8"
             VALUE "InternalName", "GUILaunpyw"
             VALUE "LegalCopyright", "Copyright (C) 2011 Python Software Foundation"
             VALUE "OriginalFilename", "pyw"
             VALUE "ProductName", "Python Launcher for Windows"
-            VALUE "ProductVersion", "1, 0, 0, 3"
+            VALUE "ProductVersion", "1, 0, 0, 8"
         END
     END
     BLOCK "VarFileInfo"
 #!python3   -> the most recent Python 3.x
 #!python3.2 -> Python 3.2 (an error will be raised if that's not installed)
 
+Basic Documentation
+-------------------
+
+Basic documentation in ReStructuredText format can be found at
+
+https://bitbucket.org/vinay.sajip/pylauncher/raw/tip/Doc/launcher.rst
+
 Software Status
 ---------------