Message140182
| Author |
higery |
| Recipients |
Peter.Waller, alexis, carljm, eric.araujo, higery, meatballhat, michael.mulich, tarek |
| Date |
2011年07月12日.13:34:37 |
| SpamBayes Score |
3.3226522e-07 |
| Marked as misclassified |
No |
| Message-id |
<CAHGir+HiHyrNvCnuWpBPrsyfNc6BqT855QM=e+=ccK5BYdNhPw@mail.gmail.com> |
| In-reply-to |
<1310397438.69.0.52541021819.issue8668@psf.upfronthosting.co.za> |
| Content |
>
> ** After the package has been installed in-place (using the develop
> command), how does one identify it as an in development project (or in
> development mode)? -- Case 3 and 6 touch on this topic (case 3 is a little
> vague at this time), but doesn't explain what type of action is intended. So
> if we install in-place (aka, develop), how does the python interpreter find
> the package? Are we using PYTHONPATH at this point (which would be
> contradict a requirement in case 6)?
>
There is an .egg-link file that will be used by pkg_resources to find the
develop-installed packages, so my current implementation of develop command
in packaging module also adds a .distinfo-link file in the site-packages
which will be used to identify a project is installed in development mode or
not. |
| Files |
| File name |
Uploaded |
|
unnamed
|
higery,
2011年07月12日.13:34:37
|
|