Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
mathstodon.xyz is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon instance for maths people. We have LaTeX rendering in the web interface!

Administered by:

Server stats:

2.8K
active users

mathstodon.xyz: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#python2

0 posts0 participants0 posts today
Replied in thread
Public
R.L. Dane :Debian: :OpenBSD: 🍵

@amin

Eh...

It's a rolling release, so it's got that going for it, but a lot/most of their custom utilities (such as the package manager) is still on Python 2, which is... not good.

/usr/bin/python is even a symlink to python2 which is really not good.

Small team. Looks like the original dev, who started a new distro, is going to re-work a lot of those things, which will be the basis for Solus going forward, so there's a lot of hope for newer and better utilities.

To be clear, my only real complaint so far is the python2-ness of it.

Also, they don't have a ksh package (which some of my scripts require), but I managed to compile the standard ksh2020.

I don't know if I will stay. #Python2 is kind of a deal-breaker.

Still slowly replicating my #KDE #Plasma setup from my work #Debian box. I have a lot of custom keybinds that make it a little more like i3/sway for me.

My other options are Debian testing, #FreeBSD (probably will lose the ability to run KSP), or #OpenSuSE tumbleweed (if they can ever just enable polkit by default, already).

Public *
postmodern

Spoke too soon about InfoSec projects still clinging to Python 2.7. Turns out my ronin-payloads project, a Ruby project, requires the python2 package in order to test it's Python Payload Encoders under Python versions 2 and 3.
github.com/ronin-rb/ronin-payl

Appears that GitHub has recently updated their GitHub Actions Ubuntu VM to 24.04.1, which no longer has a python2 package :(
github.com/ronin-rb/ronin-payl

Also looks like the setup-python GitHub Action has also already removed python2.7.
github.com/actions/setup-pytho

This poses a bit of a problem for software which needs to test against other legacy software.

GitHubGitHub - ronin-rb/ronin-payloads: A Ruby micro-framework for writing and running exploit payloadsA Ruby micro-framework for writing and running exploit payloads - ronin-rb/ronin-payloads
#python2#githubactions
Public
9Lukas5 🚂 🐧

Imagine:
- small custom tool in #Python2 / #Jython, bundled to an .exe
- Last time bundled was a few years back
- executable used on CI server

Then:
- suddenly all builds across the Server fail 😳
- The CI server and your own PC fail executing your small tool, saying "This application needs #Java 8" 🤔
- But your CI Server and own PC _have_ Java 8 installed 🤨
- The fellas around you have seemingly the same tools installed and can execute the tool 🧐

#programming#magic#CI
Public
Horror Nerd Online

Python 2 | Full Monster Horror Movie | WATCH FOR FREE

#horror – #Trailers – #horrormovies – #Python2 – @GoldwynFilms – A man, his business partner, and his wife are enlisted to transport an unknown object from a Russian military base, only to discover that the object is a giant, genetically-altered python. …

#ad #horror #Python2 #Trailers

horrornerdonline.com/2024/10/p

Public *
postmodern

Added integration tests for ronin-payload's new payload encoders and discovered that Python2 does not support evaling a print statement. Python3 however added support for this.

>>> eval('print "test"')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "<string>", line 1
    print "test"
        ^
SyntaxError: invalid syntax

Lol, wtf, how did people seriously tout Python2 over Python3. Even Ruby and JavaScript are more consistent.

GitHubGitHub - ronin-rb/ronin-payloads: A Ruby micro-framework for writing and running exploit payloadsA Ruby micro-framework for writing and running exploit payloads - ronin-rb/ronin-payloads
#python2#payloads#roninrb
Replied in thread
Public
Felix Palmen 📯

@CyDeFect @FiLiS all of these are missing too many details to tell anything about them. Except for #CIFS (although you probably don't even want that but #SMB3 instead, #Linux just kept tthe "CIFS" name although supporting SMB3), all #FreeBSD offers is indeed #SMB1. Whether this is an issue or not depends on your scenario and environment. I just offer my shares via #NFS as well, problem solved for me.

BTW, #seamonkey was removed mainly because of a #python2 (EOL for a long time) build dependency. IIRC this is meanwhile solved, so the port *could* be readded, it's just someone would have to do it and maintain it. There's an inofficial port available, you'll find it on the forums.

SearchLive feeds
About