rbarrois

5 ms·

1.
by rbarrois 2y ago
That's quite interesting. Now, I'm left to wonder if this could have been used to better handle the Python 2-to-3 transition, e.g '# coding: six.python2' would adjust Python2 code to be valid Python3, or '# coding:
2.
by rbarrois 4y ago
It seems to be available from resellers, lab401 seems to be their official reseller in Europe: https://lab401.com/collections/flipper-zero
3.
Playing Tetris on a general purpose Factorio CPU(old.reddit.com)
10 points by rbarrois 4y ago|0 comments
4.
by rbarrois 5y ago
Indeed — when you look at this from other engineering disciplines: having your train track built for "no downtime, ever" means that you have a third track available, with its dedicated platforms, so that you can work on one track
5.
by rbarrois 5y ago
I'd say that it depends on the license; for StackOverflow, it's CC-BY-SA 4.0 [1]. For sample code, that would depend on the license of the original documentation. My point is: when I'm copying code from a source with an expli
6.
by rbarrois 5y ago
An interesting impact of this discussion is, for me: within my team at work, we're likely to forbid any use of Github co-pilot for our codebase, unless we can get a formal guarantee from Github that the generated code is actually valid
7.
by rbarrois 5y ago
The only minor issue being that the materials used in fabricating the ASIC are likely more expensive (money and energy-wise) than those for a conventional heater!
8.
by rbarrois 6y ago
I gather that this project targets internal constants. Let's say you need to share the list of error codes between your backend API and your frontend: instead of having to maintain two lists, just share the constants between the two co
9.
by rbarrois 6y ago
The issue is kinda more complex: cryptography is also a hard dependency of pip, the official Python package installer. And CPython itself seem to support PPC64 and s390x — which are Tier 2 targets for rust. Hence, pip now depends on softwar
10.
by rbarrois 6y ago
From what I understand, the issue with the previous behaviour is that, although it enabled you to bypass the issue of that specific package, it could also install conflicting versions you didn't know about. For your specific use case,
11.
by rbarrois 6y ago
I think it's closer to "Celery is a great tool to get started, but as your product matures you'll end up falling back to a simple AMQP consumer stack": - By default, task IDs are just pickled Python objects - if you want
12.
by rbarrois 6y ago
It depend on the actual patch, and bug report. I sometimes receive patches where the contributor just tried to shoehorn the feature they wanted in the codebase; they didn't understand the project architecture, just found a way to get i
13.
by rbarrois 6y ago
I'd say that the deal is: - With Dynamic Linking, it's the job of the system admin (typically a distribution maintainer) to ensure that the system-provided library and application are compatible — and add patches if needed; - With
14.
by rbarrois 12y ago
This is already available, for a huge set of languages, with Sentry (originally designed for Python), too. Including event aggregation, lib versions, and so on: https://www.getsentry.com/welcome/