I hereby claim:
- I am djiit on github.
- I am jtanay (https://keybase.io/jtanay) on keybase.
- I have a public key ASBHzQOOo4BEtaeIYuaQ_ZVhK3llalGcntB5QAwoBkdwVgo
To claim this, I am signing this object:
<polymer-element name="django-ajax" extends="core-ajax"> | |
<script> | |
Polymer({ | |
getCSRFCookie: function() { | |
b = document.cookie.match('(^|;)\\s*csrftoken\\s*=\\s*([^;]+)'); | |
return b ? b.pop() : ''; | |
}, | |
ready: function() { | |
this.super(); | |
this.headers = { |
I hereby claim:
To claim this, I am signing this object:
Yes, I hear you. pip is a great tool and has been around for quite a long time. But for 3 years or so, people (contributors) have been looking for a way to enhance our packages management experience. Think about the superpowers of a npm (or better, yarn) in your favorite tool.
What they propose is (more or less) a replacement for the age-old requirements.txt
file : the Pipfile.
The new Pipfile differs from the old-style requirements file is several ways :
BEGIN KEYBASE SALTPACK ENCRYPTED MESSAGE. kiaJtA57gQd9eiw WIqKKfcWxVBKTAj BBPxms1p8IjAudf fsekdkJa5kjuzMD aCdFh8VfECezU51 bfO4pzqsRCUeWZl iiqNn8vOFh5yfo4 83WmRlDlIFTi651 JxXlNybsKGADJYG VDD7LjXZXm27JkV odlQcWLDhMZ3cDL NgvLVHUeiJhzfYE xn3PRsVEG8AJ1T6 UKv8j9Gfvx6jrLG s0UxF8LbgA3bx2x 1Zw3Nx1iQOvmffX xomb2lYlu9XliC8 l9bxhwmotka1NUD R91rR6wjUiRB7Iy z45uAnolkjb0LU3 6Q1F0pK5rkUpjgs 9iJoRxHIaWZ8mfQ OEWhmP3RTjX3SUR t6HKPJoRUzIBjxd gPj8hi40gASHEWa 8hjGxzd0oM0NqZ7 ozQARzbtqAMiy1m IoPTiBT1sxmE4xT dtwwVB6rayPQV5h 6SIJVf1JW90eaVB XrA9S3fvAa6xjpZ 5WCMRgdfmeTeoCA s9o6C2XZoCGqGUa pH6IrwX98ZnN8yi BglZ2OIGsMlgKMx rZtkOuKNYpgNK6n WQvDAMJ5EWMUTDX DbExAKtoHzePX9M oW75VKKXyZIrRUN dUF9KVj2f5q2JVI 4YJwlkugRGHOLQr PnhpT3j4LnmsyP0 G3FhYILIBR5WvvG F2BpOiPn4sHjsa8 ojeDJ8jFCe1oojk cSdLCVj2QEIMAPT oO7QAWi55mz69K8 p6wyWRfyWsicy7F B5Kn3RDkjxvsWWK wtG194FRfvRBgrn uB36nS7L4ki3I7u NXmWg74uAgCe5nx xn7IaTc2xfE682n uDO3bKwvEzh1809 8zjC1u2nB2XXbLC ie9BzdB3Rm1Arlm GgDi25rz9zWvCnd vCugEULztNnPGCW IhH9rWWdjfBeIws gVcBufFfFRntf61 7YzO3Rk5YOVKdWh Q7LQ6U |