I hereby claim:
- I am 0xbe7a on github.
- I am bela (https://keybase.io/bela) on keybase.
- I have a public key whose fingerprint is 2536 9E86 1AA5 9EB7 4C47 B138 6510 870A 77F4 9A99
To claim this, I am signing this object:
var Twit = require('twit') | |
var config = require('./config') | |
var later = require('later'); | |
var msgs = ["Miss You Fox", | |
"Rly miss you fox <3", | |
"Miss ya <3", | |
"Miss you" | |
] |
/** | |
* Created by bela on 17.06.16. | |
*/ | |
module.exports.cookie = "your cookie hear. You can find it at any XHR Request under Cookie: "Whatever"" |
I hereby claim:
To claim this, I am signing this object:
jA0EBwMCcz4Iti7E1E/p0sDGAZjkYniM8lMzxpNO2qCU7Aexppwtx/AZDYyx47+Hdm7Jhb3B/bd0 | |
AnUcyZaqz7wEWvnLM9ct8W+vRwVn61dhq0ZskMMJbUnC4GNLjMKVBQXxyZORul6VaG0XmrH4JZgi | |
NzcOtxENfLxgTJLKdP+cfpZA8GiA8FBm+cevAkoGfy01nPa1uZSnP12TiRaX7R/6EplKVSuiw0/G | |
iekE1NU3/2Uz6b0Lu3Y8Dr99TirxCBGSRnQnLGrzu1vn+ivawakLzqKJ9fNR3B16zcXWNntgNQlF | |
ktizMMbVObhnqQoOVTPWqh6e/Lymbk9nVRv0aEzp8z0QjCMEeKl6etHfqLSQsJt3TNN6xzn+SFHd | |
5x7QGYDGWF9dpLv3wzijQVDwleGSiqZAiLdfCXGoMYO/0aLLGTSdt0eBO37C7+LUUN+XW74bnNma | |
aaBW1fAUVpZUjAywo9vOhVPWC5i9g8Px8IFbDK+Gdn0b81QN6uI354ELhE7eB28iPfcgK8q+uljr | |
oYrizxieXM4Q |
extern crate regex; | |
use regex::Regex; | |
fn main() { | |
let r = match Regex::new(®ex::escape(r"\/[a-z]{3}\/[0-9]{4}")) { | |
Ok(r) => r, | |
Err(e) => { | |
println!("Could not compile regex: {}", e); | |
return; |
#cloud-config | |
apt_update: true | |
packages: | |
- wget | |
- curl | |
- bzip2 | |
- git |
The aim is to introduce a feature set mechanism in the pixi
package manager. This mechanism will enable clear, conflict-free management of dependencies tailored to specific environments, while also maintaining the integrity of fixed lockfiles.
Consider a scenario where a project needs to be tested across multiple Python versions, each requiring a different set of dependencies. In this case, defining separate feature sets for each Python version (like py39
, py310
, etc.) allows for easy switching between environments without conflicts. Similarly, for development purposes, a test
feature set can include dependencies necessary for testing and linting, which are not required in the production environment.