visceralfield

Will this be the path for Artifact going forwards? If so, I would be interested in contributing to the python redesign when it is ready for additional contributors. Please let...

PR updated with code nice-ification

Alright, cleaned things up a little more. I've ran the failed Travis test cases on my local machine and was able to handle them without issue - I can take...

Update on the extended length paths issue. I ran the following code expecting `passes` to pass and `fails` to fail, but they both passed. ``` #[cfg(test)] mod tests { use...

I am running windows 10, within PowerShell. `where` has known issues in powershell (see [here](https://stackoverflow.com/questions/16775686/why-doesnt-the-where-command-display-any-output-when-running-in-powershell/16775887)) I am assuming artifact's build system attempts to use `which` on UNIX and `where` on...

@vitiral I have created a workaround in the build script which allows successful compilation. See https://github.com/vitiral/artifact/compare/master...Josh-Thompson:master . Would you like me to submit a PR? It seems like a workaround...

Hi again! Happy to help. To give some insight into why that regex is there - Windows paths usually look like `X:\path\to\place`, where X is a drive letter. There are...

Using cargo-web deploy before doing cargo-build like that worked successfully! I was able to fully compile the project :)

PR #270 opened for this 😄

Regarding the question in the last comment, thought I would chime in and say I would also get a lot of use out of this feature were it in specs.