Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

10
  • 1
    \$\begingroup\$ Since you know the input will be ASCII (i.e. fits in a byte) why not use uint8 for one byte less? \$\endgroup\$ Commented Feb 1, 2019 at 20:49
  • 1
    \$\begingroup\$ Language has to be "Python 3 + numpy" here since numpy isn't included with the normal Python distribution \$\endgroup\$ Commented Feb 2, 2019 at 8:39
  • \$\begingroup\$ @Draconis that was actually my plan, but that introduced zeros between the correct uint8 ASCII-codes. I assume this is because Python3 uses Unicode as standard input format for strings. \$\endgroup\$ Commented Feb 4, 2019 at 7:02
  • 1
    \$\begingroup\$ 66 \$\endgroup\$ Commented Feb 4, 2019 at 8:15
  • 1
    \$\begingroup\$ It's fine, after all it's not only based off your solution, but also I don't normally use numpy anyway. Plus, it's kinda unavoidable that a solution might be very similar anyway given that all solutions are public and this is a relatively easy challenge \$\endgroup\$ Commented Feb 4, 2019 at 8:31