Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

osgeo64/processing: bag magic number in yaml #24098

Closed
qgib opened this issue Feb 13, 2017 · 9 comments
Closed

osgeo64/processing: bag magic number in yaml #24098

qgib opened this issue Feb 13, 2017 · 9 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Build/Install Related to compiling or installing QGIS
Milestone

Comments

@qgib
Copy link
Contributor

qgib commented Feb 13, 2017

Author Name: Richard Duivenvoorde (@rduivenvoorde)
Original Redmine Issue: 16188
Affected QGIS version: master
Redmine category:windows_package
Assignee: Jürgen Fischer


Just installed current dev version (bb2a6c8) on Windows here (next to 2.14) which fails to start processing because of
ImportError: bad magic number in 'yaml': b'\x03\xf3

'
see screendump

FYI: this is 64bit Windows Server 2008 R2 Enterprise install


@qgib
Copy link
Contributor Author

qgib commented Feb 14, 2017

Author Name: Nyall Dawson (@nyalldawson)


Reassigning to Jürgen- this seems an error in the yaml package itself, not in processing.


  • category_id was changed from Processing/Core to Windows Package
  • assigned_to_id was changed from Victor Olaya to Jürgen Fischer

@qgib
Copy link
Contributor Author

qgib commented Feb 14, 2017

Author Name: Jürgen Fischer (@jef-n)


Not reproducable here. Apparently it's a stale pyc. Is python3-pyyaml installed? qgis-dev depends on it.

@qgib
Copy link
Contributor Author

qgib commented Feb 14, 2017

Author Name: Jürgen Fischer (@jef-n)


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Feb 14, 2017

Author Name: Nyall Dawson (@nyalldawson)


Ok - confirmed. Removing all .pyc files from the osgeo4w folder and restarting fixed this for me.

@qgib
Copy link
Contributor Author

qgib commented Feb 14, 2017

Author Name: Richard Duivenvoorde (@rduivenvoorde)


Thanks for looking into it. I cannot confirm untill next week when I'm working on that machine again.

So this is a left over from a qgis.2x run in the same folder?
Could be because I installed from an excisting osgeo4w install/folder.

What I'm curious now for is if this could also happen when you install both 2.x and 3/2.99 in same osgeo4w64 folder and first run 2.x (generating .pyc files) and then try to run 3 (picking up those files?)...

Feel free to close it, I will open it when it does not fix my problem.

@qgib
Copy link
Contributor Author

qgib commented Feb 15, 2017

Author Name: Jürgen Fischer (@jef-n)


Richard Duivenvoorde wrote:

So this is a left over from a qgis.2x run in the same folder?

The python3 and python2 installs are different directories. Interesting would be which file it actually is.

What I'm curious now for is if this could also happen when you install both 2.x and 3/2.99 in same osgeo4w64 folder

That should work.

@qgib
Copy link
Contributor Author

qgib commented Feb 22, 2017

Author Name: Jérôme Guélat (Jérôme Guélat)


I had the same problem... Deleting C:\OSGeo4W64\apps\qgis-dev\python\yaml\init.pyc seemed to help...

Is it safe to remove it?

@qgib
Copy link
Contributor Author

qgib commented Feb 22, 2017

Author Name: Jürgen Fischer (@jef-n)


Jérôme Guélat wrote:

I had the same problem... Deleting C:\OSGeo4W64\apps\qgis-dev\python\yaml\init.pyc seemed to help...

Is it safe to remove it?

Yes - that's from an previous python2 based qgis-dev. Fixed in 702d4cc.


  • status_id was changed from Feedback to Closed
  • resolution was changed from to fixed/implemented

@qgib
Copy link
Contributor Author

qgib commented Feb 23, 2017

Author Name: Richard Duivenvoorde (@rduivenvoorde)


Yep, confirmed here too. Removed all *.pyc files and works!

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Build/Install Related to compiling or installing QGIS labels May 25, 2019
@qgib qgib added this to the Version 3.0 milestone May 25, 2019
@qgib qgib closed this as completed May 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Build/Install Related to compiling or installing QGIS
Projects
None yet
Development

No branches or pull requests

1 participant