> On Mar 18, 2016, at 1:29 PM, Donald Stufft <[email protected]> wrote: > > >> On Mar 17, 2016, at 8:51 PM, Chris Barker - NOAA Federal >> <[email protected]> wrote: >> >> When do we expect that? A lot of people rely on the current system, we >> really need to find a way to maintain it 'till it's replaced. > > Practically speaking I’m the only person maintaining the actual code behind > legacy PyPI right now. Due to some personal stuff I haven’t had the mental > bandwidth to dig through debugging the ball of twine that is legacy PyPI. > It’s been sort of falling apart a bit and fixing some of these issues require > a substantial amount of effort. I don’t know what’s wrong with search, it’s > probably not one of those kinds of issues, but the hope is that we can just > squash a bunch of these at once with the new code base. > > As far as “When do we expect that”, the answer is basically “when it’s > ready”. You can see what’s done so far at warehouse.python.org (backed by the > same live database) and the current work is being done at > github.com/pypa/warehouse.
Just to make it explicit, if anyone wants to submit a patch with a cogent explanation of what was wrong I'm sure it would get fixed ASAP. Such is the eternal rallying cry of FOSS :-) --Noah
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Distutils-SIG maillist - [email protected] https://mail.python.org/mailman/listinfo/distutils-sig
