Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Blender 2.80 is broken, may be a wider python problem.
Date: Sun, 02 Feb 2020 21:08:36 +0100	[thread overview]
Message-ID: <20200202200836.Lg-HHUnr6n79MfprQdta1azs4VaxrQzdhX5Y1jsUQLU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18567@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]

Closed issue by sanderboer on void-packages repository

https://github.com/void-linux/void-packages/issues/18567

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:  
Void 5.4.14_1 x86_64 GenuineIntel notuptodate rrrmFFF
* package:  
blender-2.80_1 3D graphics creation suite

### Expected behavior
Open blender 2.8, select the default cube, add subdivision surface modifier, see the surface be subdivided. 

### Actual behavior
No surface is subdivided. No errors are given, not in program not in the terminal. Blender works normally and other modifiers work as expected, but the subdiv modifier remains inert.

### Steps to reproduce the behavior
Open blender 2.8, select the default cube, add subdivision surface modifier.

During blender install, there are some python byte-compie warnings, for instance:
`
Byte-compiling python code in /usr/share/blender/2.80/scripts...
/usr/share/blender/2.80/scripts/addons/add_curve_extra_objects/add_curve_aceous_galore.py:109: SyntaxWarning: "is" with
a literal. Did you mean "=="?
`

I deleted the pyc files in /usr/share/blender, but this changed nothing.

On a maybe related note, I am having issues getting the python bindings for ifcopenshell to compile correctly.

If anybody could give me pointers on how to proceed or on how investigate this matter further, I would appreciate that.

thx.
S 



      parent reply	other threads:[~2020-02-02 20:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-26 13:14 [ISSUE] " voidlinux-github
2020-01-26 13:32 ` voidlinux-github
2020-01-26 17:38 ` voidlinux-github
2020-02-02 20:08 ` voidlinux-github [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200202200836.Lg-HHUnr6n79MfprQdta1azs4VaxrQzdhX5Y1jsUQLU@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).