devpi behavior when a modified pypi distribution has been uploaded with the same version?
From my understanding, it's possible for a pypi project owner to delete, and then re-upload a different distribution with the same version. how does devpi handle this? update the cache? ignore this kind of update? I'm guessing devpi updates the cache, which makes sense. It's not devpi's job to do more than pypi is doing. Just want to know devpi's stance on this, and know that it's intentional. If this is in the docs, let me know.
Hello: thanks, Marcus P.S. I'm aware of peep as a client-side solution, and at some pt, pip will grow "lock files" as well I think.
With devpi you can mark repositories as non-volatile:
http://doc.devpi.net/latest/userman/devpi_concepts.html#non-volatile-indexes
This prevents you from uploading foo.bar 0.1 twice, forcing you to do
foo.bar 0.1.1 (or whatever your versioning scheme is) if you make a mistake.
On Tue, Feb 11, 2014 at 12:53 PM, Marcus Smith
Hello: From my understanding, it's possible for a pypi project owner to delete, and then re-upload a different distribution with the same version. how does devpi handle this? update the cache? ignore this kind of update? I'm guessing devpi updates the cache, which makes sense. It's not devpi's job to do more than pypi is doing. Just want to know devpi's stance on this, and know that it's intentional. If this is in the docs, let me know. thanks, Marcus P.S. I'm aware of peep as a client-side solution, and at some pt, pip will grow "lock files" as well I think.
-- You received this message because you are subscribed to the Google Groups "devpi-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to devpi-dev+...@googlegroups.com. To post to this group, send email to devp...@googlegroups.com. Visit this group at http://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/groups/opt_out.
ok, thanks for the pointing that out.
I guess I still want to be clear that the notion of "non-volatile" applies
to the server's caching function.
It currently says: "If a version is uploaded or pushed, it can not be be
removed or overriden"
It doesn't mention caching, where devpi wasn't used for the uploads.
On Tue, Feb 11, 2014 at 12:57 PM, Dave Dash
With devpi you can mark repositories as non-volatile:
http://doc.devpi.net/latest/userman/devpi_concepts.html#non-volatile-indexes
This prevents you from uploading foo.bar 0.1 twice, forcing you to do foo.bar 0.1.1 (or whatever your versioning scheme is) if you make a mistake.
On Tue, Feb 11, 2014 at 12:53 PM, Marcus Smith
wrote: Hello: From my understanding, it's possible for a pypi project owner to delete, and then re-upload a different distribution with the same version. how does devpi handle this? update the cache? ignore this kind of update? I'm guessing devpi updates the cache, which makes sense. It's not devpi's job to do more than pypi is doing. Just want to know devpi's stance on this, and know that it's intentional. If this is in the docs, let me know. thanks, Marcus P.S. I'm aware of peep as a client-side solution, and at some pt, pip will grow "lock files" as well I think.
-- You received this message because you are subscribed to the Google Groups "devpi-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to devpi-dev+...@googlegroups.com. To post to this group, send email to devp...@googlegroups.com. Visit this group at http://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/groups/opt_out.
-- You received this message because you are subscribed to the Google Groups "devpi-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to devpi-dev+...@googlegroups.com. To post to this group, send email to devp...@googlegroups.com. Visit this group at http://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/groups/opt_out.
On Tue, Feb 11, 2014 at 13:44 -0800, Marcus Smith wrote:
ok, thanks for the pointing that out. I guess I still want to be clear that the notion of "non-volatile" applies to the server's caching function. It currently says: "If a version is uploaded or pushed, it can not be be removed or overriden" It doesn't mention caching, where devpi wasn't used for the uploads.
devpi-server should notice pypi.python.org's deleted or overriden archives and update properly. If not i consider it a bug (IIRC there is no specific automated test for this behaviour). holger
On Tue, Feb 11, 2014 at 12:57 PM, Dave Dash
wrote: With devpi you can mark repositories as non-volatile:
http://doc.devpi.net/latest/userman/devpi_concepts.html#non-volatile-indexes
This prevents you from uploading foo.bar 0.1 twice, forcing you to do foo.bar 0.1.1 (or whatever your versioning scheme is) if you make a mistake.
On Tue, Feb 11, 2014 at 12:53 PM, Marcus Smith
wrote: Hello: From my understanding, it's possible for a pypi project owner to delete, and then re-upload a different distribution with the same version. how does devpi handle this? update the cache? ignore this kind of update? I'm guessing devpi updates the cache, which makes sense. It's not devpi's job to do more than pypi is doing. Just want to know devpi's stance on this, and know that it's intentional. If this is in the docs, let me know. thanks, Marcus P.S. I'm aware of peep as a client-side solution, and at some pt, pip will grow "lock files" as well I think.
-- You received this message because you are subscribed to the Google Groups "devpi-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to devpi-dev+...@googlegroups.com. To post to this group, send email to devp...@googlegroups.com. Visit this group at http://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/groups/opt_out.
-- You received this message because you are subscribed to the Google Groups "devpi-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to devpi-dev+...@googlegroups.com. To post to this group, send email to devp...@googlegroups.com. Visit this group at http://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/groups/opt_out.
-- You received this message because you are subscribed to the Google Groups "devpi-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to devpi-dev+...@googlegroups.com. To post to this group, send email to devp...@googlegroups.com. Visit this group at http://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/groups/opt_out.
participants (3)
-
Dave Dash
-
holger krekel
-
Marcus Smith