Re: [Distutils] pip install -e foo (without Repo URL)

2016-04-18 Thread Thomas Güttler



Am 15.04.2016 um 14:12 schrieb Alex Grönholm:

To my knowledge, metadata 2.0 does not have any reliable means to specify a 
repository URL.
So how do you propose to retrieve this information?


How to retrieve the information? I don't know. Where is the best place to store 
meta information for python packages?

Regards,
  Thomas Güttler

--
Thomas Guettler http://www.thomas-guettler.de/
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig


Re: [Distutils] pip install -e foo (without Repo URL)

2016-04-16 Thread Ionel Cristian Mărieș
On Fri, Apr 15, 2016 at 1:05 PM, Thomas Güttler <
guettl...@thomas-guettler.de> wrote:

> This:
>
>  pip install -e
> ​​
> third-party-foo-lib
>
> should be the same as:
>
>  pip install -e git+https:///@mydevbranch#egg=third-party-foo-lib
>

In the first form, how would you tell pip which branch you want?​ (assuming
you don't want whatever is default)

If you have a local directory `​third-party-foo-lib` would that take
precedence over a scm checkout?

​There would need to be a way to add this extra metadata (scm url and
default branch)​ in distributions ... uh, that means changing
setuptools/distutils? That means adoption issues, people won't always have
latest and greatest.


Thanks,
-- Ionel Cristian Mărieș, http://blog.ionelmc.ro
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig


Re: [Distutils] pip install -e foo (without Repo URL)

2016-04-15 Thread Alex Grönholm
To my knowledge, metadata 2.0 does not have any reliable means to 
specify a repository URL.

So how do you propose to retrieve this information?

15.04.2016, 13:05, Thomas Güttler kirjoitti:



Am 14.04.2016 um 14:31 schrieb Ian Cordasco:


On Apr 14, 2016 2:20 AM, "Thomas Güttler" 
> 
wrote:

 >
 > I think it would be very cool if you could install a package editable
 > without the repo-url.
 >
 > The default repo-url can be defined in the meta-data of the package.
 >
 > Background: I came across this becaus saltstack prefers the branch 
"develop", but

 > most other repos use the branch "master".
 >
 > Yes, this is no big problem. I figured out the right repo url soon.
 >
 > Next use case: you use software third-party-foo-lib in your project.
 > Up to now you use it as package. You find a bug and want to fix it.
 > Wouldn't it be great if you could just type "pip install -e 
third-party-foo-lib"

 > and now you are read to create pull requests?

I don't understand how this makes me ready to submit pull requests. 
Can you explain a little more?



This:

 pip install -e third-party-foo-lib

should be the same as:

 pip install -e git+https:///@mydevbranch#egg=third-party-foo-lib

And the information needed to build the URL (in above example 
git+https:///@mydevbranch)

should be provided by setup.py.

Result: you have an editable checkout.

You are right, pull requests most often need a fork first. This is far 
out of scope.


But for custom (non public) projects hosted in a corporate lan, you 
get a ready-to-push

checkout.

Is this enough explanation? Please ask if you have further question.

Regards,
  Thomas Güttler





___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig


Re: [Distutils] pip install -e foo (without Repo URL)

2016-04-15 Thread Thomas Güttler



Am 14.04.2016 um 20:50 schrieb John Wong:


On Apr 14, 2016 2:20 AM, "Thomas Güttler" > wrote:
> Next use case: you use software third-party-foo-lib in your project.
> Up to now you use it as package. You find a bug and want to fix it.
> Wouldn't it be great if you could just type "pip install -e 
third-party-foo-lib"
> and now you are read to create pull requests?

How is this different from 1) fork, 2) update your requirements.txt file 
pointing to the new fork? I guess -e directly
from pip install would be an ad-hoc install of a python library...


Sorry, the term "pull request" was too much. See my other reply from a second 
ago.

Please ask again, if you have further question.

Regards,
  Thomas Güttler

--
Thomas Guettler http://www.thomas-guettler.de/
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig


Re: [Distutils] pip install -e foo (without Repo URL)

2016-04-15 Thread Thomas Güttler



Am 14.04.2016 um 14:31 schrieb Ian Cordasco:


On Apr 14, 2016 2:20 AM, "Thomas Güttler" > wrote:
 >
 > I think it would be very cool if you could install a package editable
 > without the repo-url.
 >
 > The default repo-url can be defined in the meta-data of the package.
 >
 > Background: I came across this becaus saltstack prefers the branch 
"develop", but
 > most other repos use the branch "master".
 >
 > Yes, this is no big problem. I figured out the right repo url soon.
 >
 > Next use case: you use software third-party-foo-lib in your project.
 > Up to now you use it as package. You find a bug and want to fix it.
 > Wouldn't it be great if you could just type "pip install -e 
third-party-foo-lib"
 > and now you are read to create pull requests?

I don't understand how this makes me ready to submit pull requests. Can you 
explain a little more?



This:

 pip install -e third-party-foo-lib

should be the same as:

 pip install -e git+https:///@mydevbranch#egg=third-party-foo-lib

And the information needed to build the URL (in above example 
git+https:///@mydevbranch)
should be provided by setup.py.

Result: you have an editable checkout.

You are right, pull requests most often need a fork first. This is far out of 
scope.

But for custom (non public) projects hosted in a corporate lan, you get a 
ready-to-push
checkout.

Is this enough explanation? Please ask if you have further question.

Regards,
  Thomas Güttler



--
Thomas Guettler http://www.thomas-guettler.de/
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig


Re: [Distutils] pip install -e foo (without Repo URL)

2016-04-14 Thread John Wong
> On Apr 14, 2016 2:20 AM, "Thomas Güttler" 
> wrote:
> > Next use case: you use software third-party-foo-lib in your project.
> > Up to now you use it as package. You find a bug and want to fix it.
> > Wouldn't it be great if you could just type "pip install -e
> third-party-foo-lib"
> > and now you are read to create pull requests?
>
How is this different from 1) fork, 2) update your requirements.txt file
pointing to the new fork? I guess -e directly from pip install would be an
ad-hoc install of a python library...
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig


Re: [Distutils] pip install -e foo (without Repo URL)

2016-04-14 Thread Ian Cordasco
On Apr 14, 2016 2:20 AM, "Thomas Güttler" 
wrote:
>
> I think it would be very cool if you could install a package editable
> without the repo-url.
>
> The default repo-url can be defined in the meta-data of the package.
>
> Background: I came across this becaus saltstack prefers the branch
"develop", but
> most other repos use the branch "master".
>
> Yes, this is no big problem. I figured out the right repo url soon.
>
> Next use case: you use software third-party-foo-lib in your project.
> Up to now you use it as package. You find a bug and want to fix it.
> Wouldn't it be great if you could just type "pip install -e
third-party-foo-lib"
> and now you are read to create pull requests?

I don't understand how this makes me ready to submit pull requests. Can you
explain a little more?

> What do you think?
>
> Regards,
>   Thomas Güttler
>
>
>
> --
> Thomas Guettler http://www.thomas-guettler.de/
> ___
> Distutils-SIG maillist  -  Distutils-SIG@python.org
> https://mail.python.org/mailman/listinfo/distutils-sig
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig


[Distutils] pip install -e foo (without Repo URL)

2016-04-14 Thread Thomas Güttler

I think it would be very cool if you could install a package editable
without the repo-url.

The default repo-url can be defined in the meta-data of the package.

Background: I came across this becaus saltstack prefers the branch "develop", 
but
most other repos use the branch "master".

Yes, this is no big problem. I figured out the right repo url soon.

Next use case: you use software third-party-foo-lib in your project.
Up to now you use it as package. You find a bug and want to fix it.
Wouldn't it be great if you could just type "pip install -e third-party-foo-lib"
and now you are read to create pull requests?

What do you think?

Regards,
  Thomas Güttler



--
Thomas Guettler http://www.thomas-guettler.de/
___
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig