"pyx" is an old-style spkg, nobody has touched it in at least 2 years when we changed the packaging system. Nobody tests it, clearly nobody uses it, and I dare say nobody knows what its for. Apparently its SPKG.txt has barely any useful information, we don't know who packaged it. It clearly doesn't pass the bar for an optional package, which is why it hasn't been converted to a new-style package.
Which also means that pyx's packaging scripts are not in the git repo. So there isn't going to be any grep-ing for deprecated stuff (like environment variables) or any kind of souce audit going to happen. On Tuesday, December 29, 2015 at 10:15:23 PM UTC+1, William wrote: > > On Tue, Dec 29, 2015 at 1:07 PM, Volker Braun <[email protected] > <javascript:>> wrote: > > Its yet another old-style spkg booby trap. > > Can you please clarify -- what does the problem I described have to do > with old style versus new style? The problem is code that contains a > docstring whose existence breaks import the python path module. > > William > > -- > William (http://wstein.org) > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
