To utilize the inherent UTF-8 support for windows console, I wanted to freeze my script in python 3.6, but I'm unable to find any. Am I missing something, or none of the freezing modules updated for 3.6 yet?
Otherwise I'll just keep a 3.5.2 frozen version and a 3.6 script version for computers with English consoles.
Thanks.
The bytecode format changed for Python 3.6 but I just pushed a change to cx_Freeze that adds support for it. You can compile it yourself or wait for the next release -- which should be sometime this week.
Related
First, I know that on windows you can compile packages from source using Rtools. We are trying to avoid having to compile the packages locally.
Are the Windows binaries not being compiled for older versions of R? See screen shot below. Or are they only being compiled 1x a year or 2x a year? Updating to a newer version of R is not possible right now.
I am not familiar with the binary/windows/R packages process to know why this is happening. I know that volunteer(s) maintain this windows binary compilation and it happens automatically.
Ok looks like I eventually found the answer to my own question. Apparently we should always read the README section!
The binaries for R < 3.4 are no longer being supported.
https://cran.r-project.org/bin/windows/contrib/ReadMe
Fresh install of ubuntu 18.04 then standard apt-install of awesome with awesome-extra.
Awesome --version returns
awesome v4.2 (Human after all)
• Compiled against Lua 5.3.3 (running with Lua 5.3)
• D-Bus support: ✔
• execinfo support: ✔
• xcb-randr version: 1.5
• LGI version: 0.9.2
gnome-control-center sound -v
** (gnome-control-center:14812): DEBUG: 14:27:19.737: Enabling debugging
** (gnome-control-center:14812): DEBUG: 14:27:19.850: No extra argument
** (gnome-control-center:14812): WARNING **: 14:27:19.850: Could not find settings panel "sound"
Basically there is no settings whatsoever.
Anyone can suggest what went wrong?
Everything else works just fine, I have sound, keyboard, multiple displays. I just lost control over settings, cannot mute sound, cannot dim a screen, cannot lock my laptop.
PS
Previous ubuntu (16.04) had unity-control-center and it was working just fine (but with older version of awesome I think)
gnome-control center can be run by tricking it into thinking it is in a gnome desktop
env XDG_CURRENT_DESKTOP=GNOME gnome-control-center
or by editing the .desktop files for each control app.
for example
/usr/share/applications/gnome-display-panel.desktop
find the line OnlyShowIn=GNOME;Unity; add awesomewm
I reached to Awesome irc channel to figure out what might be wrong. Explanation I was given (I am not quoting, I am answering as I understand the problem) is that nowadays gnome is more and more strict over it's architecture. So in the past you could replace window manager on gnome with another tool and retain whatever underlying solution was (mentioned control panel, sound widgets and etc). But nowadays gnome has approach all or nothing.
So real solution to my problem is, because sound and screen is working and I am only missing settings-control over them, is to install widgets and/or tools. For example pavucontrol was mentioned as good tool for a sound and bind key shortcuts to control brightness.
Previous iteration of Ubuntu worked, because exactly it was running unity, not gnome.
On its website OpenFlipper says it can be compiled in three steps as:
cd build
cmake ..
make # or, even better, make -j8
However I get an error saying Qt is unable to be found at the cmake step and that I should specify a QT5_INSTALL_PATH. However even if I do this OpenFlipper is still issuing the same complaint!
You are not supposed to specify where Qt is installed in the QT5_INSTALLED_DIR but prior to that as environment variable in your terminal:
# assuming Qt was installed in your home directory, as is default
export CMAKE_PREFIX_PATH=~/Qt5.7.0/5.7/gcc_64/
# note that you now have to call cmake etc from that process
Compiling and running it after that you might get errors telling you GL_ARB_vertex_buffer_object is not present, even if your glxinfo | grep ARB_vertex_buffer is telling you it is.* Clicking "Ignore" results in a crash. To mitigate this, you have to manually change (4,3) to (3,0) in
OpenFlipper/widgets/coreWidget/CoreWidget.cc
If you still experience errors, try deleting your cmake cache, this is accomplished by using cmake-gui (was in the package cmake-qt-gui for me) and hitting "Delete Cache"
(optional) remove the very annoying warning message you get at every start of OpenFlipper by removing the line concerning "renderers shipped" in
OpenFlipper/Core/Core.cc
*: My teaching assistant told me that there is a bug in Qt (<5.9) that forces OpenFlipper to use the OpenGL Compatibility Profile. Additionally Intel and AMD drivers hand back an OpenGL 3.0 Core Context when asked for an OpenGL 4.3 Compatibility Context (my TA described this behavior as a "bug", I'm not so sure about this), leading to a crash in Qt. So this should be resolved in Qt 5.9 (not out yet). This seems to affect also mainly integrated graphics, so one could try using a dedicated GPU.
I don't like the 3.6 version at all. It has too many bugs and it's too slow compared with the previous versions, so I'd like to install to a previous version and wait till they fix the problems. I can't downgrade the installation, so no, not an option.
I know that in this web: https://wiki.appcelerator.org/display/guides2/Reverting+to+a+Previous+Version there is a list of old versions, but this are VERY old, I'd like to download at least the 3.4.2 version or newer (like 3.5), but I can't see any link from wich I can download it. Can anyone give me a link or way to get previous versions of aptana?
Oh yes, oh yes, finally I found them:
MAC OS
http://d1iwq2e2xrohf.cloudfront.net/tools/studio/standalone/3.4.2.201308081805/mac/Aptana_Studio_3_Setup_3.4.2.dmg
WINDOWS
http://d1iwq2e2xrohf.cloudfront.net/tools/studio/standalone/3.4.2.201308081805/win/Aptana_Studio_3_Setup_3.4.2.exe
Linux 32 bits
http://d1iwq2e2xrohf.cloudfront.net/tools/studio/standalone/3.4.2.201308081805/linux/Aptana_Studio_3_Setup_Linux_x86_3.4.2.zip
Linux 64 bits
http://d1iwq2e2xrohf.cloudfront.net/tools/studio/standalone/3.4.2.201308081805/linux/Aptana_Studio_3_Setup_Linux_x86_64_3.4.2.zip
Can't get the plugin, sorry.
You could find Aptana 3.4.2 as Eclipse plugin at the following URL: http://d1iwq2e2xrohf.cloudfront.net/tools/studio/plugin/update/studio3/3.4.2.201308081736/com.aptana.feature.studio-3.4.2.201308081736-7W7I57boG98RAi489ctbvKi7VXbq.zip
When you are installing it from the zip, make sure you un-tick "Group Items by Category"
I'm trying to install Riverbank's PyQt for the first time, and from reading some other questions here, it looks like I need to update my Qt from 4.6 to 4.7. I've downloaded QtSDK, PyQt, and sip all within the last 2 days, so they all should be the latest.
I've installed Qt 4.6 before, and it put everything where I would expect. For example, I have a directory /usr/local/Qt4.6 that has a couple files in it, and other files, like frameworks, seem to be where I'd expect them.
Now, with Qt4.7, it looks like there's this huge package (QtSDK) that include mobile, and when the installation is done(installed into /Developer/QtSDK without issues using the online installer), I look in what I thought were the expected areas:
/usr/include - only 4.6, no 4.7
/Library/Frameworks - time stamps over a year old, indicating it's my 4.6 install
/Developer/Tools/Qt - time stamps over a year old
/usr/local - only 4.6, no 4.7
/Developer/Applications/Qt/plugins - time stamps over a year old
and I don't see Qt4.7 anywhere - I don't think I saw anything install outside of the /Developer/QtSDK area. I don't remember having to do anything special to more 4.6 into place. Is there some kind of make install type stuff I need to do for 4.7 after the online install finishes?
Or do I need to add stuff to a bunch of environment PATHs or configure files to point to the new Qt4.7?
When I try to run the configure.py for PyQt, it thinks my Qt version is 4.6(and chokes on QDBusPendingCall), so I'm pretty sure it's not seeing the newer install.
My Mac is Snow Leopard 10.6.8.
Thanks in advance!
All you need to do is set
export QTDIR=/path/to/SDK/root
export PATH=${QTDIR}/bin:$PATH
Once you're building things, the really important part is that the right 'qmake' needs to be in your path. (i.e. not an older one). After that, qmake will tell everything that wants to build Qt stuff where it (and its libraries/frameworks/includes live)