Debian 9: 9.1 released(debian.org)
debian.org
Debian 9: 9.1 released
https://www.debian.org/News/2017/20170722
28 comments
>Require non-free or proprietary drivers?
You bet I do, and thanks. I might start using that version instead of official debian + arcane ritual of copying stuff to lib/firmware during installation.
You bet I do, and thanks. I might start using that version instead of official debian + arcane ritual of copying stuff to lib/firmware during installation.
> Require non-free or proprietary drivers?
You almost certainly do, which is why I now point people to the easier to find/search https://fiendish.github.io/The-Debian-Gotham-Needs/
Unfortunately, live testing+nonfree ISOs are frequently missing or out of date.
You almost certainly do, which is why I now point people to the easier to find/search https://fiendish.github.io/The-Debian-Gotham-Needs/
Unfortunately, live testing+nonfree ISOs are frequently missing or out of date.
Both of those things will be so helpful to me! I can't get a cable up to my office so I always have to try and dance around finding the firmware for my wireless card. It's kind of enraging and I can't never quite remember what I did the last time
Does anyone know if Python 3.6 going to be in Stretch at some point?
Not having it is so annoying since Stretch is basically there for the next few years and 3.6 is a very important Python release.
I've even been considering switching all my company's servers back to Ubuntu just for that...
Not having it is so annoying since Stretch is basically there for the next few years and 3.6 is a very important Python release.
I've even been considering switching all my company's servers back to Ubuntu just for that...
Chris Lamb, the current Debian Project Leader, has said that it will not be in stretch but could potentially be available in stretch-backports:
> If someone puts in the work, sure :) There isn't a "they" in Debian... it's, well, volunteers doing the actual grunt work if they feel it's needed..
Source: https://www.reddit.com/r/debian/comments/5a0gcf/will_python_...
With that said, I've personally packaged a simple backport of Python 3.6 (currently 3.6.2) for Debian stretch. There are pre-built Debian packages available in the releases tab, and a one-liner in the README for how to build them yourself: https://github.com/chriskuehl/python3.6-debian-stretch
You can install these alongside the regular python3.5 installation (it doesn't replace it).
> If someone puts in the work, sure :) There isn't a "they" in Debian... it's, well, volunteers doing the actual grunt work if they feel it's needed..
Source: https://www.reddit.com/r/debian/comments/5a0gcf/will_python_...
With that said, I've personally packaged a simple backport of Python 3.6 (currently 3.6.2) for Debian stretch. There are pre-built Debian packages available in the releases tab, and a one-liner in the README for how to build them yourself: https://github.com/chriskuehl/python3.6-debian-stretch
You can install these alongside the regular python3.5 installation (it doesn't replace it).
I actually came across your repo a few days ago!
I haven't tried it yet. I remember seeing that comment from Chris Lamb but I'm left wondering what the blockers are to getting 3.6 in backports. I messed around with another python3.6 deb (don't remember from where) and there were too many issues with it; namely with venvs.
I haven't tried it yet. I remember seeing that comment from Chris Lamb but I'm left wondering what the blockers are to getting 3.6 in backports. I messed around with another python3.6 deb (don't remember from where) and there were too many issues with it; namely with venvs.
I've been using my packaged version pretty extensively (mostly in virtualenvs) and haven't encountered any issues yet myself, but would definitely be interested to hear (either on GitHub or here) what issues you encountered and if they occur with my packaged version as well.
I wouldn't really expect any issues since it doesn't replace `/usr/bin/python3` (it just adds a `/usr/bin/python3.6`), but it's definitely possible I just haven't run into them.
I wouldn't really expect any issues since it doesn't replace `/usr/bin/python3` (it just adds a `/usr/bin/python3.6`), but it's definitely possible I just haven't run into them.
IIRC, the python3.6 from testing was causing inconsistencies in the /lib packages shipped inside the virtualenv (like inconsistent versions would get imported). I'll definitely give your package a shot!
The OS python is there to satisfy other OS dependencies, and only occasionally for you.
If you care about the Python version, you are much better off with an independent python install, I personally recommend conda - it lets you run different python versions for different uses, all shielded from OS upgrades (whether minor dist-upgrade or complete distribution change -- or $DIETY forbid joining a Redmond religion).
I have heard good things about Enthought Python, but don't have experience with it. And you can always build the latest yourself and build a .dpkg for your company.
If you care about the Python version, you are much better off with an independent python install, I personally recommend conda - it lets you run different python versions for different uses, all shielded from OS upgrades (whether minor dist-upgrade or complete distribution change -- or $DIETY forbid joining a Redmond religion).
I have heard good things about Enthought Python, but don't have experience with it. And you can always build the latest yourself and build a .dpkg for your company.
An argument can be made that the system python is for system things, not end user things.
If you want the latest python, just use the python-build script from here: https://github.com/pyenv/pyenv/tree/master/plugins/python-bu...
And then ./python-build -v 3.6.1 /opt/python-3.6.1 and you're done.
You'll have to manage your paths manually for your shell/terminal though, this is basically what you'll need to do, though this is for perl but can be easily adapted: http://tinyurl.com/y8h7lbt2
If you want the latest python, just use the python-build script from here: https://github.com/pyenv/pyenv/tree/master/plugins/python-bu...
And then ./python-build -v 3.6.1 /opt/python-3.6.1 and you're done.
You'll have to manage your paths manually for your shell/terminal though, this is basically what you'll need to do, though this is for perl but can be easily adapted: http://tinyurl.com/y8h7lbt2
I can't recommend this for your company but would love to hear some feedback for https://labs.fedoraproject.org/python-classroom/
(note: I am not a member of the project just interested in reading some feedback)
> One of the benefits of Fedora for Python developers is the ease of setting up Python development. The Fedora Python Classroom Lab makes it even easier for teachers and instructors to use Fedora in their classrooms or workshops. Ready to use operating system with important stuff pre-installed - either with GNOME or as a headless environment for Docker or Vagrant. Teach Python on Fedora, with Fedora, using the stuff you love: IPython, Jupyter Notebook, multiple Pythons, virtualenvs, tox, git and more
> The Fedora Python Classroom Lab comes in 3 variants. Either you can run it in graphical mode with GNOME, or you can virtualize it with Vagrant or run it in a Docker container. You choose what fits your teaching environment the best.
> Users and developers are available in the #fedora-python IRC channel on irc.freenode.org for real-time chat.
> Users and developers are also available on the mailing list at [email protected].
I know Red Hat is not the best but maybe this might be worth looking into?
(note: I am not a member of the project just interested in reading some feedback)
> One of the benefits of Fedora for Python developers is the ease of setting up Python development. The Fedora Python Classroom Lab makes it even easier for teachers and instructors to use Fedora in their classrooms or workshops. Ready to use operating system with important stuff pre-installed - either with GNOME or as a headless environment for Docker or Vagrant. Teach Python on Fedora, with Fedora, using the stuff you love: IPython, Jupyter Notebook, multiple Pythons, virtualenvs, tox, git and more
> The Fedora Python Classroom Lab comes in 3 variants. Either you can run it in graphical mode with GNOME, or you can virtualize it with Vagrant or run it in a Docker container. You choose what fits your teaching environment the best.
> Users and developers are available in the #fedora-python IRC channel on irc.freenode.org for real-time chat.
> Users and developers are also available on the mailing list at [email protected].
I know Red Hat is not the best but maybe this might be worth looking into?
Why even ask such question? Debian stable has been extremely predictable in this regard. No, the major version in stable is not going to change.
You do have other options, though - run testing (python3.6 is there right now) or a mixed stable/testing system.
You do have other options, though - run testing (python3.6 is there right now) or a mixed stable/testing system.
> mixed stable/testing system
Unfortunately the deb from testing has some pretty serious compatibility issues when pulled into a stable system :(
> Why even ask such question?
Because I'm curious. Because it'd be useful. Because I haven't used any other Debian than Jessie. Because I like asking questions. Pick one?
Unfortunately the deb from testing has some pretty serious compatibility issues when pulled into a stable system :(
> Why even ask such question?
Because I'm curious. Because it'd be useful. Because I haven't used any other Debian than Jessie. Because I like asking questions. Pick one?
Can't you use a ppa? Or host a python 3.6 package yourself? Maybe build from source?
> 3.6 is a very important Python release.
Out of interest, why is it very important?
Out of interest, why is it very important?
Nothing about Wacom tablet driver fix snief. That currently freezes the system and prevents me from updating :-(
Also I really don't like that the live-cd's change my system-clock. I nearly missed closing of shops today because I didn't expect my system time being suddenly wrong. Why do that? It didn't even check any time-server, but simply set my computer clock 2 hours back without any warning!
Also I really don't like that the live-cd's change my system-clock. I nearly missed closing of shops today because I didn't expect my system time being suddenly wrong. Why do that? It didn't even check any time-server, but simply set my computer clock 2 hours back without any warning!
Assuming you're dualbooting Linux and a Windows version: Linux keeps the RTC in UTC by default while Windows expects localtime and can't handle the conversion from UTC transparently if required. Configure Linux to use localtime as well to avoid surprise as that's easier than the other way round.
I used a live-cd and the whole point of those is that you can try an OS without that OS changing your system. Localtime should be the default configuration and not something the user has to figure out after getting fucked by it.
edit: Or at least give a big warning when changing your users PC clock!!!
edit: Or at least give a big warning when changing your users PC clock!!!
How would you go about doing that? I get the feeling that it's just one change in an obscure config file
Better to set everything to use UTC
https://wiki.archlinux.org/index.php/time#UTC_in_Windows
https://wiki.archlinux.org/index.php/time#UTC_in_Windows
[deleted]
Is the anki package still broken?
Looks that way. Rather, it's missing from the stretch distribution altogether because of the bugs filed against it [1].
[1] https://qa.debian.org/excuses.php?package=anki
[1] https://qa.debian.org/excuses.php?package=anki
Using or considering Gnome 3? The "Pixel Saver" extension may be for you (https://extensions.gnome.org/extension/723/pixel-saver/). It merges the title bar of the window with the top menu. Save screen real estate on low resolution notebooks.