| Commit message (Collapse) | Author | Age |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
to reflect this.
|
| |
|
|
|
|
| |
seperated list of supported platforms (according to pep 241).
|
|
|
|
| |
1000 bytes (~333 utf8 characters) for indexes.
|
|\ |
|
| |\ |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
download_url can be an FTP URL (for instance, python-memcached does this) and
since Django doesn't validate FTP URLs on the URLField in models, it's a 400.
|
| | | |
|
|\ \ \ |
|
| | |/
| |/| |
|
| | | |
|
|/ /
| |
| |
| | |
release.pyversion)
|
| | |
|
| | |
|
| |
| |
| |
| | |
a different way.
|
|\ \ |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|/ / |
|
|/ |
|
|
|
|
|
|
| |
With existing constraint, one couldn't upload compiled binaries
targetted at specific platforms if the source for a particular version
was already released.
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Conflicts:
djangopypi/views.py
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \ |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Makes sense to keep the templates in the main folder as long as they
are not independent from the project (they seldome are anyway).
|
| | | |
|