Re: [Distutils] Setuptools-Distribute merge announcement
On Wed, Mar 20, 2013 at 12:42 PM, Erik Bray wrote: > Quick question regarding open issues on Distribute (of which I have a > handful assigned to me, and of which I intend to tackle a few others): > Would it it make sense to just hold off on those until the merge is > completed? I'd personally say no, go ahead and do the work now, except that it might be making more work for Jason later at the repository-munging level. ;-) So, hopefully he'll chime in here with a yea or nay. > Also is there anything I can do to help with the merge? > How is that coming along? It's... somewhat of a mess, actually. As Jason mentioned, distribute didn't import setuptools' version history at the start, so it's being a bit of a challenge to merge in a way that maintains history. My original suggestion for merging was to just cherrypick patches and apply them to setuptools (w/appropriate credits), because apart from the added tests and new features, there's at most about 5% difference between setuptools and distribute by line count. (And the added tests and features are mostly in separate files, so can be added without worrying about conflicts. And a lot of the remaining added stuff is being taken out, anyway, because it's the stuff that distribute uses to pretend it's setuptools.) Some challenges that have arisen since, are that the more changes Jason makes to the distribute branch in our merged repo, the less an "hg annot" is actually going to show the real authors of stuff anyway when we get done. (For example, putting back in the missing entry_points.txt whose absence has been causing problems w/distribute lately.) And we're getting huge and (mostly meaningless) conflicts during attempted merges, too. So, if you have any thoughts on what can be done to fix that, by all means, suggest away. ;-) ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Setuptools-Distribute merge announcement
On Wed, Mar 13, 2013 at 8:54 PM, PJ Eby wrote: > Jason Coombs (head of the Distribute project) and I are working on > merging the bulk of the improvements distribute made into the > setuptools code base. He has volunteered to take over maintenance of > setuptools, and I welcome his assistance. I appreciate the > contributions made by the distribute maintainers over the years, and > am glad to have Jason's help in getting those contributions into > setuptools as well. Continuing to keep the code bases separate isn't > helping anybody, and as setuptools moves once again into active > development to deal with the upcoming shifts in the Python-wide > packaging infrastructure (the new PEPs, formats, SSL, TUF, etc.), it > makes sense to combine efforts. > > Aside from the problems experienced by people with one package that > are fixed in the other, the biggest difficulties with the fork right > now are faced by the maintainers of setuptools-driven projects like > pip, virtualenv, and buildout, who have to either take sides in a > conflict, or spend additional time and effort testing and integrating > with both setuptools and distribute. We'd like to end that pain and > simplify matters for end users by bringing distribute enhancements to > setuptools and phasing out the distribute fork as soon as is > practical. > > In the short term, our goal is to consolidate the projects to prevent > duplication, wasted effort, and incompatibility, so that we can start > moving forward. This merge will allow us to combine resources and > teams, so that we may focus on a stable but actively-maintained > toolset. In the longer term, the goal is for setuptools as a concept > to become obsolete. For the first time, the Python packaging world > has gotten to a point where there are PEPs *and implementations* for > key parts of the packaging infrastructure that offer the potential to > get rid of setuptools entirely. (Vinay Sajip's work on distlib, > Daniel Holth's work on the "wheel" format, and Nick Coghlan's taking > up the reins of the packaging PEPs and providing a clear vision for a > new way of doing things -- these are just a few of the developments in > recent play.) > > "Obsolete", however, doesn't mean unmaintained or undeveloped. In > fact, for the "new way of doing things" to succeed, setuptools will > need a lot of new features -- some small, some large -- to provide a > migration path. > > At the moment, the merge is not yet complete. We are working on a > common repository where the two projects' history has been spliced > together, and are cleaning up the branch heads to facilitate > re-merging them. We'd hoped to have this done by PyCon, but there > have been a host of personal, health, and community issues consuming > much of our available work time. But we decided to go ahead and make > an announcement *now*, because with the big shifts taking place in the > packaging world, there are people who need to know about the upcoming > merge in order to make the best decisions about their own projects > (e.g. pip, buildout, etc.) and to better support their own users. > > Thank you once again to all the distribute contributors, for the many > fine improvements you've made to the setuptools package over the > years, and I hope that you'll continue to make them in the future. > (Especially as I begin to phase myself out of an active role in the > project!) > > I now want to turn the floor over to Jason, who's put together a > Roadmap/FAQ for what's going to be happening with the project going > forward. We'll then both be here in the thread to address any > questions or concerns you might have. Quick question regarding open issues on Distribute (of which I have a handful assigned to me, and of which I intend to tackle a few others): Would it it make sense to just hold off on those until the merge is completed? Also is there anything I can do to help with the merge? How is that coming along? Erik ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Setuptools-Distribute merge announcement
On Tue, Mar 19, 2013 at 5:06 AM, Adam GROSZER wrote: > Looks like running > python.exe setup.py test > is the right command to run the tests, isn't it? It certainly should be. As I said, I'm not familiar with the distribute side, so maybe Jason or somebody else can lend a hand here. I know the problem doesn't exist in setuptools now, and it won't be present post-merge either, because we're reverting all changes on the distribute side that introduced bugs relative to setuptools. But short of somebody just sticking a valid setuptools.egg-info/entry_points.txt (and PKG-INFO) into distribute as a stopgap, I've got nothing to suggest for fixing it on the distribute side. ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Setuptools-Distribute merge announcement
Hello, On 03/14/2013 05:25 PM, PJ Eby wrote: On Thu, Mar 14, 2013 at 5:05 AM, Adam GROSZER wrote: I think I can offer you some help, by providing some windows support in the means of testing with various python versions and building binary packages/installers. Note, current tests are failing... http://winbot.zope.org/builders http://winbot.zope.org/builders/distribute_dev%20py_265_win32/builds/202 That looks like the same problem other people are seeing; the problem is that the source you're building from lacks a proper setuptools.egg-info/entry_points.txt. Are you building from revision control directly, or from an sdist? It's built from the bitbucket repo to provide the earliest possible warnings. Whatever you push there gets tested. http://winbot.zope.org/builders/distribute_dev%20py_265_win32/builds/202/steps/hg/logs/stdio A possible workaround is to build with a working version of setuptools or distribute on sys.path when you run setup.py. The distribute modules will get imported, but the egg-info will get picked up from elsewhere, enabling the proper functionality. (Setuptools doesn't have this problem because it includes the entry_points.txt and other critical .egg-info files in its revision control.) It's built with an almost pristine python, which has just pywin32 installed. It would appear that either the entry_points.txt was recently removed, or there was some other workaround for its absence which has recently been removed; I have not had time to investigate, and in any case am not that familiar with the distribute side of things. Looks like running python.exe setup.py test is the right command to run the tests, isn't it? -- Best regards, Adam GROSZER -- Quote of the day: The more times you run over a dead cat, the flatter it gets. ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Setuptools-Distribute merge announcement
On 3/14/13 9:49 AM, Tarek Ziadé wrote: Congrats, This is a good move for packaging. I am very glad the merge is happening, knowing that it's now managed by a community of contributors. Cheers Tarek Oh btw, I was told Philip was saying in private he was agreeing to do the merge as long as I was not involved in it ! :) I am totally fine with this, as I am not involved in packaging anymore. But please make sure he's not ending up being the *only )one maintaining it, because you would end up back to square one: having a project locked up by a single guy. Good luck ! Tarek -- Tarek Ziadé · http://ziade.org · @tarek_ziade ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Setuptools-Distribute merge announcement
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks for the announcment, and especially thanks to all those who have worked on setuptools and distribute. Particular thanks to PJE for having both devised the thing and worked out how to get the community to adopt it. I'm looking forward to the packaging BoF now, instead of dreading it. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlFCCosACgkQ+gerLs4ltQ7qNgCgx+PDk8GYdmVIq1fbGdvqFt6K EaEAniahF//OJkZQ/LVnJx6m1DqS0r+D =0P09 -END PGP SIGNATURE- ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Setuptools-Distribute merge announcement
Congrats, This is a good move for packaging. I am very glad the merge is happening, knowing that it's now managed by a community of contributors. Cheers Tarek -- Tarek Ziadé · http://ziade.org · @tarek_ziade ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Setuptools-Distribute merge announcement
On Thu, Mar 14, 2013 at 5:05 AM, Adam GROSZER wrote: > I think I can offer you some help, by providing some windows support in the > means of testing with various python versions and building binary > packages/installers. > > Note, current tests are failing... > > http://winbot.zope.org/builders That looks like the same problem other people are seeing; the problem is that the source you're building from lacks a proper setuptools.egg-info/entry_points.txt. Are you building from revision control directly, or from an sdist? A possible workaround is to build with a working version of setuptools or distribute on sys.path when you run setup.py. The distribute modules will get imported, but the egg-info will get picked up from elsewhere, enabling the proper functionality. (Setuptools doesn't have this problem because it includes the entry_points.txt and other critical .egg-info files in its revision control.) It would appear that either the entry_points.txt was recently removed, or there was some other workaround for its absence which has recently been removed; I have not had time to investigate, and in any case am not that familiar with the distribute side of things. ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Setuptools-Distribute merge announcement
This is great news from the pip/virtualenv front. Thanks to both you for setuptools and the distribute contributors for all your work so far. Paul On 13 March 2013 20:54, PJ Eby wrote: > Jason Coombs (head of the Distribute project) and I are working on > merging the bulk of the improvements distribute made into the > setuptools code base. He has volunteered to take over maintenance of > setuptools, and I welcome his assistance. I appreciate the > contributions made by the distribute maintainers over the years, and > am glad to have Jason's help in getting those contributions into > setuptools as well. Continuing to keep the code bases separate isn't > helping anybody, and as setuptools moves once again into active > development to deal with the upcoming shifts in the Python-wide > packaging infrastructure (the new PEPs, formats, SSL, TUF, etc.), it > makes sense to combine efforts. > > Aside from the problems experienced by people with one package that > are fixed in the other, the biggest difficulties with the fork right > now are faced by the maintainers of setuptools-driven projects like > pip, virtualenv, and buildout, who have to either take sides in a > conflict, or spend additional time and effort testing and integrating > with both setuptools and distribute. We'd like to end that pain and > simplify matters for end users by bringing distribute enhancements to > setuptools and phasing out the distribute fork as soon as is > practical. > > In the short term, our goal is to consolidate the projects to prevent > duplication, wasted effort, and incompatibility, so that we can start > moving forward. This merge will allow us to combine resources and > teams, so that we may focus on a stable but actively-maintained > toolset. In the longer term, the goal is for setuptools as a concept > to become obsolete. For the first time, the Python packaging world > has gotten to a point where there are PEPs *and implementations* for > key parts of the packaging infrastructure that offer the potential to > get rid of setuptools entirely. (Vinay Sajip's work on distlib, > Daniel Holth's work on the "wheel" format, and Nick Coghlan's taking > up the reins of the packaging PEPs and providing a clear vision for a > new way of doing things -- these are just a few of the developments in > recent play.) > > "Obsolete", however, doesn't mean unmaintained or undeveloped. In > fact, for the "new way of doing things" to succeed, setuptools will > need a lot of new features -- some small, some large -- to provide a > migration path. > > At the moment, the merge is not yet complete. We are working on a > common repository where the two projects' history has been spliced > together, and are cleaning up the branch heads to facilitate > re-merging them. We'd hoped to have this done by PyCon, but there > have been a host of personal, health, and community issues consuming > much of our available work time. But we decided to go ahead and make > an announcement *now*, because with the big shifts taking place in the > packaging world, there are people who need to know about the upcoming > merge in order to make the best decisions about their own projects > (e.g. pip, buildout, etc.) and to better support their own users. > > Thank you once again to all the distribute contributors, for the many > fine improvements you've made to the setuptools package over the > years, and I hope that you'll continue to make them in the future. > (Especially as I begin to phase myself out of an active role in the > project!) > > I now want to turn the floor over to Jason, who's put together a > Roadmap/FAQ for what's going to be happening with the project going > forward. We'll then both be here in the thread to address any > questions or concerns you might have. > ___ > Distutils-SIG maillist - Distutils-SIG@python.org > http://mail.python.org/mailman/listinfo/distutils-sig > ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Setuptools-Distribute merge announcement
On Thu, Mar 14, 2013 at 1:34 AM, Carl Meyer wrote: > On 03/13/2013 06:54 PM, PJ Eby wrote: >> Jason Coombs (head of the Distribute project) and I are working on >> merging the bulk of the improvements distribute made into the >> setuptools code base. He has volunteered to take over maintenance of >> setuptools, and I welcome his assistance. > > This merge is very good news for Python packaging. Kudos and thanks to > you and Jason. > > This also seems like an appropriate opportunity to say: thank you for > building the first working packaging system for Python (the one that all > popular packaging tools are still based on), and for all the work you've > put into it over the years. Yup. Well said. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Setuptools-Distribute merge announcement
On Wed, Mar 13, 2013 at 8:54 PM, PJ Eby wrote: > Jason Coombs (head of the Distribute project) and I are working on > merging the bulk of the improvements distribute made into the > setuptools code base. He has volunteered to take over maintenance of > setuptools, and I welcome his assistance. I appreciate the > contributions made by the distribute maintainers over the years, and > am glad to have Jason's help in getting those contributions into > setuptools as well. Continuing to keep the code bases separate isn't > helping anybody, and as setuptools moves once again into active > development to deal with the upcoming shifts in the Python-wide > packaging infrastructure (the new PEPs, formats, SSL, TUF, etc.), it > makes sense to combine efforts. That's awesome news. Thanks Phillip and Jason! Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Setuptools-Distribute merge announcement
On 14 March 2013 00:54, PJ Eby wrote: > Jason Coombs (head of the Distribute project) and I are working on > merging the bulk of the improvements distribute made into the > setuptools code base. Absolutely fantastic news!!! Thanks to both Jason and PJE for making this happen. Paul ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Setuptools-Distribute merge announcement
Hello, On 03/14/2013 01:57 AM, Jason R. Coombs wrote: As PJE mentioned in his e-mail, he and I have been working on a merge of the code lines of Setuptools and Distribute. I'm excited about this transition and I hope you are too. I think I can offer you some help, by providing some windows support in the means of testing with various python versions and building binary packages/installers. Note, current tests are failing... http://winbot.zope.org/builders -- Best regards, Adam GROSZER -- Quote of the day: Men show their character in nothing more clearly than by what they think laughable. - Goethe ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Setuptools-Distribute merge announcement
Carl Meyer oddbird.net> writes: > > On 03/13/2013 06:54 PM, PJ Eby wrote: > > Jason Coombs (head of the Distribute project) and I are working on > > merging the bulk of the improvements distribute made into the > > setuptools code base. He has volunteered to take over maintenance of > > setuptools, and I welcome his assistance. > > This merge is very good news for Python packaging. Kudos and thanks to > you and Jason. > > This also seems like an appropriate opportunity to say: thank you for > building the first working packaging system for Python (the one that all > popular packaging tools are still based on), and for all the work you've > put into it over the years. > Emphatic +1! Regards, Vinay Sajip ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Setuptools-Distribute merge announcement
On Wed, Mar 13, 2013 at 5:57 PM, Jason R. Coombs wrote: > As PJE mentioned in his e-mail, he and I have been working on a merge of the > code lines of Setuptools and Distribute. I'm excited about this transition > and I hope you are too. Yay, thank you both for working hard to make this happen, and also for announcing it now for the sake of my sanity (and probably Jason's too) at the packaging and distribution mini-summit on Friday night :) Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Setuptools-Distribute merge announcement
On 03/13/2013 06:54 PM, PJ Eby wrote: > Jason Coombs (head of the Distribute project) and I are working on > merging the bulk of the improvements distribute made into the > setuptools code base. He has volunteered to take over maintenance of > setuptools, and I welcome his assistance. This merge is very good news for Python packaging. Kudos and thanks to you and Jason. This also seems like an appropriate opportunity to say: thank you for building the first working packaging system for Python (the one that all popular packaging tools are still based on), and for all the work you've put into it over the years. Carl signature.asc Description: OpenPGP digital signature ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Setuptools-Distribute merge announcement
On Wed, Mar 13, 2013 at 9:52 PM, Ross Patterson wrote: > "Jason R. Coombs" writes: >> >> Who is invited to contribute? Who is excluded? > > As long as the merged project, whatever it's called, doesn't become as > closed of to community contributions or input as led to the fork in the > first place, a merge seems like a great idea. Personally, if I have the > option, I'd probably choose to stick to "distribute" until I have some > experience indicating that the merged project won't have the same > problems that led to the original fork. > > Meantime, I raise my glass to the merge and to the Distribute developers > for keeping things moving! Distribeaut! I welcome our new setuptools overlords, and it will be so much easier to just call it setuptools always, and eventually put it on a shelf. Stunning news. :-) Daniel ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Setuptools-Distribute merge announcement
"Jason R. Coombs" writes: > > Who is invited to contribute? Who is excluded? As long as the merged project, whatever it's called, doesn't become as closed of to community contributions or input as led to the fork in the first place, a merge seems like a great idea. Personally, if I have the option, I'd probably choose to stick to "distribute" until I have some experience indicating that the merged project won't have the same problems that led to the original fork. Meantime, I raise my glass to the merge and to the Distribute developers for keeping things moving! Ross ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
[Distutils] Setuptools-Distribute merge announcement
As PJE mentioned in his e-mail, he and I have been working on a merge of the code lines of Setuptools and Distribute. I'm excited about this transition and I hope you are too. In this message, I will provide some answers based on questions that he and I encountered in our discussions and subsequent merge activity. If you have further questions, please direct them to both of us and we intend to answer promptly and also update the FAQ at the wiki (https://bitbucket.org/jaraco/setuptools/wiki/Setuptools%20and%20Distribute% 20Merge%20FAQ). - Jason R. Coombs Where does the merge occur? The merge is occurring between the heads of the default branch of Distribute and the setuptools-0.6 branch of Setuptools. The Setuptools SVN repo has been converted to a Mercurial repo hosted on Bitbucket. The work is still underway, so the exact changesets included may change, although the anticipated merge targets are Setuptools at 0.6c12 and Distribute at 0.6.35. What happens to other branches? Distribute 0.7 was abandoned long ago and won't be included in the resulting code tree, but may be retained for posterity in the original repo. Setuptools default branch (also 0.7 development) may also be abandoned or may be incorporated into the new merged line if desirable (and as resources allow). What history is lost/changed? As setuptools was not on Mercurial when the fork occurred and as Distribute did not include the full setuptools history (prior to the creation of the setuptools-0.6 branch), the two source trees were not compatible. In order to most effectively communicate the code history, the Distribute code was grafted onto the (originally private) setuptools Mercurial repo. Although this grafting maintained the full code history with names, dates, and changes, it did lose the original hashes of those changes. Therefore, references to changes by hash (including tags) are lost. Additionally, any heads that were not actively merged into the Distribute 0.6.35 release were also omitted. As a result, the changesets included in the merge repo are those from the original setuptools repo and all changesets ancestral to the Distribute 0.6.35 release. What features will be in the merged code base? In general, all "features" added in distribute will be included in setuptools. Where there exist conflicts or undesirable features, we will be explicit about what these limitations are. Changes that are backward-incompatible from setuptools 0.6 to distribute will likely be removed, and these also will be well documented. Bootstrapping scripts (ez_setup/distribute_setup) and docs, as with distribute, will be maintained in the repository and built as part of the release process. Documentation and bootstrapping scripts will be hosted at python.org, as they are with distribute now. Documentation at telecommunity will be updated to refer or redirect to the new, merged docs. On the whole, the merged setuptools should be largely compatible with the latest releases of both setuptools and distribute and will be an easy transition for users of either library. Who is invited to contribute? Who is excluded? While we've worked privately to initiate this merge due to the potential sensitivity of the topic, no one is excluded from this effort. We invite all members of the community, especially those most familiar with Python packaging and its challenges to join us in the effort. We have lots of ideas for how we'd like to improve the codebase, release process, everything. Like distribute, the post-merge setuptools will have its source hosted on bitbucket. (So if you're currently a distribute contributor, about the only thing that's going to change is the URL of the repository you follow.) Also like distribute, it'll support Python 3, and hopefully we'll soon merge Vinay Sajip's patches to make it run on Python 3 without needing 2to3 to be run on the code first. Why Setuptools and not Distribute or another name? We do understand that this announcement might be unsettling for some. The setuptools name has been subjected to a lot of deprecation in recent years, so the idea that it will now be the preferred name instead of distribute might be somewhat difficult or disorienting for some. We considered use of another name (Distribute or an entirely new name), but that would serve to only complicate matters further. Instead, our goal is to simplify the packaging landscape but without losing any hard-won advancements. We hope that the people who worked to spread the first message will be equally enthusiastic about spreading the new one, and we especially look forward to seeing the new posters and slogans celebrating the new setuptools. What is the timeframe of release? There are no hard timeframes for any of this effort, although progress is underway and a draft merge is underway and being tested privately. As an unfunded volunteer effort, our time to put i
Re: [Distutils] Setuptools-Distribute merge announcement
woo hoo!!! awesome!!! Marcus On Wed, Mar 13, 2013 at 5:54 PM, PJ Eby wrote: > Jason Coombs (head of the Distribute project) and I are working on > merging the bulk of the improvements distribute made into the > setuptools code base. He has volunteered to take over maintenance of > setuptools, and I welcome his assistance. I appreciate the > contributions made by the distribute maintainers over the years, and > am glad to have Jason's help in getting those contributions into > setuptools as well. Continuing to keep the code bases separate isn't > helping anybody, and as setuptools moves once again into active > development to deal with the upcoming shifts in the Python-wide > packaging infrastructure (the new PEPs, formats, SSL, TUF, etc.), it > makes sense to combine efforts. > > Aside from the problems experienced by people with one package that > are fixed in the other, the biggest difficulties with the fork right > now are faced by the maintainers of setuptools-driven projects like > pip, virtualenv, and buildout, who have to either take sides in a > conflict, or spend additional time and effort testing and integrating > with both setuptools and distribute. We'd like to end that pain and > simplify matters for end users by bringing distribute enhancements to > setuptools and phasing out the distribute fork as soon as is > practical. > > In the short term, our goal is to consolidate the projects to prevent > duplication, wasted effort, and incompatibility, so that we can start > moving forward. This merge will allow us to combine resources and > teams, so that we may focus on a stable but actively-maintained > toolset. In the longer term, the goal is for setuptools as a concept > to become obsolete. For the first time, the Python packaging world > has gotten to a point where there are PEPs *and implementations* for > key parts of the packaging infrastructure that offer the potential to > get rid of setuptools entirely. (Vinay Sajip's work on distlib, > Daniel Holth's work on the "wheel" format, and Nick Coghlan's taking > up the reins of the packaging PEPs and providing a clear vision for a > new way of doing things -- these are just a few of the developments in > recent play.) > > "Obsolete", however, doesn't mean unmaintained or undeveloped. In > fact, for the "new way of doing things" to succeed, setuptools will > need a lot of new features -- some small, some large -- to provide a > migration path. > > At the moment, the merge is not yet complete. We are working on a > common repository where the two projects' history has been spliced > together, and are cleaning up the branch heads to facilitate > re-merging them. We'd hoped to have this done by PyCon, but there > have been a host of personal, health, and community issues consuming > much of our available work time. But we decided to go ahead and make > an announcement *now*, because with the big shifts taking place in the > packaging world, there are people who need to know about the upcoming > merge in order to make the best decisions about their own projects > (e.g. pip, buildout, etc.) and to better support their own users. > > Thank you once again to all the distribute contributors, for the many > fine improvements you've made to the setuptools package over the > years, and I hope that you'll continue to make them in the future. > (Especially as I begin to phase myself out of an active role in the > project!) > > I now want to turn the floor over to Jason, who's put together a > Roadmap/FAQ for what's going to be happening with the project going > forward. We'll then both be here in the thread to address any > questions or concerns you might have. > ___ > Distutils-SIG maillist - Distutils-SIG@python.org > http://mail.python.org/mailman/listinfo/distutils-sig > ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
[Distutils] Setuptools-Distribute merge announcement
Jason Coombs (head of the Distribute project) and I are working on merging the bulk of the improvements distribute made into the setuptools code base. He has volunteered to take over maintenance of setuptools, and I welcome his assistance. I appreciate the contributions made by the distribute maintainers over the years, and am glad to have Jason's help in getting those contributions into setuptools as well. Continuing to keep the code bases separate isn't helping anybody, and as setuptools moves once again into active development to deal with the upcoming shifts in the Python-wide packaging infrastructure (the new PEPs, formats, SSL, TUF, etc.), it makes sense to combine efforts. Aside from the problems experienced by people with one package that are fixed in the other, the biggest difficulties with the fork right now are faced by the maintainers of setuptools-driven projects like pip, virtualenv, and buildout, who have to either take sides in a conflict, or spend additional time and effort testing and integrating with both setuptools and distribute. We'd like to end that pain and simplify matters for end users by bringing distribute enhancements to setuptools and phasing out the distribute fork as soon as is practical. In the short term, our goal is to consolidate the projects to prevent duplication, wasted effort, and incompatibility, so that we can start moving forward. This merge will allow us to combine resources and teams, so that we may focus on a stable but actively-maintained toolset. In the longer term, the goal is for setuptools as a concept to become obsolete. For the first time, the Python packaging world has gotten to a point where there are PEPs *and implementations* for key parts of the packaging infrastructure that offer the potential to get rid of setuptools entirely. (Vinay Sajip's work on distlib, Daniel Holth's work on the "wheel" format, and Nick Coghlan's taking up the reins of the packaging PEPs and providing a clear vision for a new way of doing things -- these are just a few of the developments in recent play.) "Obsolete", however, doesn't mean unmaintained or undeveloped. In fact, for the "new way of doing things" to succeed, setuptools will need a lot of new features -- some small, some large -- to provide a migration path. At the moment, the merge is not yet complete. We are working on a common repository where the two projects' history has been spliced together, and are cleaning up the branch heads to facilitate re-merging them. We'd hoped to have this done by PyCon, but there have been a host of personal, health, and community issues consuming much of our available work time. But we decided to go ahead and make an announcement *now*, because with the big shifts taking place in the packaging world, there are people who need to know about the upcoming merge in order to make the best decisions about their own projects (e.g. pip, buildout, etc.) and to better support their own users. Thank you once again to all the distribute contributors, for the many fine improvements you've made to the setuptools package over the years, and I hope that you'll continue to make them in the future. (Especially as I begin to phase myself out of an active role in the project!) I now want to turn the floor over to Jason, who's put together a Roadmap/FAQ for what's going to be happening with the project going forward. We'll then both be here in the thread to address any questions or concerns you might have. ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
