2.2 version does not work under windows

[GoogleCodeExporter]

using python 2.7 under windows

The 2.2 version does not work under windows, periscope reports that a default 
handler should be installed for __MAIN__.

Original issue reported on code.google.com by Peter.Ra...@gmail.com on 24 May 2011 at 6:09

[GoogleCodeExporter]

I've just added a 0.2.3 tarball in the downloads section.

Could you give it a try ?

Original comment by patrick....@gmail.com on 24 May 2011 at 9:45

[GoogleCodeExporter]

The real problem is now being reported:

ERROR:__main__:Could not generate a cache folder at the home location using XDG 
(freedesktop). You must specify a --cache-config folder where the cach
e and config will be located (always use the same folder).

1) I have no clue what the home location should be
2) I have no clue what the name of the file should be

suggestion: check for windows platform and just put it in the 
$homepath$\periscope\config

Original comment by Peter.Ra...@gmail.com on 25 May 2011 at 12:54

[GoogleCodeExporter]

Ok, the log message could have been more explicit.

I will use:
os.path.join(os.path.expanduser("~"), ".config", "periscope")
if the desktop is not XDG compatible.

And only if this doesn't work, show the warning.
0.2.4 should be online tomorrow.

Original comment by patrick....@gmail.com on 25 May 2011 at 1:03

[GoogleCodeExporter]

Note that in the meantime, you can do:
periscope --cache-folder C:/tmp <your_video.avi>

Original comment by patrick....@gmail.com on 25 May 2011 at 1:05

• Changed state: Accepted
• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Thanks for the workaround. I will let you know if 0.2.4 works when it is 
available.

Original comment by Peter.Ra...@gmail.com on 25 May 2011 at 2:15

[GoogleCodeExporter]

0.2.4 is now available. Could you give it another try without using the 
--cache-folder option ?

Thanks

Original comment by patrick....@gmail.com on 25 May 2011 at 8:13

[GoogleCodeExporter]

0.2.4 Created the default config file automatically. Looks like you can close 
the issue since periscope works immediately after setup.py install. 

Original comment by Peter.Ra...@gmail.com on 26 May 2011 at 9:10

[GoogleCodeExporter]

Original comment by patrick....@gmail.com on 29 May 2011 at 3:09

• Changed state: Done

[GoogleCodeExporter]

I just did a fresh install from the trunk and the config file was not created 
automatically (re #8). This is on Win7 64bit.

Error message is good enough to know that a config file is needed. But I can't 
find any documentation on what it should contain ;)

Using the --cache-folder switch for now.

But can't there be a fallback to using the system wide tmp directory?

Cheers

Original comment by mistae...@gmail.com on 25 Jan 2012 at 6:31