[Bf-committers] Meeting notes: 2.48 plans
rogerwickes at yahoo.com
Thu Sep 25 23:10:53 CEST 2008
I think if you just delete the pyc files, it forces Python to re-compile (actually re-byte-code) the source...which is what the reload() does. Perhaps these pyc should not be distributed or if they are not, people may be copying over the source but not deleting the pyc modules, and thus still have the old byte-code files being used.
Sent by Roger Wickes for intended recipient. If you are not the intended recipient, please delete this message and contact Mr. Wickes immediately.
Atlantica Investments, Inc.
PO Box 680310, Marietta, GA 30068 USA
----- Original Message ----
From: Dalai Felinto <dfelinto at gmail.com>
To: bf-blender developers <bf-committers at blender.org>
Sent: Thursday, September 25, 2008 4:27:32 PM
Subject: Re: [Bf-committers] Meeting notes: 2.48 plans
Benoit, regarding to the python problem:
I submitted a "bug report" since Blender 2.46, even for internal
scripts imported we have this problem:
If we have a work version, is early them 2.46 ...
But as Campbell said, import, reload() works fine ...
(or you can rename the module and import using the new name)
2008/9/25 Brecht Van Lommel <brecht at blender.org>:
> On Thu, 2008-09-25 at 16:10 +0200, Benoit Bolsee wrote:
>> >For all regular devs it means to communicate now if there's known
>> There is a problem with the blenderplayer, at least in Windows: the
>> texture and lighting is completely wrong in the blenderplayer. It is
>> like that since 2.47. I think it should be fixed before we release 2.48.
> I know there was such an issue in 2.47, but though it was fixed. Trying
> with texface/multitexture/glsl materials I cannot find an issue with
> latest svn, testing on Linux. Could you provide an example file that
> goes wrong?
> Bf-committers mailing list
> Bf-committers at blender.org
Bf-committers mailing list
Bf-committers at blender.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Bf-committers