[GRASS GIS] #570: startup problem with standalone GRASS install

[GRASS GIS]

#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie          
      Type:  defect        |      Status:  reopened        
  Priority:  normal        |   Milestone:  6.4.0          
 Component:  Installation  |     Version:  svn-develbranch6
Resolution:                |    Keywords:  wingrass, python
  Platform:  MSWindows XP  |         Cpu:  x86-32          
---------------------------+------------------------------------------------
Comment (by timmie):

 echo %PATH% => points to the PythonXY installation, e.g.
 C:\Programme\pythonxy\python

 echo %PYTHONPATH% => points to my own libraries located elsewhere.

 %GRASS_PYTHON% => I thought that this one is set at runtime by GRASS.

 I do not know anymore, what to do.
 I need PythonXY because it delivers what I need for other purposes.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/570#comment:23>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie          
      Type:  defect        |      Status:  reopened        
  Priority:  normal        |   Milestone:  6.4.0          
 Component:  Installation  |     Version:  svn-develbranch6
Resolution:                |    Keywords:  wingrass, python
  Platform:  MSWindows XP  |         Cpu:  x86-32          
---------------------------+------------------------------------------------
Comment (by hamish):

 Replying to [comment:23 timmie]:
 > %GRASS_PYTHON% => I thought that this one is set at runtime by GRASS.


 If it is working as designed it should respect the value you give for
 GRASS_PYTHON if it is already set; it should only set automatically if
 unset.. if you launch grass with ' -text' and type "set" at the command
 prompt you should be able to see/confirm how it is set.


 > I do not know anymore, what to do.

 I guess you have to use the Tcl/Tk GUI or command prompt until we can
 figure out the solution. Even if it is still not working we have cleaned
 up all(?) of the GRASS_PYTHON calls in grass during the course of this bug
 & so are much closer than we were when we started.


 Hamish

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/570#comment:24>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie          
      Type:  defect        |      Status:  reopened        
  Priority:  normal        |   Milestone:  6.4.0          
 Component:  Installation  |     Version:  svn-develbranch6
Resolution:                |    Keywords:  wingrass, python
  Platform:  MSWindows XP  |         Cpu:  x86-32          
---------------------------+------------------------------------------------
Comment (by timmie):

 Replying to [comment:24 hamish]:
 > Replying to [comment:23 timmie]:
 > > %GRASS_PYTHON% => I thought that this one is set at runtime by GRASS.
 > If it is working as designed it should respect the value you give for
 GRASS_PYTHON if it is already set; it should only set automatically if
 unset.. if you launch grass with ' -text' and type "set" at the command
 prompt you should be able to see/confirm how it is set.

 I started GRASS through the Start Menu -> GRASS Command Line

 then did:
 #. enter a location
 #. set > myvars.txt

 in the file myvars.txt GRASS_PYTHON is nowhere to be found.

 > Even if it is still not working we have cleaned up all(?) of the
 GRASS_PYTHON calls in grass during the course of this > bug & so are much
 closer than we were when we started.
 Thanks for the positive words and patience you always send across.




 > > I do not know anymore, what to do.
 >
 > I guess you have to use the Tcl/Tk GUI or command prompt until we can
 figure out the solution. Even if it is still not working we have cleaned
 up all(?) of the GRASS_PYTHON calls in grass during the course of this bug
 & so are much closer than we were when we started.
 >
 >
 > Hamish

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/570#comment:25>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie          
      Type:  defect        |      Status:  reopened        
  Priority:  normal        |   Milestone:  6.4.0          
 Component:  Installation  |     Version:  svn-develbranch6
Resolution:                |    Keywords:  wingrass, python
  Platform:  MSWindows XP  |         Cpu:  x86-32          
---------------------------+------------------------------------------------
Comment (by timmie):

 Replying to [comment:25 timmie]:
 > Replying to [comment:24 hamish]:
 > > Replying to [comment:23 timmie]:
 > in the file myvars.txt GRASS_PYTHON is nowhere to be found.
 Where should  GRASS_PYTHON point to?

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/570#comment:26>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie          
      Type:  defect        |      Status:  reopened        
  Priority:  normal        |   Milestone:  6.4.0          
 Component:  Installation  |     Version:  svn-develbranch6
Resolution:                |    Keywords:  wingrass, python
  Platform:  MSWindows XP  |         Cpu:  x86-32          
---------------------------+------------------------------------------------
Comment (by hamish):

 Replying to [comment:23 timmie]:
 > Where should  GRASS_PYTHON point to?

 set GRASS_PYTHON=C:\path\to\python.exe


 which should be the version of python which you want GRASS to use and set
 before you try to start GRASS.

 make sure the first path with a python25.dll (or whatever that is called)
 which shows up in your %PATH% matches that.

 i.e. the straight-python bits might not care which flavour of python you
 use as long as the .exe and .dll are matched. But the wxvdigit and wxnviz
 C++ compiled parts will probably want only the exact python(.exe & .dll)
 that they were built for.


 Hamish

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/570#comment:27>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie          
      Type:  defect        |      Status:  reopened        
  Priority:  normal        |   Milestone:  6.4.0          
 Component:  Installation  |     Version:  svn-develbranch6
Resolution:                |    Keywords:  wingrass, python
  Platform:  MSWindows XP  |         Cpu:  x86-32          
---------------------------+------------------------------------------------
Comment (by timmie):

 set GRASS_PYTHON=C:\GRASS\extrabin\
 C:\GRASS\grass64.bat -text
 => error

 set GRASS_PYTHON=C:\Programme\pythonxy\python\
 C:\GRASS\grass64.bat -text

 => error

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/570#comment:28>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie          
      Type:  defect        |      Status:  reopened        
  Priority:  normal        |   Milestone:  6.4.0          
 Component:  Installation  |     Version:  svn-develbranch6
Resolution:                |    Keywords:  wingrass, python
  Platform:  MSWindows XP  |         Cpu:  x86-32          
---------------------------+------------------------------------------------
Comment (by hamish):

 Replying to [comment:28 timmie]:
 > set GRASS_PYTHON=C:\GRASS\extrabin\

 you need the whole thing, including .exe:

 set GRASS_PYTHON=C:\GRASS\extrabin\python.exe


 > C:\GRASS\grass64.bat -text
 > => error

 ... what does the error say? (can't guess)



 Hamish

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/570#comment:29>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie          
      Type:  defect        |      Status:  reopened        
  Priority:  normal        |   Milestone:  6.4.0          
 Component:  Installation  |     Version:  svn-develbranch6
Resolution:                |    Keywords:  wingrass, python
  Platform:  MSWindows XP  |         Cpu:  x86-32          
---------------------------+------------------------------------------------
Comment (by timmie):

 * entered GRASS_PYTHON='C:\GRASS\extrabin\python.exe' in my environment
 settings in My Computer.
 * C:\GRASS\grass64.bat -wxpython
 * I get the error:
 https://trac.osgeo.org/grass/attachment/ticket/570/bug_grass.jpg

 Thanks again for your help.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/570#comment:30>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie          
      Type:  defect        |      Status:  reopened        
  Priority:  normal        |   Milestone:  6.4.0          
 Component:  Installation  |     Version:  svn-develbranch6
Resolution:                |    Keywords:  wingrass, python
  Platform:  MSWindows XP  |         Cpu:  x86-32          
---------------------------+------------------------------------------------
Comment (by glynn):

 Replying to [comment:21 hamish]:
 > Are the GRASS_PYTHON, PATH, and PYTHON_PATH environment variables all
 set to pick up a consistent version of modern python? if grass tries to
 run it's own python.exe but the PATH order grabs the .dll from PythonXY
 first, it's likely you will see errors.

 Can someone explain the point of GRASS_PYTHON, given that running a .py
 script will use the Python interpreter which is set in the registry?

 Absent a reasonable explanation, I intend to remove it in 7.0.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/570#comment:31>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone GRASS install
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie          
      Type:  defect        |      Status:  reopened        
  Priority:  normal        |   Milestone:  6.4.0          
 Component:  Installation  |     Version:  svn-develbranch6
Resolution:                |    Keywords:  wingrass, python
  Platform:  MSWindows XP  |         Cpu:  x86-32          
---------------------------+------------------------------------------------
Comment (by dvictori):

 I had the same problem timmie mentioned, using WinXP, python(x,y) and
 grass from OSGeo4W. I got it fixed by replacing the pywintypes25.dll in
 c:/windows/system32 with the one that came with OSGeo4W

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/570#comment:32>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone winGRASS install and custom python
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie          
      Type:  defect        |      Status:  reopened        
  Priority:  normal        |   Milestone:  6.4.0          
 Component:  Installation  |     Version:  svn-develbranch6
Resolution:                |    Keywords:  wingrass, python
  Platform:  MSWindows XP  |         Cpu:  x86-32          
---------------------------+------------------------------------------------
Changes (by hamish):

  * summary:  startup problem with standalone GRASS install => startup
              problem with standalone winGRASS install and
              custom python

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/570#comment:33>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone winGRASS install and custom python
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie          
      Type:  defect        |      Status:  reopened        
  Priority:  normal        |   Milestone:  6.4.0          
 Component:  Installation  |     Version:  svn-develbranch6
Resolution:                |    Keywords:  wingrass, python
  Platform:  MSWindows XP  |         Cpu:  x86-32          
---------------------------+------------------------------------------------
Comment (by timmie):

 so,
 * is the pywintypes25.dll from PythonXY wrong?
 * who has to solve it: pythonxy or GRASS?

 I would like to have them both installed without major problems or
 negative interaction.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/570#comment:34>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone winGRASS install and custom python
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie          
      Type:  defect        |      Status:  reopened        
  Priority:  normal        |   Milestone:  6.4.0          
 Component:  Installation  |     Version:  svn-develbranch6
Resolution:                |    Keywords:  wingrass, python
  Platform:  MSWindows XP  |         Cpu:  x86-32          
---------------------------+------------------------------------------------
Comment (by dvictori):

 Replying to [comment:34 timmie]:
 > so,
 > * is the pywintypes25.dll from PythonXY wrong?
 > * who has to solve it: pythonxy or GRASS?
 >
 > I would like to have them both installed without major problems or
 negative interaction.

 I don't know who is at fault. All that I know is that winGrass (OSGeo4W)
 does not like python(x,y)'s pywintypes25.dll BUT, python(x,y) will work
 with the file supplied by OSGeo4W. It's probably a python version mix-up
 problem.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/570#comment:35>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone winGRASS install and custom python
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie          
      Type:  defect        |      Status:  reopened        
  Priority:  normal        |   Milestone:  6.4.0          
 Component:  Installation  |     Version:  svn-develbranch6
Resolution:                |    Keywords:  wingrass, python
  Platform:  MSWindows XP  |         Cpu:  x86-32          
---------------------------+------------------------------------------------
Comment (by timmie):

 Replying to [comment:35 dvictori]:
 from PythonXY:

 ''One thing is sure: there is no such thing as "Python(x,y)'s
 pywintypes25.dll" because this DLL is directly coming from the
 official pywin32 binary package. In other words, installing Python
 (x,y)'s pywin32 plugin is exactly the same as installing pywin32
 official package (http://sourceforge.net/projects/pywin32/files/
 pywin32/pywin32-213.win32-py2.5.exe). And there is more: as you may
 know, Python(x,y) binaries for Python itself are installed using the
 official Python .msi installer. So, installing Python 2.5 official
 distribution with pywin32 official binary package should lead to the
 exact same bug.

 I would suggest to test the previous release of pywin32 (2.12) to see
 if it's related. And if it is, it's between GRASS and pywin32.

 Have you tested a simple Python 2.5 install (with the official binary
 distribution) with pywin32 2.13?''

 => it is an issue between GRASS and pywin32 as it also existed with
 pywin32 (2.12):
 I reported this first on 04/26/09 and pywin32 was updated in PythonXY
 Version 2.1.13  (06-14-2009).

 What version of Python and pywin32 is GRASS using?

 According to http://sourceforge.net/projects/pywin32/
 the version2.13 is the mostr recent one!

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/570#comment:36>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone winGRASS install and custom python
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie          
      Type:  defect        |      Status:  reopened        
  Priority:  normal        |   Milestone:  6.4.0          
 Component:  Installation  |     Version:  svn-develbranch6
Resolution:                |    Keywords:  wingrass, python
  Platform:  MSWindows XP  |         Cpu:  x86-32          
---------------------------+------------------------------------------------
Comment (by timmie):

 How can we get a statement from persons packaging GRASS for windows on
 this Python issue?

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/570#comment:37>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone winGRASS install and custom python
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie          
      Type:  defect        |      Status:  reopened        
  Priority:  normal        |   Milestone:  6.4.0          
 Component:  Installation  |     Version:  svn-develbranch6
Resolution:                |    Keywords:  wingrass, python
  Platform:  MSWindows XP  |         Cpu:  x86-32          
---------------------------+------------------------------------------------
Comment (by cnielsen):

 Replying to [comment:37 timmie]:
 > How can we get a statement from persons packaging GRASS for windows on
 this Python issue?

 Hi Timmie,
 I'm the packager of the native winGrass but I'm not sure how to deal with
 your python issue. I use the python package from the OSGeo4W installer so
 you can check [http://trac.osgeo.org/osgeo4w/wiki/PackageListing#Languages
 here] for details on what versions are included there (though I couldn't
 find details on pywin32). If you think an update of one of those packages
 would resolve your issue, post to the osgeo4w-dev list. Once that's
 updated, I'll put out a new native winGrass package with the update as
 well.

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/570#comment:38>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone winGRASS install and custom python
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie          
      Type:  defect        |      Status:  reopened        
  Priority:  normal        |   Milestone:  6.4.0          
 Component:  Installation  |     Version:  svn-develbranch6
Resolution:                |    Keywords:  wingrass, python
  Platform:  MSWindows XP  |         Cpu:  x86-32          
---------------------------+------------------------------------------------
Comment (by aghisla):

 Replying to [comment:32 dvictori]:
 > I had the same problem timmie mentioned, using WinXP, python(x,y) and
 grass from OSGeo4W. I got it fixed by replacing the pywintypes25.dll in
 c:/windows/system32 with the one that came with OSGeo4W

 Thanks for the tip dvictori!
 It solved this issue on my WinXP, OSGeo4W's GRASS (6.4.0svn2) and locally
 installed Python 2.5 (in C:\Python25\). No need to edit environment
 variables.

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/570#comment:39>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone winGRASS install and custom python
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie          
      Type:  defect        |      Status:  reopened        
  Priority:  normal        |   Milestone:  6.4.0          
 Component:  Installation  |     Version:  svn-develbranch6
Resolution:                |    Keywords:  wingrass, python
  Platform:  MSWindows XP  |         Cpu:  x86-32          
---------------------------+------------------------------------------------
Comment (by timmie):

 I try to track the Python problem at OSGEO4W:
 http://trac.osgeo.org/osgeo4w/ticket/82

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/570#comment:40>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone winGRASS install and custom python
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie          
      Type:  defect        |      Status:  reopened        
  Priority:  normal        |   Milestone:  6.4.0          
 Component:  Installation  |     Version:  svn-develbranch6
Resolution:                |    Keywords:  wingrass, python
  Platform:  MSWindows XP  |         Cpu:  x86-32          
---------------------------+------------------------------------------------
Comment (by timmie):

 Hi,
 as stated in
 http://trac.osgeo.org/osgeo4w/ticket/82
 This is still an issue with the latest installer.

 How can I connect this report with the one in OSGEO4W?

 How shall we proceed?

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/570#comment:41>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS GIS]

#570: startup problem with standalone winGRASS install and custom python
---------------------------+------------------------------------------------
  Reporter:  timmie        |       Owner:  timmie          
      Type:  defect        |      Status:  reopened        
  Priority:  critical      |   Milestone:  6.4.0          
 Component:  Installation  |     Version:  svn-develbranch6
Resolution:                |    Keywords:  wingrass, python
  Platform:  MSWindows XP  |         Cpu:  x86-32          
---------------------------+------------------------------------------------
Changes (by timmie):

  * priority:  normal => critical

Comment:

 Makred as critical because GRASS 6.4 release aims to support windows
 correctly.

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/570#comment:42>
GRASS GIS <http://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev