localshop icon indicating copy to clipboard operation
localshop copied to clipboard

Published 20 hours ago • verified publisher icon mvantellingen

Ability to delete packages?

Open victorhooi opened this issue 11 years ago • 12 comments

Hi,

Is it possible to expose functionality through the Localshop webinterface that would let you remove packages?

I assume currently you can just delete the files, then remove all of the entries from the DB manually - however, it would be cleaner if this could be done via the Localshop web interface.

Cheers, Victor

victorhooi avatar Nov 23 '12 02:11 victorhooi

Yeah I agree. This needs to be implemented. Will take a look at it asap

mvantellingen avatar Dec 29 '12 14:12 mvantellingen

Yes please :) As a workaround, is it enough to remove the package in the admin?

dbrgn avatar Feb 06 '13 11:02 dbrgn

Just look out what I described on issue #61. If you remove it, nobody can guarantee that someone already downloaded it, and worse: if you upload a different package (different source code) with same version. We will have inconsistency.

lovato avatar May 10 '13 14:05 lovato

The same problem exists on the "real" pypi too, though. It's just something that you shouldn't do.

Removing packages during the testing phase would be great though. It's the users responsibility not to delete packages that other people are already using (similar to force-rewriting public VCS repositories).

dbrgn avatar May 10 '13 14:05 dbrgn

Latest development branch contains a menu to access Django admin.

llonchj avatar Jun 20 '13 19:06 llonchj

I have a PROD and DSV localshops. Probaly there can be a switch to enable or not that. Will not remove packages on my production environment. Just increment version, fix it and submit it again. Perhaps the best is to mark the package as bad_package. So no one will be able to download it again. And also never overide it.

lovato avatar Jun 22 '13 00:06 lovato

I can see your point having 2 localshop instances. As localshop acts also as a pypi proxy, have you considered using only one localshop and specify the version to download in setup.py or requirements.txt?

llonchj avatar Jun 22 '13 00:06 llonchj

The DSV one is intended for testing only. Package creation/upload tests. If the package is well configured, tested and so on, it goes to production.

lovato avatar Jun 24 '13 18:06 lovato

DSV version was discontinued :-)

lovato avatar Sep 04 '13 14:09 lovato

Marco,

What are the reasons to discontinue DSV version? Are you now installing version-specific modules of your products?

Cheers, Jordi

2013/9/5 Marco Lovato [email protected]

DSV version was discontinued :-)

— Reply to this email directly or view it on GitHubhttps://github.com/mvantellingen/localshop/issues/36#issuecomment-23793219 .

llonchj avatar Sep 04 '13 17:09 llonchj

No, no. We had 2 localshops, one for testing our packaging process, and other one for real packages. Since we kind of mastered the packaging, and found the django /admin path, we no longer need the DSV version. It was the very same localshop version installed on both.

Marco

[]s

Lovato

sent from GMail

On Wed, Sep 4, 2013 at 2:07 PM, Jordi Llonch [email protected]:

Marco,

What are the reasons to discontinue DSV version? Are you now installing version-specific modules of your products?

Cheers, Jordi

2013/9/5 Marco Lovato [email protected]

DSV version was discontinued :-)

— Reply to this email directly or view it on GitHub< https://github.com/mvantellingen/localshop/issues/36#issuecomment-23793219>

.

— Reply to this email directly or view it on GitHubhttps://github.com/mvantellingen/localshop/issues/36#issuecomment-23806427 .

lovato avatar Sep 07 '13 03:09 lovato

Thanks @lovato. I am about to implement CI for the whole devel process in a platform. This is why I was curious about your process.

llonchj avatar Sep 08 '13 07:09 llonchj