Timeline for Convert YYYYMM to MMMYY
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 24, 2016 at 20:16 | history | edited | jqkul | CC BY-SA 3.0 |
added 44 characters in body
|
| Jun 24, 2016 at 3:10 | comment | added | TLW | @a25bedc5-3d09-41b8-82fb-ea6c353d75ae - "import time" would save you 6 characters, but would cost you 10 ("time.", twice) | |
| Jun 23, 2016 at 13:32 | comment | added | grooveplex |
Why not simply import time?
|
|
| Jun 23, 2016 at 10:03 | comment | added | Henry Gomersall |
Though this loses a byte: lambda s:" JFMAMJJASONDAEAPAUUUECOENBRRYNLGPTVC"[int(s[4:])::12]+s[2:4]
|
|
| Jun 23, 2016 at 9:37 | comment | added | xnor | @Neil Oh, it wouldn't work there. | |
| Jun 23, 2016 at 9:08 | comment | added | Neil |
@xnor Would that work for the 000112 example?
|
|
| Jun 23, 2016 at 8:39 | comment | added | xnor |
Your manual version can be done in 69 bytes in Python 2 if you take a number as input: lambda n:"JFMAMJJASONDAEAPAUUUECOENBRRYNLGPTVC"[n%100-1::12]+`n`[2:4].
|
|
| Jun 23, 2016 at 0:01 | comment | added | Daniel | Ugh I was going to do exactly your 72 byte answer +1 | |
| Jun 22, 2016 at 21:09 | comment | added | jqkul | @MorganThrapp I got the idea from this answer. | |
| Jun 22, 2016 at 20:59 | comment | added | Morgan Thrapp | That manual parsing is crazy. | |
| Jun 22, 2016 at 20:54 | history | edited | jqkul | CC BY-SA 3.0 |
added a period at end
|
| Jun 22, 2016 at 20:30 | history | answered | jqkul | CC BY-SA 3.0 |