Gabriel Huber
Gabriel Huber
Not an issue with the package list and it's unlikely the author will ever fix this.
What should be done with the detected packages? Should I rename them with an underscore and add an alias?
We decided this needs to be discussed in an RFC because it only makes sense if we enforce package names to match module names, which is a much bigger change.
Deleted packages are now marked with the tag "deleted"
This will be handled on a bigger scale soon with tagging.
Thanks, this is a great feature request! I don't have a feature like that at the moment.
I wrote a quick implementation for `manifest` and `load_path` at https://github.com/Yepoleb/pyramid_webassets/commit/cfba87e1e8cbe5cd9f42fc62fa2a23ecc8a6be6e. It's probably not ready to be merged, but maybe you want to take some parts from it.
I have tagged all unavailable packages with "deleted". There are some smaller issues still remaining with documentation links but the major problems are resolved.
Then stop using `int` for array iteration, it's the wrong type. There's a reason someone added the `size_t` typedef to the standard and you're completely eliminating its benefits. The reverse...
I couldn't find any official documents stating that `size_t` should be used, but there are a few StackOverflow questions about the topic, like this one: http://stackoverflow.com/questions/1951519/when-should-i-use-stdsize-t. It just seems obvious...